Deliverable 3.1. Metadata Model - ICT Biochain€¦ · Deliverable 3.1. Metadata Model Page 11 of...

This project has received funding from the Bio Based

Industries Joint Undertaking under the European

Union’s Horizon 2020 research and innovation

programme under grant agreement No 792221.

Deliverable 3.1. Metadata

Model

Acronym: ICT-BIOCHAIN

Project title: ICT-BIOCHAIN - ICT Tools in Efficient Biomass Supply Chains for

Sustainable Chemical Production

Contract Nº: 792221

Start date: 01/06/2018

Duration: 24 months

Deliverable number D3.1

Deliverable title Metadata Model

Submission due date M6 – November 2018

Actual submission date M6 – November 2018

Work Package WP3

WP Lead Beneficiary IML

Dissemination Level Public

Version 03

Authors Timo Erler (Fraunhofer IML)

Ref. Ares(2019)6423438 - 17/10/2019

Deliverable 3.1. Metadata Model

of 13

DOCUMENT CONTROL PAGE

Author(s) Timo Erler (Fraunhofer IML)

Version

history

#### ReviewerReviewerReviewerReviewer CommentsCommentsCommentsComments

00 All Draft

01 All Method and Model update

02 All Formalization process

03 All Template update


of 13

1. Executive Summary

The Metadata Model describes all entities and properties for ICT solutions in the

domain of Biomass Supply Chain. Based on the Metadata Model the platform prototype

will be developed. The information kept in this Metadata Model will be changing over

time. Therefore, a method is implemented to create, publish, evaluate and update the

Metadata Model and the technical representation. The method is a circle around

requirements and is build out of five steps that are iterative. Every step produces

outputs that are necessary for the next step.


of 13

Content

1. Executive Summary ........................................................................................................ 3

2. Acronyms and abbreviations ......................................................................................... 5

3. Introduction ................................................................................................................... 6

4. Modeling Method .......................................................................................................... 6

5. Metadata Model ............................................................................................................ 8

5.1. Competency Questions .............................................................................................. 8

5.2. Vocabulary .................................................................................................................. 9

5.3. UML Diagram (Conceptualization) .......................................................................... 10

Detailed Description .................................................................................................... 10

6. Conclusions and Outlook ............................................................................................. 12

7. References .................................................................................................................... 13


of 13

2. Acronyms and abbreviations

UMLUMLUMLUML Unified Modelling Language

ICTICTICTICT Internet CommunicaEon

Technology

IoTIoTIoTIoT Internet of Things

TRLTRLTRLTRL Technology Readiness Level

URIURIURIURI Uniform Resource IdenEfier


of 13

3. Introduction

This document is divided into two parts. One part describes the Metadata Model itself.

The Metadata Model describes region specific data models for biomass sources and

models containing ICT, IoT and Industry 4.0 technologies. The described Metadata

Model is the first version and contains the initial entities and properties. The Metadata

Model will take changes during the project, as requirements and other factors can

change. Therefore, the document provides also a continuous developing method. The

method explains how to create, publish, evaluate and update a Metadata Model

according to data changes.

4. Modeling Method

The Method is a circle of actions and is intended for an ongoing modelling process. The

result is a Metadata Model. Figure 1 illustrates the method:

Figure 1: Modelling Method


of 13

The essential part are the requirements. They are the starting point and reference in

every step. In a first step the stakeholders define a goal and a scope. Goal and scope are

heavily connected to the requirements as they are based on them, but also updates the

list based on the vision the project team is trying to reach. The target of this step is to

specify a domain / context, aims and objectives, roles and responsibilities. Beside this

general output there is also a data specific output: Competency Questions. Competency

Questions are derived from the requirements and are intended to get needed

information out of the data. An example: In which countries is the ICT solution used?

Competency Questions are used in the development and publication process to check if

the modelled information meets the requirement. With the developed model you have

to be ready to answer the questions.

The second step is called “Information Gathering”. Based on the goal and requirements

(especially Competency Questions) the project team analyses possible data sources and

data itself to get an overview about the information that can be used to create the

ontology (in this case Metadata Model). The result is a Vocabulary (or Glossary) of

identified terms. This Vocabulary lists all terms, but does not link them to each other.

The linkage is made in a next step called “Conceptualization”. This step creates a model

out of the list of terms. The model is human readable. In this case it is modelled in the

Unified Modelling Language (UML). UML shows the information by classes (entities) and

attributes (properties). Beside the linkage of classes and attributes, UML offers the

possibility to add constraints such as enumerations.

After the model is finished it is necessary to transfer the generic approach to a formal

representation. This formal representation is called ontology. The ontology describes

the conceptual entities, properties and connections in form of triples. Triples can be

compared to a sentence of subject, predicate object. An example: Solution X (subject) is

used in (predicate) country Y (object). The ontology describes on the one hand the

