Guide for Extensions
1 Getting aligned with FIESTA-IoT’s semantic data models
1.4 Best practices for producing valid the annotations
Below we describe some of the best practices that testbed owners should follow in order to create annotation. Please note that the APIs provided in the section 1.6 already use/satisfy the best practices. The best practices are:
The following list represents the fields that you have to fill for every elements you want to bring to the ontology/taxonomy:
- Do not use blank nodes. Create individuals for concepts used
- Have meaningful URIs for Individuals
- Respect the cardinality provided within the ontology
- Do not push unnecessary/fake/test data
- Remove unused concepts. They might cause validation errors. Further, you are not obliged to provide certain tuples that have predicates such as http://www.w3.org/2002/07/owl#equivalentProperty, http://www.w3.org/2002/07/owl#inverseOf
- ssn:SensingDevice individuals should have identical URIs in observation graph and resource graph
- In observation realm, use both ssn:madeObservation and ssn:observedBy. This also applies to all other properties that have inverse relationships.
- Do not abuse iot-lite:Metadata by providing just any information about the sensing device.
- Get the annotations validated first before pushing data to FIESTA-IoT repository by using certification portal or validation services.