|
Ontology Class
|
Badge
|
Card.
|
+|--------------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------|------------------------------------|
+| 1 | @context | Explanation of metadata keys in ontology terms. | [context.json](https://raw.githubusercontent.com/OpenEnergyPlatform/oemetadata/production/oemetadata/latest/context.json) | | Platinum | [0..1] |
+| 2 | @id | A unique identifier (UUID/DOI) for the dataset. This is the Databus Artifact. | [databus.openenergyplatform.org/oeplatform/supply/wri_global_power_plant_database/](https://databus.openenergyplatform.org/oeplatform/supply/wri_global_power_plant_database/) | [dct:identifier](http://purl.org/dc/terms/identifier) | Platinum | [0..1] |
+| 3 | path | A unique identifier (URI/UUID/DOI) for the dataset. | [oemetadata_table_template](https://openenergyplatform.org/database/tables/oemetadata_table_template) | [dcat:accessURL](https://www.w3.org/ns/dcat#accessURL) | Bronze | [0..1] |
+| 4 | name | A filename or database conform dataset name. | oep_oemetadata | [rdfs:label](https://www.w3.org/2000/01/rdf-schema#/label) | Iron | [1] |
+| 5 | title | A human readable dataset name. | OEP OEMetadata | [dct:title](http://purl.org/dc/terms/title) | Bronze | [0..1] |
+| 6 | description | A free text description of the dataset. | A collection of tables for the OEMetadata examples. | [dct:description](http://purl.org/dc/terms/description) | Bronze | [0..1] |
+| 7 | **spatial** | An object that describes a covered area or region of the dataset. | | [oeo:spatial region](http://purl.obolibrary.org/obo/BFO_0000006) | | [0..1] |
+| 7.1 | region | The name of the spatial region of the dataset. | Berlin | [rdfs:label](https://www.w3.org/2000/01/rdf-schema#/label) | Silver | [0..1] |
+| 7.2 | @id | A URI reference for the region of the dataset. | [www.wikidata.org/wiki/Q64](https://www.wikidata.org/wiki/Q64) | [dct:identifier](http://purl.org/dc/terms/identifier) | Platinum | [0..1] |
+| 8 | referenceDate | A base year, month or day. The time for which the dataset should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 9 | languages | An array of languages used within the described data structures (e.g. titles, descriptions). The language key can be repeated if more languages are used. Standard: IETF (BCP47) | en-GB, de-DE | [dct:language](http://purl.org/dc/terms/language) | Gold | [*] |
+| 10 | version | A version string identifying the version of the package. | 0.1.0 | [dcat:version](https://www.w3.org/ns/dcat#version) | Silver | [0..1] |
+| 11 | image | An image to use for this data package. | https://openenergyplatform.org/static/img/about/OpenEnergyFamily_GroupPhoto2.png | [schema.org:image](https://schema.org/image) | Gold | [0..1] |
+| 12 | **subject** | An array of objects that references to the subjects of the resource in ontology terms. | | | - | [*] |
+| 12.1 | name | A class label of the ontology term. | energy | [rdfs:label](https://www.w3.org/2000/01/rdf-schema#/label) | Platinum | [0..1] |
+| 12.2 | @id | A unique identifier (URI/IRI) of the ontology class. | [openenergyplatform.org/ontology/oeo/OEO_00000150](https://openenergyplatform.org/ontology/oeo/OEO_00000150) | [dct:subject](http://purl.org/dc/terms/subject) | Platinum | [0..1] |
+| 13 | keywords | An array of freely selectable keywords that help with searching and structuring. | example, ODbL-1.0, NFDI4Energy | [dcat:keyword](http://www.w3.org/ns/dcat#keyword) | Silver | [*] |
### Dataset - Project Context Keys
|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
@@ -108,9 +109,9 @@ If a value is not yet available, use: `ToDo`.
| 2 | path | A unique identifier (URI/UUID/DOI) for the table or file. | [oemetadata_table_template](https://openenergyplatform.org/database/tables/oemetadata_table_template) | [dcat:accessURL](https://www.w3.org/ns/dcat#accessURL) | Bronze | [0..1] |
| 3 | name | A filename or database conform table name. | oemetadata_table_template | [rdfs:label](https://www.w3.org/2000/01/rdf-schema#/label) | Iron | [1] |
| 4 | title | A human readable resource or table name. | OEMetadata Table | [dct:title](http://purl.org/dc/terms/title) | Silver | [0..1] |
-| 5 | topics | An array of predefined topics that correspond to the database schemas of the OEP. | model_draft | [foaf:topic](http://xmlns.com/foaf/spec/#term_topic) | Bronze | [*] |
-| 6 | description | A description of the table. It should be usable as summary information for the table that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
-| 7 | publicationDate | A date of publication of the data or metadata. The date format is ISO 8601 (YYYY-MM-DD). | 2024-10-15 | [dct:issued](http://purl.org/dc/terms/issued) | Bronze | [0..1] |
+| 5 | description | A description of the table. It should be usable as summary information for the table that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
+| 6 | publicationDate | A date of publication of the data. The date format is ISO 8601 (YYYY-MM-DD). | 2024-10-15 | [dct:issued](http://purl.org/dc/terms/issued) | Bronze | [0..1] |
+| 7 | topics | An array of predefined topics that correspond to the database schemas of the OEP. | model_draft | [foaf:topic](http://xmlns.com/foaf/spec/#term_topic) | Bronze | [*] |
| 8 | **subject** | An array of objects that references to the subjects of the resource in ontology terms. | | | | [*] |
| 8.1 | name | A class label of the ontology term. | energy | [rdfs:label](https://www.w3.org/2000/01/rdf-schema#/label) | Platinum | [0..1] |
| 8.2 | @id | A unique identifier (URI/IRI) of the ontology class. | [openenergyplatform.org/ontology/oeo/OEO_00000150](https://openenergyplatform.org/ontology/oeo/OEO_00000150) | [dct:subject](http://purl.org/dc/terms/subject) | Platinum | [0..1] |
@@ -150,68 +151,6 @@ If a value is not yet available, use: `ToDo`.
| 1.2.5 | alignment | An indicator of whether timestamps in a time series are to the left, right or in the centre. | left | [oeo:time stamp alignment](http://openenergyplatform.org/ontology/oeo/OEO_00140044) | Silver | [0..1] |
| 1.2.6 | aggregationType | An indicator of whether the values are a sum, an average or a current value. | current | [oeo:aggregation type](https://openenergyplatform.org/ontology/oeo/OEO_00140068/) | Silver | [0..1] |
-### Resources - Module Keys
-|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
-|--------------------------------|----------------------------------|-------------------------------------------|---------------------------------------|----------------------------------------------|------------------------------------|------------------------------------|
-| 1 | **modules** | An objects with domain specific metadata | | | | [0..1] |
-
-### Module - Energy Systems (LH)
-|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
-|--------------------------------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------|
-| 1 | moduleName | The name of the module | Energy Systems | | Platinum | [0..1] |
-| 3 | supplyTechnologies | A supply technology describes how specific technical components and processes are combined to generate or provide energy | (Solar, Wind, Biomass, Biogas, Geo, ST, other) | [oeo:OEO_00020003 energy transformation](https://openenergyplatform.org/ontology/oeo/OEO_00020003) | Platinum | [0..1] |
-| 4 | storageTechnologies | An energy storage technology describes how energy storage components and energy carriers are combined to charge, store, and discharge energy for temporary use. | (Battery, Kinetic, CA, Pump, Chemical) | [oeo:00020366 energy storage technology](https://openenergyplatform.org/ontology/oeo/OEO_00020366) | Platinum | [0..1] |
-| 6 | supplyGrid | A supply grid is a system of interconnected technical components that together enable the distribution and delivery of energy. | (electricity, gas, heating) | [oeo:OEO_00000200 supply grid](https://openenergyplatform.org/ontology/oeo/OEO_00000200) | Platinum | [0..1] |
-| 2 | finalEnergyCarrier | A final energy carrier is an energy carrier that is delivered to and directly used by end users without further transformation. | (electricity, heating, gas, fuel, ...) | [oeo:OEO_00140080 final energy carrier](https://openenergyplatform.org/ontology/oeo/OEO_00140080/) | Platinum | [0..1] |
-| 5 | demandSectors | An energy demand sector is a sector of the energy system that groups together energy consumers with similar usage characteristics. | (building, commercial, households, transport) | [oeo:OEO_00000128 energy demand sector](https://openenergyplatform.org/ontology/oeo/OEO_00000128) | Platinum | [0..1] |
-| 7 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Platinum | [0..1] |
-
-### Module - Measurement Data (LH)
-|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
-|--------------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------|------------------------------------|------------------------------------|
-| 1 | moduleName | The name of the module WIP | Measurement Data | ? | Platinum | [0..1] |
-| 2 | instrumentIdentifier | Unique string that identifies the instrument instance | http://hdl.handle.net/21.11157/a9250866-bbec-4542-86b3-a5f78c0c6922 | ? | Platinum | [0..1] |
-| 3 | instrumentPath | A landing page that the identifier resolves to | https://sms.atmohub.kit.edu/devices/961 | ? | Platinum | [0..1] |
-| 5 | instrumentName | Name by which the instrument instance is known | MFC_001000_02 - Merck KGaA - FC-2926V - DH9806004 | ? | Platinum | [0..1] |
-| 4 | instrumentOwner | Institution(s) responsible for the management of the instrument. This may include the legal owner, the operator, or an institute providing access to the instrument. | Karlsruhe Institute of Technology (KIT) | ? | Platinum | [0..1] |
-| 5 | manufacturerName | Full name of the manufacturer | Merck KGaA | ? | Platinum | [0..1] |
-| 6 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example instrument of PIDInst. | [dct:description](http://purl.org/dc/terms/description) | Platinum | [0..1] |
-
-### Module - Data Transformations & ERSMeta (AK)
-|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
-|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------|------------------------------------|
-| 1 | moduleName | The name of the module WIP | Data Transformations | | | [0..1] |
-| 2 | softwareName | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 3 | softwarePath | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 4 | softwareVersion | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 5 | softwareType | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 6 | programmingLanguage | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 7 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
-
-### Module - Transportation Systems (CHK)
-|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
-|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------|------------------------------------|
-| 1 | moduleName | The name of the module WIP | Transportation Systems | | | [0..1] |
-| 2 | transportMode | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 3 | meansOfTransport | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 4 | transportInfrastructure | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 5 | dataGenerationMethod | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 6 | surveyPopulation | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 7 | elementaryUnit | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 8 | spatialUnit | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 9 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
-
-### Module - Advanced Provenience (AK, JF)
-|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
-|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------|------------------------------------|
-| 1 | moduleName | The name of the module WIP | Advanced Provenience | | | [0..1] |
-| 2 | policy | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 3 | objectLifeCycleType | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 4 | objectTombstoneInformation | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 5 | provenanceGraph | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 6 | wasGeneratedBy | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
-| 7 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
-
### Resources - Sources Keys
|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------|------------------------------------|
@@ -287,6 +226,70 @@ If a value is not yet available, use: `ToDo`.
| 1.1 | path | A link or path to the documented open peer review. | [open_peer_review/9](https://openenergyplatform.org/dataedit/view/model_draft/oep_table_example/open_peer_review/9/) | [sc:url](https://schema.org/url) | [0..1] |
| 1.2 | badge | A badge of either Iron, Bronze, Silver, Gold or Platinum is used to label the quality of the metadata. | Platinum | [oeo:quality control flag](https://openenergyplatform.org/ontology/oeo/OEO_00140098/) | [0..1] |
+
+### Dataset - Module Keys
+|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
+|--------------------------------|----------------------------------|-------------------------------------------|---------------------------------------|----------------------------------------------|------------------------------------|------------------------------------|
+| 1 | **modules** | An objects with domain specific metadata | | | | [0..1] |
+
+
+### Dataset - Module - Energy Systems
+|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
+|--------------------------------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------|
+| 1 | supplyTechnologies | A supply technology describes how specific technical components and processes are combined to generate or provide energy. | (Solar, Wind, Biomass, Biogas, Geo, ST, other) | [oeo:OEO_00020003 energy transformation](https://openenergyplatform.org/ontology/oeo/OEO_00020003) | Module | [0..1] |
+| 2 | storageTechnologies | An energy storage technology describes how energy storage components and energy carriers are combined to charge, store, and discharge energy for temporary use. | (Battery, Kinetic, CA, Pump, Chemical) | [oeo:00020366 energy storage technology](https://openenergyplatform.org/ontology/oeo/OEO_00020366) | Module | [0..1] |
+| 3 | supplyGrid | A supply grid is a system of interconnected technical components that together enable the distribution and delivery of energy. | (electricity, gas, heating) | [oeo:OEO_00000200 supply grid](https://openenergyplatform.org/ontology/oeo/OEO_00000200) | Module | [0..1] |
+| 4 | finalEnergyCarrier | A final energy carrier is an energy carrier that is delivered to and directly used by end users without further transformation. | (electricity, heating, gas, fuel, ...) | [oeo:OEO_00140080 final energy carrier](https://openenergyplatform.org/ontology/oeo/OEO_00140080/) | Module | [0..1] |
+| 5 | demandSectors | An energy demand sector is a sector of the energy system that groups together energy consumers with similar usage characteristics. | (building, commercial, households, transport) | [oeo:OEO_00000128 energy demand sector](https://openenergyplatform.org/ontology/oeo/OEO_00000128) | Module | [0..1] |
+| 6 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Module | [0..1] |
+
+### Dataset - Module - Measurement Data
+|
#
|
Key
|
Description
|
Example
|
Semantic Property
|
Badge
|
Card.
|
+|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|------------------------------------|
+| 1 | instrumentIdentifier | Unique string that identifies the instrument instance. | http://hdl.handle.net/21.11157/a9250866-bbec-4542-86b3-a5f78c0c6922 | [dct:identifier](http://purl.org/dc/terms/identifier) | Module | 1 |
+| 2 | instrumentPath | A landing page that the identifier resolves to. | https://sms.atmohub.kit.edu/devices/961 | [dct:url](http://purl.org/dc/terms/url) | Module | [0..1] |
+| 3 | instrumentName | Name by which the instrument instance is known. | MFC_001000_02 - Merck KGaA - FC-2926V - DH9806004 | [dct:name](http://purl.org/dc/terms/name) | Module | [0..1] |
+| 4 | instrumentOwner | Institution(s) responsible for the management of the instrument. This may include the legal owner, the operator, or an institute providing access to the instrument. | Karlsruhe Institute of Technology (KIT) | [sc:owner](https://schema.org/owner) | Module | [0..1] |
+| 5 | manufacturerName | Full name of the manufacturer. | Merck KGaA | [sc:manufacturer](https://schema.org/manufacturer) | Module | [0..1] |
+| 6 | instrumentConfiguration | The configuration of the instrument that was used during measurement | https://example.com/a-file-that-describes-the-instrument-configuration | [m4i:hasParameterSet](https://w3id.org/nfdi4ing/metadata4ing#hasParameterSet) | Module | [0..1] |
+| 7 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example instrument of PIDINST schema. | [dct:description](http://purl.org/dc/terms/description) | Module | 1 |
+
+### Dataset - Module - Data Transformations & ERSMeta
+|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
+|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------|------------------------------------|
+| 1 | moduleName | The name of the module WIP | Data Transformations | | | [0..1] |
+| 2 | softwareName | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 3 | softwarePath | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 4 | softwareVersion | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 5 | softwareType | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 6 | programmingLanguage | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 7 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
+
+### Dataset - Module - Transportation Systems
+|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
+|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------|------------------------------------|
+| 1 | moduleName | The name of the module WIP | Transportation Systems | | | [0..1] |
+| 2 | transportMode | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 3 | meansOfTransport | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 4 | transportInfrastructure | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 5 | dataGenerationMethod | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 6 | surveyPopulation | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 7 | elementaryUnit | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 8 | spatialUnit | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 9 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
+
+### Dataset - Module - Advanced Provenience
+|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Badge
|
Card.
|
+|--------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------|------------------------------------|
+| 1 | moduleName | The name of the module WIP | Advanced Provenience | | | [0..1] |
+| 2 | policy | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 3 | objectLifeCycleType | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 4 | objectTombstoneInformation | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 5 | provenanceGraph | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 6 | wasGeneratedBy | XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. | 2020-01-01 | [dct:date](http://purl.org/dc/terms/date) | Silver | [0..1] |
+| 7 | moduleDescription | A description of the module. It should be usable as summary information for the module that is described by the metadata. | Example table used to illustrate the OEMetadata structure and features. | [dct:description](http://purl.org/dc/terms/description) | Silver | [0..1] |
+
+
### MetaMetadata Keys
|
#
|
Key
|
Description
|
Example
|
Ontology Class
|
Card.
|
|--------------------------------|----------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------|------------------------------------|
diff --git a/oemetadata/v2/v21/metadata_key_details.md b/oemetadata/v2/v21/metadata_key_details.md
index bb2ef8a9..c05f28dd 100644
--- a/oemetadata/v2/v21/metadata_key_details.md
+++ b/oemetadata/v2/v21/metadata_key_details.md
@@ -1322,7 +1322,7 @@ If a value is not yet available, use: `ToDo`.
| Description | The metadata on the OEP can go through an open peer review process. See the Academy course [Open Peer Review](https://openenergyplatform.github.io/academy/courses/09_peer_review/) for further information. |
| Example | |
| Ontology Class | |
-| Badge | [0..1] |
+| Card. | [0..1] |
### Resources - Review Keys - path
| | |
@@ -1331,7 +1331,7 @@ If a value is not yet available, use: `ToDo`.
| Description | A link or path to the documented open peer review. |
| Example | [open_peer_review/9](https://openenergyplatform.org/dataedit/view/model_draft/oep_table_example/open_peer_review/9/) |
| Ontology Class | [sc:url](https://schema.org/url) |
-| Badge | [0..1] |
+| Card. | [0..1] |
### Resources - Review Keys - badge
| | |
@@ -1340,7 +1340,138 @@ If a value is not yet available, use: `ToDo`.
| Description | A badge of either Iron, Bronze, Silver, Gold or Platinum is used to label the quality of the metadata. |
| Example | Platinum |
| Ontology Class | [oeo:quality control flag](https://openenergyplatform.org/ontology/oeo/OEO_00140098/) |
-| Badge | [0..1] |
+| Card. | [0..1] |
+
+
+## Dataset - Modules
+
+### Dataset - Module - Energy Systems
+| | |
+|----------------|------------------------------------------------------------------|
+| Key | **moduleEnergySystems** |
+| Description | An Object that describes the main concepts of an energy system. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Energy Systems - supplyTechnologies
+| | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------|
+| Key | **supplyTechnologies** |
+| Description | A supply technology describes how specific technical components and processes are combined to generate or provide energy. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Energy Systems - storageTechnologies
+| | |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Key | **storageTechnologies** |
+| Description | An energy storage technology describes how energy storage components and energy carriers are combined to charge, store, and discharge energy for temporary use. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Energy Systems - supplyGrid
+| | |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------|
+| Key | **supplyGrid** |
+| Description | A supply grid is a system of interconnected technical components that together enable the distribution and delivery of energy. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Energy Systems - finalEnergyCarrier
+| | |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Key | **finalEnergyCarrier** |
+| Description | An energy storage technology describes how energy storage components and energy carriers are combined to charge, store, and discharge energy for temporary use. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Energy Systems - demandSectors
+| | |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| Key | **demandSectors** |
+| Description | An energy demand sector is a sector of the energy system that groups together energy consumers with similar usage characteristics. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Energy Systems - moduleDescription
+| | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------|
+| Key | **moduleDescription** |
+| Description | A description of the module. It should be usable as summary information for the module that is described by the metadata. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+
+### Dataset - Module - Measurement Data
+| | |
+|----------------|-------------------------------------------------------------------|
+| Key | **moduleMeasurementData** |
+| Description | An Object that describes the instruments used in the measurement. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Measurement Data - instrumentIdentifier
+| | |
+|----------------|---------------------------------------------------------------------|
+| Key | **instrumentIdentifier** |
+| Description | Unique string that identifies the instrument instance. |
+| Example | http://hdl.handle.net/21.11157/a9250866-bbec-4542-86b3-a5f78c0c6922 |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Measurement Data - instrumentPath
+| | |
+|----------------|-------------------------------------------------|
+| Key | **instrumentPath** |
+| Description | A landing page that the identifier resolves to. |
+| Example | https://sms.atmohub.kit.edu/devices/961 |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Measurement Data - instrumentName
+| | |
+|----------------|----------------------------------------------------|
+| Key | **instrumentName** |
+| Description | Name by which the instrument instance is known. |
+| Example | MFC_001000_02 - Merck KGaA - FC-2926V - DH9806004 |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Measurement Data - instrumentOwner
+| | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Key | **instrumentOwner** |
+| Description | Institution(s) responsible for the management of the instrument. This may include the legal owner, the operator, or an institute providing access to the instrument. |
+| Example | Karlsruhe Institute of Technology (KIT) |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Measurement Data - manufacturerName
+| | |
+|----------------|--------------------------------|
+| Key | **manufacturerName** |
+| Description | Full name of the manufacturer. |
+| Example | Merck KGaA |
+| Ontology Class | |
+| Card. | [0..1] |
+
+### Dataset - Module - Measurement Data - moduleDescription
+| | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------|
+| Key | **moduleDescription** |
+| Description | A description of the module. It should be usable as summary information for the module that is described by the metadata. |
+| Example | |
+| Ontology Class | |
+| Card. | [0..1] |
+
### MetaMetadata Keys
| | |
diff --git a/oemetadata/v2/v21/schema.json b/oemetadata/v2/v21/schema.json
index 41f45a2f..7ca4bdfd 100644
--- a/oemetadata/v2/v21/schema.json
+++ b/oemetadata/v2/v21/schema.json
@@ -453,6 +453,312 @@
"title": "Contributor"
}
},
+ "moduleEnergySystems": {
+ "description": "An Object that describes the main concepts of an energy system.",
+ "type": "object",
+ "properties": {
+ "supplyTechnologies": {
+ "description": "A supply technology describes how specific technical components and processes are combined to generate or provide energy.",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "name": {
+ "description": "A class label of the ontology term.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "energy transformation"
+ ],
+ "badge": "Module",
+ "title": "Supply Technologies Subject Name"
+ },
+ "@id": {
+ "description": "A unique identifier (URI/IRI) of the ontology class.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "https://openenergyplatform.org/ontology/oeo/OEO_00020003"
+ ],
+ "badge": "Module",
+ "title": "Supply Technologies Subject Identifier",
+ "format": "uri"
+ }
+ },
+ "badge": "Module",
+ "title": "Supply Technologies Subject"
+ },
+ "badge": "Module",
+ "title": "Supply Technologies"
+ },
+ "storageTechnologies": {
+ "description": "An energy storage technology describes how energy storage components and energy carriers are combined to charge, store, and discharge energy for temporary use.",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "name": {
+ "description": "A class label of the ontology term.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "energy storage technology"
+ ],
+ "badge": "Module",
+ "title": "Storage Technologies Subject Name"
+ },
+ "@id": {
+ "description": "A unique identifier (URI/IRI) of the ontology class.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "https://openenergyplatform.org/ontology/oeo/OEO_00020366"
+ ],
+ "badge": "Module",
+ "title": "Storage Technologies Subject Identifier",
+ "format": "uri"
+ }
+ },
+ "badge": "Module",
+ "title": "Storage Technologies Subject"
+ },
+ "badge": "Module",
+ "title": "Storage Technologies"
+ },
+ "supplyGrid": {
+ "description": "A supply grid is a system of interconnected technical components that together enable the distribution and delivery of energy.",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "name": {
+ "description": "A class label of the ontology term.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "supply grid"
+ ],
+ "badge": "Module",
+ "title": "Supply Grid Subject Name"
+ },
+ "@id": {
+ "description": "A unique identifier (URI/IRI) of the ontology class.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "https://openenergyplatform.org/ontology/oeo/OEO_00000200"
+ ],
+ "badge": "Module",
+ "title": "Supply Grid Subject Identifier",
+ "format": "uri"
+ }
+ },
+ "badge": "Module",
+ "title": "Supply Grid Subject"
+ },
+ "badge": "Module",
+ "title": "Supply Grid"
+ },
+ "finalEnergyCarrier": {
+ "description": "A final energy carrier is an energy carrier that is delivered to and directly used by end users without further transformation.",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "name": {
+ "description": "A class label of the ontology term.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "final energy carrier"
+ ],
+ "badge": "Module",
+ "title": "Final Energy Carrier Subject Name"
+ },
+ "@id": {
+ "description": "A unique identifier (URI/IRI) of the ontology class.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "https://openenergyplatform.org/ontology/oeo/OEO_00140080"
+ ],
+ "badge": "Module",
+ "title": "Final Energy Carrier Subject Identifier",
+ "format": "uri"
+ }
+ },
+ "badge": "Module",
+ "title": "Final Energy Carrier Subject"
+ },
+ "badge": "Module",
+ "title": "Final Energy Carrier"
+ },
+ "demandSectors": {
+ "description": "An energy demand sector is a sector of the energy system that groups together energy consumers with similar usage characteristics.",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "name": {
+ "description": "A class label of the ontology term.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "energy demand sector"
+ ],
+ "badge": "Module",
+ "title": "Demand Sectors Subject Name"
+ },
+ "@id": {
+ "description": "A unique identifier (URI/IRI) of the ontology class.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "https://openenergyplatform.org/ontology/oeo/OEO_00000128"
+ ],
+ "badge": "Module",
+ "title": "Demand Sectors Subject Identifier",
+ "format": "uri"
+ }
+ },
+ "badge": "Module",
+ "title": "Demand Sectors Subject"
+ },
+ "badge": "Module",
+ "title": "Demand Sectors"
+ },
+ "moduleDescription": {
+ "description": "A description of the module. It should be usable as summary information for the module that is described by the metadata.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "Example module for an energy system dataset"
+ ],
+ "badge": "Module",
+ "title": "Energy Systems Module Description"
+ }
+ },
+ "badge": "Module",
+ "title": "Energy Systems Module"
+ },
+ "moduleMeasurementData": {
+ "description": "An Object that describes the instruments used in the measurement.",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "instrumentIdentifier": {
+ "description": "Unique string that identifies the instrument instance.",
+ "type": "string",
+ "examples": [
+ "http://hdl.handle.net/21.11157/a9250866-bbec-4542-86b3-a5f78c0c6922"
+ ],
+ "badge": "Module",
+ "title": "Instrument Identifier"
+ },
+ "instrumentPath": {
+ "description": "A landing page that the identifier resolves to.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "https://sms.atmohub.kit.edu/devices/961"
+ ],
+ "badge": "Module",
+ "title": "Instrument Path",
+ "format": "uri"
+ },
+ "instrumentName": {
+ "description": "Name by which the instrument instance is known.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "MFC_001000_02 - Merck KGaA - FC-2926V - DH9806004"
+ ],
+ "badge": "Module",
+ "title": "Instrument Name"
+ },
+ "instrumentOwner": {
+ "description": "Institution(s) responsible for the management of the instrument. This may include the legal owner, the operator, or an institute providing access to the instrument.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "Karlsruhe Institute of Technology (KIT)"
+ ],
+ "badge": "Module",
+ "title": "Instrument Owner"
+ },
+ "manufacturerName": {
+ "description": "Full name of the manufacturer.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "Merck KGaA"
+ ],
+ "badge": "Module",
+ "title": "Manufacturer Name"
+ },
+ "instrumentConfiguration": {
+ "description": "URL to a configuration of the instrument used for the experiment",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "https://example.com/my/experiment/instrument/config.yaml"
+ ],
+ "badge": "Module",
+ "title": "Instrument Configuration"
+ },
+ "moduleDescription": {
+ "description": "A description of the module. It should be usable as summary information for the module that is described by the metadata.",
+ "type": "string",
+ "examples": [
+ "Example instrument of PIDINST schema."
+ ],
+ "badge": "Module",
+ "title": "Module Description"
+ }
+ },
+ "badge": "Module",
+ "title": "Instrument",
+ "required": [
+ "instrumentIdentifier",
+ "moduleDescription"
+ ]
+ },
+ "badge": "Module",
+ "title": "Measurement Data Module"
+ },
"datasetLicenses": {
"description": "An array of objects of licenses under which the described data is provided.",
"type": "array",
@@ -534,10 +840,10 @@
}
},
"badge": "Bronze",
- "title": "License"
+ "title": "Dataset License"
},
"badge": "Bronze",
- "title": "Licenses"
+ "title": "Dataset Licenses"
},
"review": {
"description": "The metadata on the OEP can go through an open peer review process. See the Academy course [Open Peer Review](https://openenergyplatform.github.io/academy/courses/09_peer_review/) for further information.",
@@ -613,7 +919,7 @@
"null"
],
"examples": [
- "example.csv"
+ "oemetadata_table_example"
],
"badge": "Iron",
"title": "Name"
@@ -630,24 +936,6 @@
"badge": "Silver",
"title": "Title"
},
- "topics": {
- "description": "An array of predefined topics that correspond to the database schemas of the OEP.",
- "type": "array",
- "items": {
- "description": "The topics are used to group the data in the database.",
- "type": [
- "string",
- "null"
- ],
- "examples": [
- "model_draft"
- ],
- "badge": "Bronze",
- "title": "Topic"
- },
- "badge": "Bronze",
- "title": "Topics"
- },
"description": {
"description": "A description of the table. It should be usable as summary information for the table that is described by the metadata.",
"type": [
@@ -673,6 +961,24 @@
"title": "Publication Date",
"format": "date"
},
+ "topics": {
+ "description": "An array of predefined topics that correspond to the database schemas of the OEP.",
+ "type": "array",
+ "items": {
+ "description": "The topics are used to group the data in the database.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "examples": [
+ "model_draft"
+ ],
+ "badge": "Bronze",
+ "title": "Topic"
+ },
+ "badge": "Bronze",
+ "title": "Topics"
+ },
"subject": {
"description": "An array of objects that references to the subjects of the resource in ontology terms.",
"type": "array",
diff --git a/oemetadata/v2/v21/template.json b/oemetadata/v2/v21/template.json
index 99677cdd..48f59c9b 100644
--- a/oemetadata/v2/v21/template.json
+++ b/oemetadata/v2/v21/template.json
@@ -48,6 +48,50 @@
"comment": ""
}
],
+ "moduleEnergySystems": {
+ "supplyTechnologies": [
+ {
+ "name": "",
+ "@id": ""
+ }
+ ],
+ "storageTechnologies": [
+ {
+ "name": "",
+ "@id": ""
+ }
+ ],
+ "supplyGrid": [
+ {
+ "name": "",
+ "@id": ""
+ }
+ ],
+ "finalEnergyCarrier": [
+ {
+ "name": "",
+ "@id": ""
+ }
+ ],
+ "demandSectors": [
+ {
+ "name": "",
+ "@id": ""
+ }
+ ],
+ "moduleDescription": ""
+ },
+ "moduleMeasurementData": [
+ {
+ "instrumentIdentifier": "",
+ "instrumentPath": "",
+ "instrumentName": "",
+ "instrumentOwner": "",
+ "manufacturerName": "",
+ "instrumentConfiguration": "",
+ "moduleDescription": ""
+ }
+ ],
"datasetLicenses": [
{
"name": "",
@@ -68,11 +112,11 @@
"path": "",
"name": "",
"title": "",
+ "description": "",
+ "publicationDate": "",
"topics": [
""
],
- "description": "",
- "publicationDate": "",
"subject": [
{
"name": "",
diff --git a/test/oemetadata/v2/v21/test_example.py b/test/oemetadata/v2/v21/test_example.py
index 40283264..111f9104 100644
--- a/test/oemetadata/v2/v21/test_example.py
+++ b/test/oemetadata/v2/v21/test_example.py
@@ -11,6 +11,13 @@ def test_oemetadata_example_should_load():
print("Cannot open OEMetadata Example (v2.1)!")
+def test_oemetadata_example_modules_should_load():
+ try:
+ pass
+ except Warning:
+ print("Cannot open OEMetadata Example Modules (v2.1)!")
+
+
def test_oemetadata_schema_should_validate_oemetadata_example():
from jsonschema import ValidationError, validate
@@ -24,6 +31,19 @@ def test_oemetadata_schema_should_validate_oemetadata_example():
print("Cannot validate OEMetadata Example with Schema (v2.1)!", e)
+def test_oemetadata_schema_should_validate_oemetadata_example_modules():
+ from jsonschema import ValidationError, validate
+
+ from oemetadata.v2.v21.example_modules import OEMETADATA_V21_EXAMPLE_MODULES
+ from oemetadata.v2.v21.schema import OEMETADATA_V21_SCHEMA
+
+ try:
+ validate(OEMETADATA_V21_EXAMPLE_MODULES, OEMETADATA_V21_SCHEMA)
+ print("OEMetadata Example Modules is valid OEMetadata Schema (v2.1).")
+ except ValidationError as e:
+ print("Cannot validate OEMetadata Example Modules with Schema (v2.1)!", e)
+
+
def test_oemetadata_example_is_datapackage():
from frictionless import Package
@@ -32,3 +52,13 @@ def test_oemetadata_example_is_datapackage():
descriptor = OEMETADATA_V21_EXAMPLE.to_descriptor()
errors = list(Package.metadata_validate(descriptor))
assert not errors, [str(e) for e in errors]
+
+
+def test_oemetadata_example_modules_is_datapackage():
+ from frictionless import Package
+
+ from oemetadata.v2.v21.example_modules import OEMETADATA_V21_EXAMPLE_MODULES
+
+ descriptor = OEMETADATA_V21_EXAMPLE_MODULES.to_descriptor()
+ errors = list(Package.metadata_validate(descriptor))
+ assert not errors, [str(e) for e in errors]