introduction and actual use of state of the art technologies (Ubiquitous
Learning, Mobile Learning, Internet of Things). European countries need as
potential employees youngsters who are able to think creatively, apply new
knowledge in an effective way, become continuously competitive in a highly
demanding working environment through constant self-monitoring and thus be
able to stand up for all the challenges that work based learning brings. The
ability to switch efficiently between different disciplines such as STEM
disciplines depends on processing effectively the educational material based
on clearly defined outcomes, expanding a broad repertoire of ICT
communication, problem-solving and decision-making skills, and using the
collective knowledge represented in networks, based on working environments.
_The orientation of UMI-Sci–Ed is entrepreneurial and multidisciplinary in an
effort to raise young boys’ and girls’ motivation in science education and to
increase their prospects in choosing a career in pervasive, mobile computing
and IoT (UMI)._

Under this scope, the project should deliver meta-level solutions to link
school, community and third-level initiatives together and should foster a
model that looks to strongly broaden impacts from the current cohort (e.g.
students competing in STEM/UMI competitions) to the entire ‘education’
population. The most effective way to do this will be to build communities of
practice (CoPs) within active clusters where a body of knowledge already
exists. The project should also provide tools, particularly technology, to
support this; however, the creation of this toolset should empower the
stakeholder group and this should be considered carefully. New technology is
often rejected, so approaches where participants can help co-create the
toolkit should be prioritised. In this context adopting a ‘making’ culture may
prove highly beneficial and a productive way of building a tangible bridge
between theory and action; it could foster pilots that enable exploration and
validation of technical, pedagogical and community-based innovation
approaches.

In order to achieve the abovementioned, this project investigates important
parameters on the introduction of UMI technologies in science education
supported by the implementation of a CoPs format. By carefully exploiting
state of the art technologies in order to design educational tools and
activities, the project aims to offer novel educational services by
implementing innovative pedagogies so as to enhance students’ and teachers’
creativity, socialisation and scientific citizenship. We aim to develop an
integrated yet open fully integrated training environment for 14-16 years old
students based on a selection of methodological processes and UMI
applications. The training environment will consist of an open repository of
educational material, educational means, training activities, a platform to
support CoPs through socialization, delivery specific of educational material,
entrepreneurship training, showcases, self-evaluation, mentoring, and
conceptualisation of content and information management. This project’s core
objectives are the following:

**O1 Novel educational services:** To develop a training mechanism, as a
methodology, for young students, containing guidelines for UMI learning under
the CoPs format, roles and structures.

**O2 Career consultancy services:** To foster innovation and support promising
scientific careers. The career consultancy will be carried out by conducting a
series of piloting UMI-SciEd activities and scenarios using CoPs and UMI. It
includes linking the market needs to the project stakeholders through the
platform, formation and management of CoPs using social computing tools and
adaptation of specific, specially selected technological tools used for
establishing CoPs.

**O3 Supporting software tools:** To design and implement an integrated
learning environment which shall actually support all stakeholders to form
CoPs as a facilitating mechanism for UMI learning in the science education.

**O4 Supporting hardware tools:** To integrate, package and delivery a
necessary hardware kit to support training and to develop the accompanied
programming environment allowing the interaction with the hardware kit and
supporting young students to realize their ideas from the beginning of their
training.

**O5 Dissemination of the project ideas and results:** To disseminate the use
of UMI technologies in real educational settings and promote their added
pedagogical value to youngsters (male and female) in science education mostly
but alternatively also in emerging disciplines of STEM (Technology,
Engineering, Mathematics) and to convey project scientific achievements and
RTD results both internally among project partners and externally to European
and International research communities, potential users and
industrial/commercial organizations.

**Rationale and changes introduced in DMP revision**

The first objective of initial DMP was to define and classify the most
important datasets that will be produced and exchanged throughout the lifetime
of the project among project partners and participants. As such, four datasets
have been defined, i.e., _Educational Scenarios Derivatives_ , _Research data_
, _Educational material_ and _Platform & market analysis data _ . A
description of these datasets has been given to the best possible extent.
However, as noted in section 1.3 of DMP v1.0, with only a preliminary design
and development of the UMI-Sci-Ed project platform (which consists the major
means of project data collection, generation and exchange) in hand, several
issues regarding the collection, organisation and presentation of data could
not be accurately predicted and major decisions had to be made for several
aspects of data management. On the other hand, while the datasets were
correctly defined, the definition and development of educational scenarios and
the evaluation framework that will drive the educational activities and the
main educational research directions, respectively, were not yet mature enough
in order to fully specify the data types and the metadata that are important
for the project and the research activities involved. Last, but not least, the
initial DMP development followed the Horizon 2020 directions available at the
beginning of the project and was based on DMP online platform  2  provided by
Data Curation Centre (DCC). In the meantime, Horizon 2020 released a new
template  3  as well as new guidelines on Open Access  4  ]. Taking into
account the abovementioned issues, together with several decisions that were
made by the consortium in the meantime, a major revision of the initial DMP
was necessary. Overall, the DMP has been revised in the following major
aspects:

  * The initial datasets have been enriched with two more datasets. In specific: _DS5 Project working data_ is introduced in order to keep track and of internal working documents, that were decided to be circumvented through the _Filedepot_ feature of the project platform; _DS6 - Other data_ is introduced in order to include all other data that will be exchanged through the project platform that cannot be classified in one of the rest datasets. 

  

  * Each of the datasets, either new or existent in the DMP v1.0 has been described in accordance with the project platform content types. Data curation and preservation methods have been fully clarified and Zenodo has been decided to be used as a repository of research data. 

  

  * A set of metadata has been defined for each of the most important platform content types based on the LRMI/DCMI specification following the Schema.org metadata structure. 

  

  * The DMP has been rewritten following the new template provided by Horizon 2020. 

  

**DMP as a living document: Next steps**

The revised DMP described in this deliverable can be considered as a
consistent and mature plan for data management. However, as clearly described
above, the vast majority of data is going to be collected, generated and
exchanged via the project platform. The project platform on the other hand is
going to be enriched, change and expand, according to the needs and results of
research activities that will lead to accomplishment of the project
objectives. Therefore, the DMP is going to evolve in conjunction with the
project platform and the project, as a whole, evolution. In this context,
while the major decisions regarding the DMP have been already made, several
issues will need reconsideration, revision and improvement. The next important
step is the conclusion and evaluation of the local pilots phase (T6.2). This
will provide a compact base of data as well as significant experience of the
detailed utilisation of the platform that will drive the next steps of the
platform implementation and the research methods to be subsequently followed.
As such, it is expected that several decisions and specifications included in
this document regarding the data and metadata management will be revised
accordingly.

  1. **Data Summary**

    1. **Introduction**

  
  

  

  

UMI-Sci-Ed is going to generate, use, circulate and disseminate a big amount
of diverse data. These include data that will support the educational and
training activities, the artefacts and derivatives of the piloting and
implementation phases, data that will drive the research process that will
take place in the context of the project, etc. These data will be both
qualitative and quantitative and may either be automatically or manually
generated. The origin will differ substantially, e.g., data will be generated
by the participants to the educational activities (e.g., students, tutors,
researchers, project members or professionals), researchers that will process
and analyse the activities and data created in the context of the educational
scenarios implementation, sensors or other artefacts producing data in the
context of the pilot and implementation phases as well as the UMI-Sci-Ed
platform itself. Furthermore, it is clear that the generated data will follow
different formats and standards due their diverse nature and post-processing
requirements. Almost all types of data will be managed through the UMI-Sci-Ed
platform  5  that has been created in order to support the activities that
will be realized in the context of the project.

