Convert between OO-LD schemas and SAMM aspect models (Eclipse Semantic Modeling Framework).
Spec-side siblings: OO-LD/oold-schema#119 (generating OO-LD schemas from an existing source model) and OO-LD/oold-schema#107 (QuantityValue as a base building block).
Mapping
- Aspect to the top-level object schema, Entity to nested object schemas, Property to schema properties
- SAMM is RDF/Turtle based, so the OO-LD
@context is the natural source and target for the IRIs
SAMM Characteristics overlap substantially with existing concepts in world.opensemantic.core, which should be reused rather than re-invented:
- Characteristic, the elementary building block for object data schemas, which can inherit, reuse or define properties from other Characteristics
- CharacteristicType, a set of properties intended for use in other characteristic types or classes
- QuantityValue (
value, unit) and QuantityValueType (quantity, default_unit), which cover the SAMM Quantifiable and Unit cases
Open questions
- How far the SAMM Characteristic model and the OSW Characteristic / CharacteristicType model actually align, and where they diverge
- Which Characteristics and Constraints have no JSON Schema counterpart, and what happens to them
- Overlap with the AAS submodel converter: AAS submodel templates can be generated from SAMM, so decide whether to chain through SAMM or convert independently
- Which SAMM version to target
Convert between OO-LD schemas and SAMM aspect models (Eclipse Semantic Modeling Framework).
Spec-side siblings: OO-LD/oold-schema#119 (generating OO-LD schemas from an existing source model) and OO-LD/oold-schema#107 (QuantityValue as a base building block).
Mapping
@contextis the natural source and target for the IRIsSAMM Characteristics overlap substantially with existing concepts in
world.opensemantic.core, which should be reused rather than re-invented:value,unit) and QuantityValueType (quantity,default_unit), which cover the SAMM Quantifiable and Unit casesOpen questions