The present document gives guidance and provisions for making IoT smart applications and products interoperable at the semantic level in compliance to the SAREF framework. It contains provisions about how to use SAREF, points to the relevant existing Technical Reports and Technical Specifications and specifies a methodology to follow for showing SAREF compliance according to the present SAREF EN. Further on, it describes how to contribute optionally to a new SAREF extension (if what Users need is not yet in the SAREF framework).
The present document addresses parties involved in the development and manufacturing of IoT smart applications and products, who might take different roles in their organization like:
• executives and product owners, who decide on to invest in a SAREF-compliant product;
• developers, who will implement a SAREF-compliant product as non-ontology experts or even ontology experts.
Different roles imply different intentions and expectations when reading the present document according to their tasks in the organization. The present document considers this by its implemented structure. Clause 4 provides guidance about how to go throughout the present document in order to judge, which clauses might be essential for the special role of the reader and which ones might be skipped.
The present document is structured as follows:
• Clauses 1 to 3 set the scene and provide references as well as definitions of terms, symbols and abbreviations, which are used in the present document.
• Clause 4 defines the motivation and principles shared by those who are reading the present document also serving as a checkpoint whether the reader is in the right place or not. It includes a brief reading guide as not everyone needs to read every part of the present document, depending on the reader's role and expertise.
• Clause 5.1 provides guidance about the best practice of specifying use cases as the important basis for deriving requirements from them.
• Clause 5.2 provides guidance/provisions about identifying core elements from the use cases defined in clause 5.1.
• Clause 5.3 describes, how to get acquainted with SAREF.
• Clause 5.4 provides guidance /provisions about ensuring that the correct (latest) versions of the relevant SAREF modules/patterns/extensions are selected. It illustrates, how to document the version of those SAREF modules, which the product, application, or possible ontology extension is compliant to.
• Clause 6.1 provides guidance/provisions about the translation of data into SAREF.
• Clause 6.2 gives guidance about testing "SAREF-compliant data" in one example application of interoperability exchange with another organization/manufacturer/brand.
• Clause 7.1 provides guidance/provisions about creating a new SAREF extension (or pattern).
• Clause 7.2 provides guidance/provisions about checking SAREF compliance of a new created SAREF extension without going (yet) to an official standardization contribution to ETSI.
• Clause 8 describes the process of incorporating a new created SAREF extension according to clause 7 in the official standardization process in ETSI, which will then result in a new official extension/pattern (SAREF4abcd) under the ETSI SAREF namespace.
• Annex A contains an example of a possible use case to provide context to clause 5.1.
• Annex B contains examples of relevant core elements from use cases to provide context to clause 5.2.
• Annex C contains examples of translating data into SAREF-compliant data to provide context to clause 6.1.
• Annex D contains examples of testing SAREF data to provide context to clause 6.2.
• Annex E provides a short summary of SAREF ontology development methodology with figures and different phases.
• Annex F provides a mechanism for the User of the present document (who is expected to be an entity involved in the development and manufacturing of IoT smart applications and products) to give information about the implementation of the provisions within the present document.
• Annex G provides an example of how to enhance the SAREF core with its extensions to give context to clause 7.
Required fields are indicated with *
