1 Definition | 2 Functional Requirements | 3 Syntax |
4 Semantics | 5 Conformance Testing | 6 Performance Assessment |
1 Definition
A region of an entity with Space-Time attributes that is further subdivided in Basic Locations.
2 Functional Requirements
A Location
- Has an extension limited in Space and Time.
- Is composed of Basic Locations, e.g.:
- A room can be a Basic Location of the Location defined as an apartment.
- An apartment can be a Basic Location of the Location defined as a building.
3 Syntax
https://schemas.mpai.community/OSD/V1.1/data/Location.json
4 Semantics
Label | Size | Description |
Header | N1 Bytes | Location Header |
– Standard | 9 Bytes | The characters “MMM-LOC-V” |
– Version | N2 Bytes | Major version |
– Dot-separator | 1 Byte | The character “.” |
– Subversion | N3 Bytes | Minor version |
MInstanceID | N4 Bytes | Identifier of M-Instance. |
LocationID | N5 Bytes | Identifier of Location. |
LocationData | N6 Bytes | Locations and Basic-Locations composing the Location. |
– BasicLocation | N7 Bytes | A Basic Location composing the Location. |
– Time | N8 Bytes | Time of validity of Basic Location in Location |
DescrMetadata | N9 Bytes | Descriptive Metadata. |
5 Conformance Testing
A Data instance Conforms with Location (OSD-LOC) V1.2 if:
- The Data validates against the Location’s JSON Schema.
- All Data in the Location’s JSON Schema
- Have the specified type
- Validate against their JSON Schemas
- Conform with their Data Qualifiers if present.
6 Performance Assessment