Difference between revisions of "Schema Representations"
| Line 4: | Line 4: | ||
| − | The MOD-CO project is developing the conceptual and procedural meta-omics schema called '''"MOD-CO schema | + | The MOD-CO project is developing the conceptual and procedural meta-omics schema called '''"MOD-CO schema – a conceptual schema for processing sample data in meta’omics research"''' published in various kind of schema representations. With that, the MOD-CO schema is providing specifications useful for later software implementation and facilitates international standardisation processes. Certain [[Implementations| Implementations and Use Cases]] are provided. |
Revision as of 12:49, 7 February 2019
Conceptual and procedural schemas and community standards are established to provide a common understanding of the meaning or semantics of data, concepts and data pipelines. They are built on sets of vocabulary/ ontology terms which can be used to describe resources for the purposes of discovery. Schema(s) and standard(s) enable structured data management and data exchange between data storage structures relying on them. Schema(s) might rely on standard vocabularies. In the MOD-CO project context meta-omics-related vocabularies were evaluated.
The MOD-CO project is developing the conceptual and procedural meta-omics schema called "MOD-CO schema – a conceptual schema for processing sample data in meta’omics research" published in various kind of schema representations. With that, the MOD-CO schema is providing specifications useful for later software implementation and facilitates international standardisation processes. Certain Implementations and Use Cases are provided.
MOD-CO schema namespace in numbers
see under modco
Access to MOD-CO schema
Representation 1: versioned MOD-CO version 1.0 namespace scheme publication (static, snapshot): https://www.mod-co.net/wiki/MOD-CO_Schema_Reference
Representation 2: LOD-compliant MOD-CO version 1.0 namespace scheme publication under https://www.mod-co.net/wiki/MOD-CO with 2,463 'concepts', including 653 concepts (= 'concept classes' according to TDWG-compliant MediaWiki structure) and 1,810 (predefined) concept values (= 'concept properties' according to TDWG-compliant MediaWiki structure)
- The editing of concepts etc. for future versions is done in a master installation of DiversityDescriptions with export function.
- The editorial work will be followed by a regular data export and data import in the MOD-CO wiki for web access.
- The "View history" function of each wiki page is used to document the history of published editorial changes and have a documentation of the "issue date" and “modified date” for each single concept page.
Representation 3: SDD-structured XML document of MOD-CO version 1.0: MODCOschema1.0_SDDstructured.xml for download as ZIP archive here.
- This XML representation might be imported in any installation of the DiversityDescriptions application or other applications with interfaces for data exchange with SDD. For download of DiversityDescriptions database and client see https://diversityworkbench.net/Portal/DiversityDescriptions. For SDD as a metastandard see Standard Description Download and SDD Schema files SDD1.1rev5.
- A zip archive with SDD-structured XML document of MOD-CO version 1.0 will be available as data publication through GFBio data pipelines with appropriate GFBio parameter assignments and SNSB as GFBio data center.
Representation 4: two DiversityDescriptions installations at the SNSB IT Center with MOD-CO schema version 1.0, one as read-only access for anonymous DWB users (DWB cloud services) and the other for training and outreach purposes, i.e., integrated in the DWB Training environment.
Representation 5: Normative XSD (= XML Schema Definition) for MOD-CO schema version 1.0 is available under http://schema.mod-co.net/MOD-CO_1.0.xsd.
- The generation of the XSD with DiversityDescriptions is explained under MOD-CO normative XSD representation. The XSD is for validation of any external XML document assumed to be structured according MOD-CO concerning well-formedness. Validation might be done using any online XML validator.