schema and on the other hand the instantiation. The entirety of triples creates a graph

that is based on the schema and contains all instantiations. The graph must be able to

answer all the competency questions in form of query.

In the “Publication & Evaluation” step the ontology is implemented in the IT

environment and is usable by the users. Also the ontology is checked against the

requirements and combined with other feedback from stakeholders to eventually

generate optimization potential.


of 13

¡Error! No se encuentra el origen de la referencia.¡Error! No se encuentra el origen de la referencia.¡Error! No se encuentra el origen de la referencia.¡Error! No se encuentra el origen de la referencia. sums up the steps with tasks and

outputs:

Step Tasks Output

Goal & Scope

Definition

• Specify requirements and

project context

• Determine goal & scope

• Create competency

questions

• A list of

competency

questions

Information

Gathering

• Gather information from

several data sources

• List terms that are figured

out

• Vocabulary (list of

terms without

linkage)

Conceptualization • Define classes in UML

• Define attributes in UML

• Connect classes via

attributes

• Add constraints to diagram

• Check against competency

questions

• UML model (human

readable)

Formalization • Formalization of the

conceptual model in a

representation language

• Check against competency

questions

• Ontology (machine

readable)

Publication &

Evaluation

• Implementation in IT

environment

• Evaluation of result

• Documentation of

optimization

potential Table 1: Methodology Steps & Results

5. Metadata Model

The following chapter describes the result of the first three steps of the previous

defined method. It starts with the competency questions, continues with the vocabulary

and results in the Metadata Model itself with a detailed description of properties.

5.1. Competency Questions

Based on the projects team input the following competency questions are created for

the project:

• What ICT solutions are being used in a specific country?

• Which ICT solutions are implemented in the region regarding biomass?

• Can I filter ICT technologies by type of biomass?


of 13

• What are the benefits and costs of a specific ICT

technology?

• At which level of implementation is a specific ICT technology right now?

• Who are potential local clients for biomass?

• What are current supply value chains / oder supply chain values?

• Who are ICT technology suppliers and what is their field of expertise?

• Which ICT technologies apply to a specific supply chain?

• Which ICT technologies are current state of the art?

• What is the necessary knowledge about available innovative technologies that

can be used?

• What are the outcomes and benefits of the technology used in biomass supply

chain?

• Which innovative tools are available in each region?

• Which projects and developments are currently running?

• Who is the contact person for a specific ICT technology?

• When does a ICT Technology that is currently in development approximately go

into service?

5.2. Vocabulary

Derived from the internal discussions and with look a on the competency questions, the

following terms are listed in the vocabulary:

• ICT-Information

o The Contents of the ICT-Biochain will be summarized within ICT-Information

objects. These contain all information of the specific content including

references to objects that relate to it.

• ICT-Image

o Images will be encapsulated in an ICT-Image that contains the actual filepath

to the image as well as the name and source of it.

• Person

o An entity of the Person class will hold a persons name and his contact

information as well as the name of the company they work for.

• TRL

o TRL (Technological Readiness level) is an enumeration describing the

different levels of readiness of a technology.

• Country

o Enumeration of valid country-names.

• Sector

o Enumeration of valid sectors relevant to possible products and projects.


of 13

5.3. UML Diagram (Conceptualization)

The following UML Diagram illustrates the entities and properties in form of classes and

attributes and connects them with each other.

Figure 2: UML Diagram of the Metadata Model

Detailed Description

A detailed description of the UML Diagram is listed in the following table to give further

information of the modelled result. This description contains also type and constraint

information. ¡Error! No se encuentra el origen de la referencia.¡Error! No se encuentra el origen de la referencia.¡Error! No se encuentra el origen de la referencia.¡Error! No se encuentra el origen de la referencia. illustrates the detailed

description.

Name of PropertyName of PropertyName of PropertyName of Property DescriptionDescriptionDescriptionDescription TypeTypeTypeType ConstraintsConstraintsConstraintsConstraints

namenamenamename Name of the

Product/Project/Technology +

Acronym

String

rAndDrAndDrAndDrAndD Name of the Company, R&D

Institute, University (Research

Group) involved in the project

String

generalInfogeneralInfogeneralInfogeneralInfo Two line introduction to

Technology

String Maximum of two

lines.

intoServiceintoServiceintoServiceintoService Date when the technology is

expected to launch or has

gone into service

LocalDate

weblinkweblinkweblinkweblink URI to the website providing

extra information about the

technology

URI Has to be a valid URI

publishLinkpublishLinkpublishLinkpublishLink URI to further URI Has to be a valid URI


of 13

articles/publications about the

research or project or

references

extraInfoextraInfoextraInfoextraInfo Other relevant information

about the project or

where/with whom other

information can be found

String

processStepsprocessStepsprocessStepsprocessSteps List of process steps in the

application/operation of the

specified technology

List<String>

benefitsbenefitsbenefitsbenefits Short text about the benefits