Aiming to provide easy access and processing capabilities, the consortium
revised the original dataset categories with respect to the data that will be
generated throughout the project from four (4) to six (6). In addition to the
datasets described in the DMP v1.0, two more datasets have been introduced,
namely, the _Project working data_ and the _Other data_ . The main idea behind
this categorisation is the provision of a simple structure while keeping the
major relevant data collections compact, in terms of the origin of creation,
and the postprocessing that will be applied to the data collections. In
specific, the six datasets are:

  * **_DS1: Educational scenarios derivatives._ ** This is a family of datasets that will contain all the raw or processed data that will be generated during the execution of the pilots as learning artefacts, mainly by the students and the tutors. Each educational scenario will eventually have its own dataset. 

  

  * _**DS2: Research data.** _ This dataset will include all the quantitative and qualitative data (pre- and post-processed questionnaires, reflections, evaluations, etc.) that will support educational research. 

  

  * _**DS3: Educational material.** _ This dataset will include all the educational material that will be developed by the partners, tutors, professionals, etc. that will participate in the preparation of the educational scenarios and the pilots. 

  

  * _**DS4: Platform and market analysis data.** _ This dataset will include information about the usage of the platform that will be developed in the context of the project in the form of log files and evaluation forms as well as overall evaluation data that will be used for market analysis and exploitation. 

  

  * _**DS5: Project working data.** _ This dataset includes working documents in the context of the project, such as presentations, draft deliverable documents, deliverable review documents, etc. 

  

  * _**DS6: Other data.** _ This dataset includes other types of information that will be gathered in the UMI-Sci-Ed platform throughout the project that cannot be categorized in one of the above datasets. 

  

The UMI-Sci-Ed platform that hosts the above mentioned data has been organised
in specific content types to support the activities of the project, as
described in D4.2. These include _UMI Scenario_ , _UMI Project_ , _Group
Article_ , _Repository Entry_ 6  , _Blog_ , _Survey_ , _Wiki_ , _Forum Topic_
, _Poll_ , and _Event_ . In addition, a _Filedepot_ is included in the
platform that supports information exchange among project partners. In the
following section, each of six datasets is described separately, in relation
with the above-mentioned content types, following the guidelines of the H2020
template for DMP [2].

  2. **Datasets description**

  

  

**1.2.1 DS1: Educational scenarios derivatives**

This is a family of datasets containing the raw or assembled and processed
intermediate or final data that will be created by the participants as
learning artefacts during the pilots that will take place within WP6 (Tasks
6.2 and 6.3). This kind of data will be mainly generated and collected in the
context of UMI projects ( _UMI Project_ content type) that will implement the
predefined educational scenarios (UMI scenarios), that is, the basis of the
above mentioned activities. However, relevant data can be uploaded in the
_Blog_ , _Forum Topic_ , _Survey_ , etc. content types that are related to UMI
projects.

The data of this dataset will be generated manually by students and tutors or
automatically by UDOO devices themselves running pieces of codes created by
the participants. UMI-SciEd partners and researchers may also create data,
e.g., during demonstration or dissemination activities.

The dataset may comprise software code (e.g. programs for managing
experiments, programs for building hardware), data produced by running
experiments or building solutions, student reports, etc., following several
diverse formats, e.g., text, images, audio, video, scripts, numerical
(spreadsheet) and binary sensor data, etc. Open and/or wellestablished format
standards will be considered and used as first options to guarantee easy
exchange and processing using non-proprietary software. Customised format
standards might also be used if necessary for the execution of the UMI
projects; in such case, documentation and/or open source software tools to
access the data will be released too. Available standards describing raw data
from sensors such as Sensor Model Language (SML) and Sensor Observation
Service (SOS) will be examined for adoption in the project. The data size
cannot be predicted yet since it depends on the level of participation of
students and their tutors. However, there is no restriction posed by technical
or administrative issues.

Data of this dataset may be categorized as raw data and processed data. Raw
data represent all the artefacts of the students’ activities that take place
with the use of UDOO devices. Processed data represent all material
(documents, statistics, reports, etc.) that will be generated by the students
after processing the raw data in cases that such processing is required in the
UMI scenarios and UMI projects.

The main purpose of these datasets is to support the activities of the
students and tutors during the realisation of UMI projects and to allow groups
and CoPs interaction when working on the same UMI project. In addition,
specific samples of these data may be used to support research reasoning and
outcomes or proof of concept and applicability of the UMISci-Ed platform and
hardware devices. Therefore, they are closely related with O1, O3 and O4
objectives and they will be used as input to the assessment of the training
methodology, the UMI-Sci-Ed platform, and the UDOO hardware kit, respectively,
that are under development in the context of the project.

**1.2.2 DS2: Research data**

This is a data set containing the research data that will be collected during
the UMI projects realisation (implementation of the UMI scenarios) in the
classroom (T6.2 and T6.3), the CoPs study and evaluation phases (T2.3 and
T2.4) as well as overall evaluation phase (T7.2 and T7.3). The data will
mainly be collected through the _Survey_ or _Poll_ content types of the
platform and may be exchanged (in aggregated and anonymised format) through
the _Group Article_ , _Repository Entry_ content types and the _Filedepot_ .
_UMI Scenario_ contents can be used in research activities as well.

Each pilot study will produce a number of different files including both
qualitative and quantitative data. Indicative information to be collected is
as follows:

  * Pilot/workshop information (goals, hardware kits, programming language, group formation, success criteria, Gantt charts etc.) 

  

  * Project partners responsible for the pilot/workshop, demographic information of participants (age, gender, etc.), tutors/mentors information. 

  

  * Video/audio recordings, log interactions and observations. 

  

  * Student assessments. 

  

  * Tutors' reflections. 

  

  * Corporate sector feedback. 

  

  * Interviews with the participants (students, tutors, parents, etc.). 

  

  * Different questionnaires addressed to participants (students, tutors, researchers) for collecting qualitative and quantitative data before, during and after the project activities performed in the context of the pilots/workshops. 

  

The above mentioned generated data will mainly be used in the context of
research activities of UMI-Sci-Ed, including assessment of novel educational
services, evaluation of software and hardware tools, as well as dissemination
of the project ideas and results, as described in O1, O3, O4, and O5
objectives of the project, respectively. Therefore, they will support and
accompany publications (which by default are included in this dataset as
well). In this context, these data will be useful for researchers within the
framework of UMI-Sci-Ed, as well as external researchers that are active in
similar or complementary research areas. Existing data by previous research
efforts (out of the context of the project) may be used and analysed in order
to provide comparative results.

Several data formats will be necessary to support the research and evaluation
process including, but not restricted to, text, spreadsheets and audio/video.
Open and/or wellestablished format standards will be considered and used as
first options to guarantee easy exchange of the information. Estimation of the
generated data volume cannot be made since it depends on the activities of
project partners. However, there is no restriction posed by technical or
administrative issues.

**1.2.3 DS3: Educational material**

