Data classes - aus-plant-phenomics-network/appn-implementation GitHub Wiki

See the pages for each class for definitions, interrelationships and APPN publication strategies for associated instance data.

schema.org base classes

• MediaObject as File
• Dataset
• Organization
• Person
• SoftwareApplication

RO-Crate alias

• File

MIAPPE classes

MIAPPE classes are preferred where these are present and well-defined.

• DataFile as File
• GrowthFacility
• Institution as Organization
• Investigation
• Method
• ObservationUnit
• ObservedVariable
• Person
• Sample
• Scale
• Study
• Trait

SOSA classes

MIAPPE does not include any representation for Sensors and sensor Platforms. APPN is adopting these and other relevant classes from SSN/SOSA:

• Deployment (SSN class - http://www.w3.org/ns/ssn/Deployment)
• FeatureOfInterest (SOSA class - http://www.w3.org/ns/sosa/FeatureOfInterest) as ObservationUnit
• Observation (SOSA class - http://www.w3.org/ns/sosa/Observation)
• ObservableProperty (SOSA class - http://www.w3.org/ns/sosa/ObservableProperty) as ObservedVariable
• Platform (SOSA class - http://www.w3.org/ns/sosa/Platform)
• Procedure (SOSA class - http://www.w3.org/ns/sosa/Procedure) as Method
• Result (SOSA class - http://www.w3.org/ns/sosa/Result)
• Sample (SOSA class - http://www.w3.org/ns/sosa/Sample)
• Sampling (SOSA class - http://www.w3.org/ns/sosa/Sampling)
• Sensor (SOSA class - http://www.w3.org/ns/sosa/Sensor)

PROV-O classes

PROV-O is well-defined and provides generalised concepts important to modelling data values.

• Activity
• Agent
• Entity as Result

Software Ontology classes

If additional detail is required for software components, the Software Ontology will be used.

• Software as Software

Units Ontology

The Units Ontology may help to formalise the values recorded in data.

• Quality as ObservedVariable
• Unit as Scale