of the technology in its current

usage

String

costPerUnitcostPerUnitcostPerUnitcostPerUnit The cost per unit of the

specified technology

double

environmentalImpactenvironmentalImpactenvironmentalImpactenvironmentalImpact Any information on potential

environmental impact

integrating specified

technology within supply

chains

String

ICTInfoIDICTInfoIDICTInfoIDICTInfoID Unique identifier of the

technology used within the

system

ObjectID

imageimageimageimage Image representing or

depicting the technology

ICT-Image

contactcontactcontactcontact Contact person for the

project/research

Person

countrycountrycountrycountry Country in which the main

research undertaken or the

technology is installed in

Country Must be an Element

of the Country-

enumeration

containing the

names of existing

countries.

areaOfApplicationareaOfApplicationareaOfApplicationareaOfApplication Area in which the technology

is currently applied in

List<String>

potentialAOApotentialAOApotentialAOApotentialAOA Potential future inclusion

within biobased supply chain

areas

List<String>

subsectorsubsectorsubsectorsubsector Subsector to which the

product/project relate to

Sector Valid sectors are

IOT, ICT and

Industry 4.0

imagePathimagePathimagePathimagePath Datapath to Image-File within

the system

File

imageNameimageNameimageNameimageName Name of the Image String

imageSourceimageSourceimageSourceimageSource Source of the Image String

givennamegivennamegivennamegivenname Given name of the contact String


of 13

person

surnamesurnamesurnamesurname Surname of the contact person String

companycompanycompanycompany Company the contact person

works for or is affiliated to

String

mailAddressmailAddressmailAddressmailAddress E-Mail Address of the contact

person

Email Has to be a valid E-

Mail address

phonenumberphonenumberphonenumberphonenumber Phone number of the contact

person

PhoneNumber Has to be a valid

phone number

operationalStatusoperationalStatusoperationalStatusoperationalStatus Technological Readiness Level TRL See description

below Table 2: Detailed Description

TRLTRLTRLTRL----LevelLevelLevelLevel

• TRL 1 – basic principles observed

• TRL 2 – technology concept formulated

• TRL 3 – experimental proof of concept

• TRL 4 – technology validated in lab

• TRL 5 – technology validated in relevant environment (industrially relevant

environment in the case of key enabling technologies)

• TRL 6 – technology demonstrated in relevant environment (industrially relevant

environment in the case of key enabling technologies)

• TRL 7 – system prototype demonstration in operational environment

• TRL 8 – system complete and qualified

• TRL 9 – actual system proven in operational environment (competitive

manufacturing in the case of key enabling technologies; or in space)

• TRL 10 - Best practice

6. Conclusions and Outlook

The next steps (Formalization and Publication) will take place in the implementation

phase of the platform prototype. In the meantime, the first model will be evaluated and

optimized by the project team. Also in this phase, the step of information gathering is

used again, as external ontologies will be researched to get formalization standards and

best practices included in the Metadata Model.


of 13

7. References

M. Uschold and M. King. (1995). Towards a Methodology for Building Ontologies. In

Proc. of the IJCAI’95, Workshop on Basic Ontological Issues in Knowledge Sharing, 1995

H. Sofia Pinto. (1999). Towards Ontology Reuse. From: AAAI Technical Report WS-99-13

N. Shadbolt, T. Berners-Lee and W. Hall. (2006). The Semantic Web Revisited. In IEEE

Intelligent Systems, vol. 21, no. 3, pp. 96-101.

S. Staab, R. Studer, H. -. Schnurr and Y. Sure. (2001). Knowledge processes and

ontologies. In IEEE Intelligent Systems, vol. 16, no. 1, pp. 26-34.

C. Bizer. (2009). The Emerging Web of Linked Data. In IEEE Intelligent Systems, vol. 24,

no. 5, pp. 87-92

A. Freitas, E. Curry, J. G. Oliveira and S. O'Riain. (2012). Querying Heterogeneous

Datasets on the Linked Data Web: Challenges, Approaches, and Trends. In IEEE Internet

Computing, vol. 16, no. 1, pp. 24-33

C. Bezerra, F. Freitas and F. Santana. (2013). Evaluating Ontologies with Competency

Questions. In IEEE/WIC/ACM International Joint Conferences on Web Intelligence (WI)

and Intelligent Agent Technologies (IAT), Atlanta, GA, pp. 284-285.

Pinto, H. & Martins, J. (2004). Ontologies: How can They be Built?. In Knowledge and

Information-Systems, pp. 441-464, https://doi.org/10.1007/s10115-003-0138-1

Deliverable 3.1. Metadata Model - ICT Biochain€¦ · Deliverable 3.1. Metadata Model Page 11 of...

Documents

Transcript of Deliverable 3.1. Metadata Model - ICT Biochain€¦ · Deliverable 3.1. Metadata Model Page 11 of...