This dataset contains the educational material and resources that will be
developed in the context of tasks T2.2, T5.2 and T6.1 in order to support the
pilots. The dataset will include two general types of educational material,
i.e., material to be used by the tutors and material to be used by the
students. The material will either be developed by the consortium partners
participating in educational activities, external stakeholders and
professionals as well as the tutors themselves, or it is already available (by
organisations outside the framework of UMI-Sci-Ed) and will be redistributed,
mainly in the form of URLs. The educational material will mainly be available
through the _UMI Scenario_ , _UMI Project_ , _Repository Entry_ , _UMI Forum
Topic_ , and _Wiki_ content types of the UMI-Sci-Ed platform. While the
educational material is mainly intended to be used by the target groups of the
project, i.e., tutors and students in the context of UMI-Sci-Ed as well as the
general public, some material will support research efforts and publications
as well. Indicative information to be generated and distributed includes:

  * Educational (UMI) Scenarios' detailed descriptions including activity plans, session/lesson plans hardware/software to be used, etc. 

  

  * Supporting documentation and presentations for UDOO devices. 

  

  * Guidelines, templates, handouts, instructive videos, presentations and documentation for the scientific topics under consideration in the UMI Scenarios and UMI Projects. 

  

From the above description, it is evident that this dataset is mainly related
to O1 and O2 UMI-Sci-Ed objectives that deal with novel educational services
development and career consultancy services support. The data generated and
distributed can be of audio, video, document, presentation and other types.
Common and well-established formats will be used to guarantee easy exchange
and processing. The expected size of data cannot be estimated since it depends
on the productivity of the project participants and partners. However, there
is no restriction posed by technical or administrative issues.

**1.2.4 DS4: Platform and market analysis data**

The purpose of this dataset is to provide information about the usage of the
UMI-Sci-Ed platform as well as general evaluation of the project and the
offered services. Data to be collected can be categorized in two major parts,
that is, log files and evaluation data. Both will include information
regarding

  * user info (e.g., ID or name for registered users, submitted info by unregistered users) 

  

  * user category (according to the actors that will be defined in the specifications of the platform) 

  

  * date/time 

  

  * visiting duration 

  

  * visited pages/tools 

  

  * platform and overall services evaluation data (through evaluation forms that will be defined in the specifications of the platform) as well as questionnaires and interviews for the services offered in general by the project. 

  

Platform usage log data will be collected automatically by the platform via
proper software modules as text files (.csv or .xml) while evaluation data
will be provided by the interaction of the users with the platform through
proper evaluation forms and questionnaires that will be processed to provide
spreadsheets or numerical tables. Furthermore, interviews (as audio or video
files) may be required to collect qualitative data. These data will be
properly aggregated in order (a) to get feedback for the quality of services
that the platform and the project (as a whole) offers to the users, (b) to
measure the visibility of the project, and (c) to be combined with other data
in order to draw conclusions in educational research, drive market analysis
and subsequent exploitation plans in the context of Task 8.3. Therefore, this
dataset’s data will be useful for the consortium in the context of the O3 and
O5 UMI-Sci-Ed objectives that are related to the supporting software tools
assessment and the dissemination of the project ideas and results,
respectively.

The data size cannot be predicted since it has to do with the visibility and
utilisation of the UMI-Sci-Ed platform throughout and after the project.
However, there is no restriction posed by technical or administrative issues.

**1.2.5 DS5: Project working data**

This dataset includes working documents in the context of the project, such as
draft deliverable documents, deliverable evaluation forms, deliverable
revisions, progress reports, presentations, meeting minutes, etc., as well as
other auxiliary material, that are created and exchanged through the UMI-Sci-
Ed platform _Filedepot_ by the project partners in order to fulfil the typical
project requirements. Thus, this dataset is related with all the objectives of
the project and is used for monitoring the activities and progress of the
project as a whole. It mainly consists of text files or presentations;
however, other data types may be occasionally used, in well-established
formats that have been agreed among the partners.

**1.2.6 DS6: Other data**

This dataset includes other types of information that will be gathered in the
UMI-Sci-Ed platform by any registered user throughout the project and cannot
be categorised in one of the _DS1_ \- _DS5_ datasets while still relevant and
useful for the project, e.g., forum and blog discussions, announcements, etc.
This dataset includes, in general, auxiliary data that are exchanged among the
platform users in the context of educational scenarios/projects design and
implementation and can be of any type. Their size depends on the utilisation
of the platform throughout the project. They are not directly connected with
the objectives of the project, however post-processing of them may be useful
in qualitative analysis that could be used in research efforts of the project
partners.

**1.3 Datasets and UMI-Sci-Ed platform relations**

The plurality and diversity of data that will be generated, gathered and
exchanged through the UMI-Sci-Ed platform, as described in the previous
section, make their classification and organisation a rather involved task.
Furthermore, the platform, tools and methods are expected to be updated,
expanded or shrunk in several aspects in order to support effectively the
CoPs’ and educational activities throughout the duration of the project.
Therefore, while the described datasets seem to cover the data that will be
gathered in the framework of the project, the described in sections 1.1 and
1.2 relations between the platform content types and datasets, i.e., in which
content types the _DS1_ \- _DS6_ data are expected to be uploaded, may change.
In order to ease the presentation and keep track of the changes that may be
necessary in the future, Table 1 provides the platform content types that will
be used for collecting or exchanging data of the defined datasets.  
  
<table>  
<tr>  
<th>

**Content Type**

</th>  
<th>

**DS1: Educational scenarios derivatives**

</th>  
<th>

**DS2: Research data**

</th>  
<th>

**DS3: Educational material**

</th>  
<th>

**DS4: Platform and market analysis data**

</th>  
<th>

**DS5:**

**Project working data**

</th>  
<th>

**DS6:**

**Other Data**

</th> </tr>  
<tr>  
<td>

**UMI Scenario**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**UMI Project**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Group Article**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td> </tr>  
<tr>  
<td>

**Repository Entry**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Forum Topic**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td> </tr>  
<tr>  
<td>

**Blog**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td> </tr>  
<tr>  
<td>

**Survey**

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Poll**

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Wiki**

</td>  
<td>

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Filedepot**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

×

</td>  
<td>

</td> </tr> </table>

**Table 1 Datasets and UMI-Sci-Ed platform content types relation**

  2. **Fair Data**

  

  

**2.1 Making data findable, including provisions for metadata**

The UMI-Sci-Ed platform is the major place of data collection and presentation
either raw or processed data of the project. Additionally, publications and
relative research data will be uploaded to Zenodo ( _https://zenodo.org/_ ) in
order to expand visibility. All data of the content types described in Chapter
1 that are uploaded in the project platform, including attachments, have a
unique and persistent identifier of URI type that is automatically generated
by the platform. Research data uploaded to Zenodo will also have a unique DOI
provided by Zenodo platform.

A first set of metadata has been declared for each of the content types of the
platform focusing in educational research while general metadata are also
going to be generated. The specific set for each content type has been decided
as a compromise between a full descriptive set of metadata for educational
research and low requirements of user input, so that to avoid end user
dissatisfaction that will prevent users from using the platform. Therefore,
_UMI Scenario_ and _UMI Project_ content types that are basically developed by
project partners require a significant set of metadata (provided by user
input) during the setup of a scenario or a project. In all other cases user
input related to metadata has been minimised.

Following the same principle, attachments in the platform are classified in
two major categories: attachments including educational material that supports
educational scenarios and activities under the _UMI Scenario_ content type and
attachments for all other content types. In the former case, educational
material is classified in 5 categories, that is, Source Code, URL, Digital
Document, Media Object and Rich Text, each one accompanied by a detailed set
of metadata that will be generated either by user input or automatically by
the platform. In the latter case, attachments are categorized as file
attachments, image/photos and YouTube videos and are accompanied by a minimum
set of metadata that will be generated by user input in order to ease file and
media exchange.

The metadata schema for educational research in the framework of the project
will follow the Learning Resource Metadata Initiative (LRMI) version 1.1 of
Dublin Core Metadata Initiative (DCMI)  7  , properly adapted and expanded to
fulfil the needs of the project. Table 2 provides the properties of
_Schema.org/CreativeWork_ that were adopted from LRMI specification, new
properties introduced, the metadata collection method in the platform and some
clarifying comments. Table 3 summarizes the use of _AlignmentObject_ type and
its properties by providing specific examples and value sets that are going to
be used as a basis for detailed metadata in the context of educational
research. A new set of values has been defined in addition to the recommended
by LRMI 1.1 values for the _alignmentType_ property. These are going to be
used primarily with _UMI Scenario_ and secondarily with _UMI Project_ content
types and are expected to enhance discoverability and reusability of UMI-Sci-
Ed data.

The preliminary set of metadata that has been specified for the most important
content types of the project platform is presented in detail in Appendix A.
All metadata are saved in the platform following Schema.org  8  structure.
Metadata and their value sets are going to be finalised after the local
pilots’ period (T6.2) based on the evaluation of the data that will be
gathered.  
  
<table>  
<tr>  
<th>

**Property**

</th>  
<th>

**LRMI**

</th>  
<th>

**New**

</th>  
<th>

**Generation method**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**educationalAlignment**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

User input

</td>  
<td>

This property is of _schema.org/AlignmentObject_ type which is further
described in Table 3.

</td> </tr>  
<tr>  
<td>

**educationalUse**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

Automatically by the platform

</td>  
<td>

“Educational scenario plan” and

“Educational scenario implementation” are the values used for _UMI Scenario_
and _UMI Project_ content types in the context of UMI-Sci-Ed. The value set
may be revised according to UMI-Sci-Ed future needs.

</td> </tr>  
<tr>  
<td>

**timeRequired**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

User input

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**typicalAgeRange**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

Automatically by the platform

</td>  
<td>

Value depends on the _educationalRole_ value and may be “14-16” for “learner”
or “22-” for other values.

</td> </tr>  
<tr>  
<td>

**interactivityType**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

User input or automatically by the platform

</td>  
<td>

Generation method depends on the platform content type.

</td> </tr>  
<tr>  
<td>

**learningResourceType**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

User input or automatically by the platform

</td>  
<td>

Specific content types have predefined values.

</td> </tr>  
<tr>  
<td>

**artefactType**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

User input

</td>  
<td>

A new property that provides means for characterization of learning artefacts.

</td> </tr>  
<tr>  
<td>

**licence**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

User input

</td>  
<td>

This corresponds to the LRMI property useRightsUrl as defined in Schema.org

</td> </tr>  
<tr>  
<td>

**educationalRole**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

User input

</td>  
<td>

This is a property of

_schema.org/EducationalAudience_ type and includes the values “learner”,
“teacher”, “author”, “manager”, as specified in IEEE LOM. It is mainly used
for _UMI Scenario_ and _UMI Project_ content types.

</td> </tr> </table>

#  Table 2 LRMI properties adopted in UMI-Sci-Ed

_UMI Scenario_ , _UMI Project_ , _Group Article_ , _Repository Entry_ , _Blog_
, _Wiki_ and _Forum Topic_ content types, include a mandatory field for Key
Terms or Tags. All of them will be mapped to
_schema.org/CreativeWork:keywords_ property for metadata generation.
Therefore, all datasets (see Table 1) will be accompanied by keywords.
Keywords are available as a list (autocomplete feature) while typing new key
terms or tags in the abovementioned content types in order to enhance
reusability. Keywords are searchable through the main search function of the
platform.

Versioning of _UMI Scenario_ , _UMI Project_ and _Wiki_ content types is
preserved automatically by the platform. Additionally, versioning is available
for _UMI Scenario_ , _UMI Project_ and _Wiki_ content types by user input. For
file attachments, users are suggested not to delete (replace) older versions
of the same file in order to keep tracking of the file changes. Decimal
numbering with two numbers preceded by “ _v_ ” and separated by “ _._ ” will
be followed, indicating major or minor changes. For file attachments, version
may be put in the end of file name followed, optionally, by language
indication, e.g., “ _UMI-SCI-Ed CTI Scenario My Social Panel v3.1 en.docx_ ”.  
  
<table>  
<tr>  
<th>

**alignmentType value**

</th>  
<th>

**LRMI**

</th>  
<th>

**New**

</th>  
<th>

**educationalFramework value or example**

</th>  
<th>

**targetName value set or example**

</th> </tr>  
<tr>  
<td>

**“learningOutcomes”**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

Ex: “Revised Bloom Taxonomy”

</td>  
<td>

Ex: “Describe a simple local area computer network”

</td> </tr>  
<tr>  
<td>

**“educationalLevel”**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

Ex: “Greek upper secondary school”

</td>  
<td>

Ex: “year 10 (on K-12 scale)”

</td> </tr>  
<tr>  
<td>

**“educationalSubject”**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

Ex: “Greek upper secondary school”

</td>  
<td>

Ex: “Informatics’ Applications

(Curriculum 932/14-4-2014/τΒ)”

</td> </tr>  
<tr>  
<td>

**“umiDomain”**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

“Horizon 2020 UMI-Sci-Ed”

</td>  
<td>

“Ubiquitous”, “Mobile”, “IoT”

</td> </tr>  
<tr>  
<td>

**“educationalScenarioOri enation”**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

“Horizon 2020 UMI-Sci-Ed”

</td>  
<td>

“Acquire new Knowledge”,

“Develop new Skills”, “Attain

Attitudes”

</td> </tr>  
<tr>  
<td>

**“pedagogicalTheory”**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

“Horizon 2020 UMI-Sci-Ed”

</td>  
<td>

Ex: “Active Learning”

</td> </tr>  
<tr>  
<td>

**“requires”**

</td>  
<td>

×

</td>  
<td>

</td>  
<td>

“hardware resources”,

“software resources”,

“other resources”

</td>  
<td>

Ex: “Arduino IDE”

</td> </tr>  
<tr>  
<td>

**activityType**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

“Horizon 2020 UMI-Sci-Ed”

</td>  
<td>

“Introductory”, “Core”

“Concluding” or “Auxiliary”

</td> </tr>  
<tr>  
<td>

**“learningObjectives”**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

Ex: “Revised Bloom Taxonomy”

</td>  
<td>

Ex: “List UMI applications”

</td> </tr>  
<tr>  
<td>

**“difficulty”**

</td>  
<td>

</td>  
<td>

×

</td>  
<td>

“IEEE LOM 5.8”

</td>  
<td>

“Easy”, “Intermediate” or

“Advanced”

</td> </tr> </table>

#  Table 3 Properties of Schema.org/Intangible/AlignmentObject used in UMI-
Sci-Ed

**2.2 Making data openly accessible**

All data will be generated or collected via the UMI-Sci-Ed platform and will
be made openly available to registered users with the following exceptions due
to legal and contractual reasons:

  1. Raw educational research data (part of _DS1_ dataset), i.e., survey and poll answers, interviews, observation notes, etc., that include or may collectively reveal the identity of student participants. This kind of data will be properly anonymised before use allowing information on demographic characteristics (e.g., age, gender) of students only (see Chapter 5). 

  

  2. Raw platform use log data ( _DS4_ dataset) or platform survey and evaluation data that include sensitive personal information of users. These data will be accessible only to 

  

  

the platform administrator and available only to officially authorised
persons. They may be released to the consortium partners for processing and
evaluation after anonymisation or exclusive permission of the steering
committee upon a fully justified request. These data are not going to be
shared outside the project consortium in any case (see also Chapter 5).

  3. Files uploaded to _Filedepot_ which are by default created and exchanged between the project partners for internal use only. 

  

  4. Any data that are related to business activities and goals of corporate consortium partners. 

  

  

Furthermore, registered users that participate in a Group (supporting CoPs’
activities) have the capability to restrict specific types of the platform
content to Group visibility only, as described in deliverable “D4.2 –
Intermediate version of the system”.

All data will be available through UMI-Sci-Ed platform after registration. In
addition, research or platform data ( _DS2_ and _DS4_ datasets) supporting
publications (as well as the publications themselves) will be openly available
in Zenodo, after proper anonymisation, as described in (a) and (b) above. No
special methods or tools are necessary to access the data with the exception
of UDOO sensor data that will be gathered when implementing educational
scenarios. The necessary software will be available in open-source code and
will be accessible with a special link via the UMI-Sci-Ed platform.

All data will be deposited in CTI servers dedicated to the project and
accessed through the UMI-Sci-Ed platform. In addition, publications and
accompanying data will be deposited to Zenodo and other institutional/national
databases. Access to UMI-Sci-Ed platform is provided according to deliverable
“D4.1 – System Requirements and Architectural Design”. The platform
administrator can additionally provide massive access to data (either via the
platform or directly to CTI servers) to consortium members, the project
officer and the reviewers, after registration to the platform and proper
consent of the project coordinator. All registered users are uniquely
identifiable by the platform.

  3. **Making data interoperable**

  

  

The data that will be produced during the project and will be publicly made
available will follow well-established and massively used format standards,
open as much as possible, with preference to .csv, .pdf, .xml, .png, .jpeg
formats. This will allow reusability between researchers, institutions and
organisations not participating in the project consortium.

Data and metadata vocabularies, as described in section 2.1 especially for
educational research purposes, as well as with commonly used metadata for the
platform content, as described in Schema.org, will offer enhanced
interoperability and inter-disciplinary use. A preliminary set of the planned
metadata and vocabularies for the content types of the platform are provided
in detail in Appendix A.

  4. **Increase data re-use (through clarifying licences)**

  

  

Data produced by the project will be available through the platform or
published on Zenodo platform under a Creative Common (CC)  9  proper license.
In this context, _UMI Scenario_ , _UMI Project_ and _Repository Entry_ content
types, include a license field to be filled by the user (as a list of
available CC licensing types) that applies to all the content included in them
as well. Research data and publications will follow the same procedure in
Zenodo.

All data that are viewable by registered users of the platform or uploaded in
Zenodo or are accessible via the project web site  10  are considered to be
available for re-use by third parties by the moment they are made available in
public. No embargo period will be applied. Re-use of data is restricted only
when they are related to business activities and goals of corporate consortium
partners. Data will be and remain re-usable for a minimum time of two (2)
years after the end of the project. The project partners will decide which
data will be preserved for a longer period by the end of the project.

Raw data processing, aggregation and presentation for research activities will
take place following standardised methodologies and tools as described in
detail in deliverable “D7.1 – Evaluation concept-framework and piloting” in
order to assure processed data quality. Data related to deliverables and
project reporting follow the predefined by the project document control
special procedure that includes: (a) Use of predefined and agreed templates,
(b) Review and revision process and (c) Approval from the steering committee.
Raw and processed data will be kept in the platform and archived to CTI
servers following standardised procedures that guarantee data integrity. A
short description of the infrastructure, software and procedures used can be
found in Chapter 4.

  3. **Allocation of resources**

  

  

The costs for making the data FAIR have been pre-allocated as part of Horizon
2020 grant in the context of Work Package 1 (Project management). No extra
costs will be necessary for platform data curation and preservation during the
project and for a period of two (2) years after the end of the project.
Research data uploaded to Zenodo will not require extra costs. The project
partners (through the Steering Committee) will decide what platform data will
require longer term preservation. These data may be uploaded to Zenodo as well
(depending on data volume) at no cost. Otherwise extra costs will burden CTI
which is responsible for the maintenance of the platform and the project
servers.

CTI is responsible for data management. The platform administrator and the
project coordinator (both in CTI) are the key persons for data management
during the project. Furthermore, the coordinator of each partner is
responsible for any data (intended to be scant or none) that are locally kept
by the project partners outside the project platform.

  4. **Data security**

  

  

All data will be stored and preserved in CTI project servers. UMI-Sci-Ed
platform is running on a server with Ubuntu 16.04 LTS operating system
installed. LTS stands for “Long Term Support” and it means that Canonical (the
company behind Ubuntu) provides support (security updates etc) for at least 5
years. As a web server, we have installed the latest version of Apache web
server with PHP 7.0 and as database server UMI-Sci-Ed platform stores the data
to the latest version of MySQL Server Community Edition.

For better resources management and allocation, we use virtualization
technologies in our servers. Regarding the project, UMI-Sci-Ed server is a
virtual machine that runs on an ESXi infrastructure. The bare metal ESXi
server runs on a Dell R430 machine with redundant power supply and redundant
hard disk drives (SAS HDD – RAID1).

The physical location of the server is CTI’s computer room. Our computer room
is equipped with UPS systems, systems that maintain the temperature and the
humidity levels inside the computer room and special fire suspension systems
(Waterless Fire Suppressant). Finally, only authorized personnel can access
the computer room by using personal ID cards. Also, any entrance to the
computer room is logged and the entrance is video recorded 24/7.

For the backup of UMI-Sci-Ed server, we use one extra, independent server
(backup server). Our backup plan is executed daily at 2:00 and we keep 60
restore points. This means that we can restore any instance of UMI-Sci-ed
server 60 from the past 60 days. All backups are created and transferred to
the backup server via a secure connection.

UMI-Sci-Ed development team checks in a regular basis servers’ system logs and
ensures that all the necessary system updates are installed in our servers.
Furthermore, CTI’s cyber security department monitors daily the internet
traffic from/to CTI’s network to prevent any malicious actions, attempts for
unauthorized access etc.

Finally, as noted in Chapter 3, for longer than 2 years after the end of the
project preservation, properly selected sets of data (that include research
data) will be deposited to Zenodo.

  5. **Ethical aspects**

  

  

The project meets national legal and ethical requirements of the partners’
countries. The project will not study vulnerable populations. No sensitive
personal data will be recorded. As we are interested in UMI/STEM use and
career potential of both genders, gender of participating students and tutors
will be probably recorded, but in anonymous questionnaires, with general
descriptors like country, school name, geographic region, as well as opinion
about project actions, etc. In spite of being sensitive, all collected data
will be treated with care and respect, and only the results of their
processing will be published. However, whenever personal data collection is
required, this will be made with the explicit written consent of the
individuals involved. Especially for children (which are unable to give
informed consent), the consortium has already provided compliance with the
ethical standards and guidelines of Horizon 2020 (Annex 1, DoA, part B,
section 5.1, p. 76). The description and the justification of the methodology
adopted and the composition of the sample are provided in Chapter 2 (sections
2.1 and 2.2) of deliverable “D9.2 – H - Requirement No. 1”. Furthermore,
detailed information on the informed consent procedures that will be
implemented regarding the participation of humans, as well as clarifications
on how assent will be ensured for children is provided in section 2.3 of D9.2.

More specifically, among the datasets under consideration in Chapter 1, _DS3_
and _DS5_ , educational material and project working data, do not, by
definition, include personal student data. Other auxiliary data falling in
_DS6_ , on the other hand, are unlikely to carry personal student data. Major
importance for ethical aspects is data collected as part of _DS2_ and _DS4_
datasets, i.e., research and platform data, respectively. For _DS2_ , all data
will be stored without any reference to the student interacting with the
platform and will be password protected. In the case of the tutors collecting
or generating information (interviews, assessments, reflections, etc.), the
information will be directly stored to the platform via proper forms with no
reference to student personal data. In all the abovementioned cases, only
demographic student data will be stored (e.g., gender, age) and will be
password protected. Following the same strategy, _DS4_ data including platform
log files will be encrypted, statistically processed and aggregated to ensure
anonymity. Aggregated and anonymised data may be shared within the consortium
and may be made publicly available when they support research publications via
the CTI platform and Zenodo. Finally, for _DS1_ data that include educational
derivatives, the original intention of the project was to anonymise all
learning artefacts created by students with reference only to groups and not
the individuals. In this context, artefacts that inevitably contain personal
student data (i.e., not fully anonymised) will be marked as sensitive and will
be password protected and/or encrypted. However, this last case will be
further examined by the consortium in cooperation with local tutors in the
context of providing recognition (visible for the members of the Cops) to
active students. Further information on ethical aspects and relative
procedures can be found in deliverables “D9.1 – POPD - Requirement No. 2” and
“ D7.1 – Evaluation concept-framework and piloting”.

Finally, the educational material will include a section about plagiarism,
code of ethics, and plain advice on how could students properly avoid it by
properly referencing their sources.

  6. **Other**

  

  

No other national/funder/sectorial/departmental procedure for data management
will be used.

**Appendix A: Metadata tables for UMI-Sci-Ed platform content types**

This section provides the preliminary set of metadata that have been specified
for the _UMI Scenario_ , _UMI Project_ , _Group Article_ , _Wiki_ , _Blog_ ,
_Forum Topic_ and _Repository Entry_ content types of the platform.
Furthermore, the set of metadata that are kept in case of _Files and Media_
attachments to the above content types (excluding UMI Scenario that includes a
special set of metadata for attachments) is also given. It has to be noted
that the tables given below may undergo changes after the local small scale
pilots, in order to better support the objectives of the project and the
usability of the project platform.

Table 4 shows the metadata that have been specified for the main parameters of
_UMI Scenario_ content type together with the mandatory attached file. The
table includes the metadata property and the type of metadata according to
Schema.org, the value space, the platform field that the platform user
utilizes for input and some comments (when necessary). An empty platform field
indicates that metadata are created automatically without any user input. Each
educational scenario (that corresponds to _UMI Scenario_ content type)
includes a set of activities that are supported by their own set of metadata.
The set of metadata defined for the activity are presented in Table 5. Each
activity can further include several types of educational material, i.e.,
pieces of source code, URLs, digital documents (text, presentation or
spreadsheet), media objects, or rich text parts. The corresponding set of
metadata is not included here for brevity.

Tables 6, 7, 8, 9, 10 and 11 present the metadata that have been specified for
_UMI Project_ , _Group Article_ , _Wiki_ , _Blog_ (including both the blog and
a blog comment), _Forum Topic_ (including both the forum topic and a Forum
Post) and _Repository Entry_ content types.

_Files and Media_ attachments may be files, YouTube videos (via URL) and
images or photos. Table 12 provides the metadata that have been for file
attachments.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**alternateName**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Abbreviation

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**version**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Version

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**inLanguage**

</td>  
<td>

CreativeWork

</td>  
<td>

Text, as defined in IETF BCP47

</td>  
<td>

Language

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Synopsis

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**keywords**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Key Terms

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**educationalRole**

</td>  
<td>

Ιntangible > Audience > EducationalAudience

</td>  
<td>

"teacher", "learner",

"author", "manager"

</td>  
<td>

Audience

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**audienceType**

</td>  
<td>

Intangible > Audience

</td>  
<td>

"public" or UMI Group

</td>  
<td>

Group content

visibility, Groups audience

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "learningOutcomes"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Expected Learning Outcomes

</td>  
<td>

alignmentFramework = "Revised Bloom Taxonomy"

</td> </tr>  
<tr>  
<td>

**timeRequired**

</td>  
<td>

CreativeWork

</td>  
<td>

ISO 8601

</td>  
<td>

Expected duration

</td>  
<td>

Months, days, hours, minutes

</td> </tr>  
<tr>  
<td>

**alignmentFramework**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Framework

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "educationalLevel"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Level

</td>  
<td>

alignmentFramework is defined by the field "Framework"

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "educationalSubject"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Subject

</td>  
<td>

alignmentFramework is defined by the field "Framework"

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "umiDomain"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

"Ubiquitous", "Mobile",

"IoT"

</td>  
<td>

UMI Domain

</td>  
<td>

alignmentFramework = "Horizon2020 UMI-Sci-Ed"

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType =**

**"educationalScenarioOrien ation"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

"Acquire new Knowledge",

"Develop new Skills", "Attain

Attitudes"

</td>  
<td>

UMI-Sci-Ed Orientation/Focus

</td>  
<td>

alignmentFramework = "Horizon2020 UMI-Sci-Ed"

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "pedagogicalTheory"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Pedagogical Theory

</td>  
<td>

alignmentFramework = "Horizon2020 UMI-Sci-Ed"

</td> </tr>  
<tr>  
<td>

**interactivityType = "mixed"**

</td>  
<td>

CreativeWork

</td>  
<td>

"active", "expositive" or

"mixed"

</td>  
<td>

Interactivity Type

</td>  
<td>

Only one out of the three values

</td> </tr>  
<tr>  
<td>

**targetName,**

**alignmentType = "requires"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Resources - Hardware

</td>  
<td>

alignmentFramework = "UMI-Sci-Ed hardware resources"

</td> </tr>  
<tr>  
<td>

**targetName,**

**alignmentType = "requires"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Resources - Software

</td>  
<td>

alignmentFramework = "UMI-Sci-Ed software resources"

</td> </tr>  
<tr>  
<td>

**targetName,**

**alignmentType = "requires"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Resources - Software

</td>  
<td>

alignmentFramework = "UMI-Sci-Ed other resources"

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI Scenario"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

</td>  
<td>

"UMI-Sci-Ed Educational

Scenario"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**educationalUse**

</td>  
<td>

CreativeWork

</td>  
<td>

"Educational Scenario plan"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**typicalAgeRange**

</td>  
<td>

CreativeWork

</td>  
<td>

"14-16"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text (as defined in https://www.w3.org/wiki/W ebSchemas/Accessibility)

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_UMIScenarioFile_

</td>  
<td>

</td>  
<td>

For the UMI Scenario File.

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_EducationalActivity_

</td>  
<td>

</td>  
<td>

For the UMI Activities, there can be more than one Activities.

</td> </tr>  
<tr>  
<td>

**UMI Scenario File**

</td> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

The name of the file

</td> </tr>  
<tr>  
<td>

**Metadata property**

</td>  
<td>

**Metadata typeof**

</td>  
<td>

**Value space**

</td>  
<td>

**Platform field**

</td>  
<td>

**Comments**

</td> </tr>  
<tr>  
<td>

**fileformat**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Text (MIME format - see IANA site)

</td>  
<td>

</td>  
<td>

The type of the file

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

Inherited from UMIScenario

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

Inherited from UMIScenario

</td> </tr>  
<tr>  
<td>

**datePublished**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**isPartOf**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

UMIScenario

</td>  
<td>

</td>  
<td>

</td> </tr> </table>

#  Table 4 Metadata defined for the _UMI Scenario_ content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Description and Steps

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**interactivityType**

</td>  
<td>

CreativeWork

</td>  
<td>

"active", "expositive" or

"mixed"

</td>  
<td>

Interactivity Type

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "activityType"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

"Introductory", "Core"

"Concluding" or "Auxiliary"

</td>  
<td>

Type of Activity

</td>  
<td>

alignmentFramework = "Horizon2020 UMI-Sci-Ed"

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "learningObjectives"**

</td>  
<td>

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Learning Objectives

</td>  
<td>

alignmentFramework = "Revised Bloom Taxonomy"

</td> </tr>  
<tr>  
<td>

**timeRequired**

</td>  
<td>

CreativeWork

</td>  
<td>

ISO 8601

</td>  
<td>

Expected duration

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**educationalRole**

</td>  
<td>

Ιntangible > Audience > EducationalAudience

</td>  
<td>

"teacher", "learner",

"author", "manager"

</td>  
<td>

Audience

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**version**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**inLanguage**

</td>  
<td>

CreativeWork

</td>  
<td>

Text, as defined in IETF BCP47

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text (as defined in https://www.w3.org/wiki/W ebSchemas/Accessibility)

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"Educational Activity"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Educational

Activity"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**educationalUse**

</td>  
<td>

CreativeWork

</td>  
<td>

"Educational Scenario implementation"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**typicalAgeRange**

</td>  
<td>

CreativeWork

</td>  
<td>

"14-16"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**isPartOf**

</td>  
<td>

CreativeWork

</td>  
<td>

UMIScenario

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**learningResourceType**

</td>  
<td>

CreativeWork

</td>  
<td>

"learning activity"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_UMIActivityFile_

</td>  
<td>

</td>  
<td>

For the UMI Activity File

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_UMIEducationalMaterial_

</td>  
<td>

</td>  
<td>

For the Educational Material

</td> </tr>  
<tr>  
<td>

**UMI Activity File**

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

Filename

</td> </tr>  
<tr>  
<td>

**fileformat**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Text (MIME format - see IANA site)

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

Inherited from _UMIScenario_

</td> </tr>  
<tr>  
<td>

**isPartOf**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

UMIScenario

</td>  
<td>

</td>  
<td>

</td> </tr> </table>

#  Table 5 Metadata defined for an activity that is part of a _UMI Scenario_
content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**version**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Version

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**isBasedOn**

</td>  
<td>

CreativeWork

</td>  
<td>

_UMIScenario_

</td>  
<td>

UMI Scenario

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**inLanguage**

</td>  
<td>

CreativeWork

</td>  
<td>

Text, as defined in IETF BCP47

</td>  
<td>

Language

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Description

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**keywords**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Key Terms

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**timeRequired**

</td>  
<td>

CreativeWork

</td>  
<td>

ISO 8601

</td>  
<td>

Duration

</td>  
<td>

Months, days, hours, minutes

</td> </tr>  
<tr>  
<td>

**interactivityType = "mixed"**

</td>  
<td>

CreativeWork

</td>  
<td>

"active", "expositive" or

"mixed"

</td>  
<td>

Interactivity Type

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**targetName,**

**alignmentType =**

**"difficulty"**

</td>  
<td>

AlignmentObject

</td>  
<td>

"Easy", "Intermediate" or

"Advanced"

</td>  
<td>

Difficulty

</td>  
<td>

alignmentFramework = "IEEE LOM

5.8"

</td> </tr>  
<tr>  
<td>

**targetName,**

**alignmentType = "requires"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Resources - Hardware

</td>  
<td>

alignmentFramework = "UMI-Sci-Ed hardware resources"

</td> </tr>  
<tr>  
<td>

**targetName,**

**alignmentType = "requires"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Resources - Software

</td>  
<td>

alignmentFramework = "UMI-Sci-Ed software resources"

</td> </tr>  
<tr>  
<td>

**targetName,**

**alignmentType = "requires"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Resources - Software

</td>  
<td>

alignmentFramework = "UMI-Sci-Ed other resources"

</td> </tr>  
<tr>  
<td>

**targetName, alignmentType = "learningOutcomes"**

</td>  
<td>

Ιntangible >

AlignmentObject

</td>  
<td>

Text

</td>  
<td>

Expected Learning Outcomes

</td>  
<td>

alignmentFramework = "Revised Bloom Taxonomy"

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

License

</td>  
<td>

Creative Commons URL

</td> </tr>  
<tr>  
<td>

**educationalRole**

</td>  
<td>

Ιntangible > Audience > EducationalAudience

</td>  
<td>

"learner"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI Project"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Project"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**educationalUse**

</td>  
<td>

CreativeWork

</td>  
<td>

"Educational Scenario implementation"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**typicalAgeRange**

</td>  
<td>

CreativeWork

</td>  
<td>

"14-16"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text (as defined in https://www.w3.org/wiki/W ebSchemas/Accessibility)

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_UMIProjectFile_

</td>  
<td>

</td>  
<td>

For the UMI Project File.

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_FileAttachment_ ,

_YouTubeVideo_ , or

_Image/Photo_

</td>  
<td>

</td>  
<td>

Files and Media

</td> </tr>  
<tr>  
<td>

**UMI Project file**

</td> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

The name of the file

</td> </tr>  
<tr>  
<td>

**fileformat**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Text (MIME format - see IANA site)

</td>  
<td>

</td>  
<td>

The type of the file

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

Inherited from _UMIProject_

</td> </tr>  
<tr>  
<td>

**datePublished**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**isPartOf**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

_UMIProject_

</td>  
<td>

</td>  
<td>

</td> </tr> </table>

#  Table 6 Metadata defined for the _UMI Project_ content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**keywords**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Tags

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Summary

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**articleBody**

</td>  
<td>

CreativeWork > Article

>

</td>  
<td>

Text

</td>  
<td>

Body

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**audienceType**

</td>  
<td>

Intangible > Audience

</td>  
<td>

"public" or _UMIGroup_

</td>  
<td>

Group content visibility, Groups audience

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI Group Article"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Group Article"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**interactivityType**

</td>  
<td>

CreativeWork

</td>  
<td>

"expositive"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**ResourceType**

</td>  
<td>

</td>  
<td>

"Article"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_FileAttachment_ ,

_YouTubeVideo_ , or

_Image/Photo_

</td>  
<td>

</td>  
<td>

Files and Media

</td> </tr> </table>

#  Table 7 Metadata defined for the _Group Article_ content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Subject

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**articleBody**

</td>  
<td>

CreativeWork > Article

</td>  
<td>

Text

</td>  
<td>

Body

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**keywords**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Tags of Wiki

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**version**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Version

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**text**

</td>  
<td>

CreativeWork > Comment

</td>  
<td>

</td>  
<td>

Revision log message

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**audienceType**

</td>  
<td>

Intangible > Audience

</td>  
<td>

"public" or _UMIGroup_

</td>  
<td>

Group content

visibility, Groups audience

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

https://creativecommons.or g/licenses/by/4.0/

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**contributor**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI Wiki"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Wiki"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**interactivityType**

</td>  
<td>

CreativeWork

</td>  
<td>

"expositive"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**learningResourceType**

</td>  
<td>

CreativeWork

</td>  
<td>

"wiki page"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**typicalAgeRange**

</td>  
<td>

CreativeWork

</td>  
<td>

"14-"

</td>  
<td>

</td>  
<td>

Fixed value.

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr> </table>

#  Table 8 Metadata defined for the _Wiki_ content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**keywords**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Tags

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Summary

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**sharedContent**

</td>  
<td>

CreativeWork > Article

> SocialMediaPosting >

BlogPosting - typeOf

CreativeWork >

Article: articleBody

</td>  
<td>

Text

</td>  
<td>

Body

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**audienceType**

</td>  
<td>

Intangible > Audience

</td>  
<td>

"public" or _UMIGroup_

</td>  
<td>

Group content visibility, Groups audience

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**sharedContent**

</td>  
<td>

CreativeWork

</td>  
<td>

_FileAttachment_ ,

_YouTubeVideo_ , or

_Image/Photo_

</td>  
<td>

</td>  
<td>

Files and Media

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI Blog"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Blog"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**Blog post (Comment)**

</td> </tr>  
<tr>  
<td>

**about**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Subject

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**text**

</td>  
<td>

CreativeWork > Comment

</td>  
<td>

Text

</td>  
<td>

Comment

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

any date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**parentItem**

</td>  
<td>

CreativeWork > Comment

</td>  
<td>

_UMIBlog_

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**sharedContent**

</td>  
<td>

CreativeWork

</td>  
<td>

_FileAttachment_ ,

_YouTubeVideo_ , or

_Image/Photo_

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

(RegisteredUser)

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI Blog Comment"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Blog Comment"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr> </table>

#  Table 9 Metadata defined for the _Blog_ content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Subject

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI General Discussion

Forum" or "UMI Platform

Support Forum"

</td>  
<td>

Forums

</td>  
<td>

Depending on user selection

</td> </tr>  
<tr>  
<td>

**sharedContent**

</td>  
<td>

CreativeWork > Article

> SocialMediaPosting > DiscussionForumPosti ng - typeof

CreativeWork >

Article: articleBody

</td>  
<td>

Text

</td>  
<td>

Body

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**sharedContent**

</td>  
<td>

CreativeWork

</td>  
<td>

_FileAttachment_ ,

_YouTubeVideo_ , or

_Image/Photo_

</td>  
<td>

</td>  
<td>

Files and Media

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Forum"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**Forum Post (Comment)**

</td> </tr>  
<tr>  
<td>

**about**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Subject

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**text**

</td>  
<td>

CreativeWork > Comment

</td>  
<td>

Text

</td>  
<td>

Comment

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

any date

</td>  
<td>

</td>  
<td>

To be shown in view mode

</td> </tr>  
<tr>  
<td>

**parentItem**

</td>  
<td>

CreativeWork > Comment

</td>  
<td>

_UMIForumTopic_

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**sharedContent**

</td>  
<td>

CreativeWork

</td>  
<td>

_FileAttachment_ ,

_YouTubeVideo_ , or

_Image/Photo_

</td>  
<td>

</td>  
<td>

Files and Media

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

To be shown in view mode

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI Forum Comment"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Forum

Comment"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr> </table>

#  Table 10 Metadata defined for the _Forum Topic_ content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Title

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**keywords**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Key terms

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**author**

</td>  
<td>

Person

</td>  
<td>

Registered User

</td>  
<td>

Authors

</td>  
<td>

Multiple inputs are allowed

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"Educational Material",

“Learning Artefact”,

"Research Material",

"Other"

</td>  
<td>

Type

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Subject

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

License

</td>  
<td>

Creative Commons URL

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**disambiguatingDescription**

</td>  
<td>

CreativeWork

</td>  
<td>

"UMI-Sci-Ed Repository

Entry"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**interactivityType**

</td>  
<td>

CreativeWork

</td>  
<td>

"expositive"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**learningResourceType**

</td>  
<td>

CreativeWork

</td>  
<td>

"wiki page"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**typicalAgeRange**

</td>  
<td>

CreativeWork

</td>  
<td>

"14-"

</td>  
<td>

</td>  
<td>

Fixed value.

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

TBD

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

TBD

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

TBD

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

TBD

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_FileAttachment_ ,

_YouTubeVideo_ , or

_Image/Photo_

</td>  
<td>

</td>  
<td>

Files and Media

</td> </tr>  
<tr>  
<td>

**learningResourceType**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

Inherited from Files and Media

</td> </tr>  
<tr>  
<td>

**artefactType**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

Inherited from Files and Media

</td> </tr>  
<tr>  
<td>

**resourceType**

</td>  
<td>

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

Inherited from Files and Media

</td> </tr> </table>

#  Table 11 Metadata defined for the _Repository Entry_ content type.  
  
<table>  
<tr>  
<th>

**Metadata property**

</th>  
<th>

**Metadata typeof**

</th>  
<th>

**Value space**

</th>  
<th>

**Platform field**

</th>  
<th>

**Comments**

</th> </tr>  
<tr>  
<td>

**description**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Description

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**genre**

</td>  
<td>

CreativeWork

</td>  
<td>

"Educational Material",

"Artefact", "Research

Material", "Other"

</td>  
<td>

Type of Attachment

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**learningResourceType**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

File content characterization

</td>  
<td>

Takes value if genre = "Educational Material"

</td> </tr>  
<tr>  
<td>

**artefactType**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

Takes value if genre = "Artefact"

</td> </tr>  
<tr>  
<td>

**resourceType**

</td>  
<td>

</td>  
<td>

Text

</td>  
<td>

Takes value if genre = "Research Material" or "Other"

</td> </tr>  
<tr>  
<td>

**dateCreated**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**dateModified**

</td>  
<td>

CreativeWork

</td>  
<td>

Date

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**provider:name**

</td>  
<td>

Organization:Text

</td>  
<td>

"Horizon2020 UMI-Sci-Ed"

</td>  
<td>

</td>  
<td>

Fixed Value

</td> </tr>  
<tr>  
<td>

**license**

</td>  
<td>

CreativeWork

</td>  
<td>

URL

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityAPI**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityControl**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityFeature**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**accessibilityHazard**

</td>  
<td>

CreativeWork

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

TBD

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**typicalAgeRange**

</td>  
<td>

CreativeWork

</td>  
<td>

"14-"

</td>  
<td>

</td>  
<td>

Fixed value

</td> </tr>  
<tr>  
<td>

**isPartOf**

</td>  
<td>

CreativeWork

</td>  
<td>

_UMIProject_ , _UMIBlog_ ,

_UMIBlogPost_ ,

_UMIForumTopic_ ,

_UMIGroupArticle_ ,

_UMIForumPost_ , _UMIWiki_ ,

_UMIRepositoryEntry_

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**hasPart**

</td>  
<td>

CreativeWork

</td>  
<td>

_AttachmentFile_

</td>  
<td>

</td>  
<td>

For the Attached File

</td> </tr>  
<tr>  
<td>

**Attachment File**

</td> </tr>  
<tr>  
<td>

**name**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

Text

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**fileformat**

</td>  
<td>

CreativeWork

</td>  
<td>

Text (MIME format - see IANA site)

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**identifier**

</td>  
<td>

CreativeWork

</td>  
<td>

URI

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**isPartOf**

</td>  
<td>

CreativeWork > DigitalDocument

</td>  
<td>

_UMIProject_ , _UMIBlog_ ,

_UMIBlogPost_ ,

_UMIForumTopic_ ,

_UMIGroupArticle_ ,

_UMIForumPost_ , _UMIWiki_ ,

_UMIRepositoryEntry_

</td>  
<td>

</td>  
<td>

</td> </tr> </table>

**Table 12 Metadata defined for _Files and Media_ supporting several content
types. NOTE: These metadata are for a file attachment. YouTube videos do not
have an Attachment file and include a “contentUrl” property instead. Image or
photo attachments on the other hand include a “caption” property in place of
the “description” property. **