1、 ETSI TS 118 112 V2.0.0 (2016-09) oneM2M; Base Ontology (oneM2M TS-0012 version 2.0.0 Release 2) floppy3TECHNICAL SPECIFICATION ETSI ETSI TS 118 112 V2.0.0 (2016-09)2oneM2M TS-0012 version 2.0.0 Release 2Reference DTS/oneM2M-000012 Keywords M2M, ontology ETSI 650 Route des Lucioles F-06921 Sophia An
2、tipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present
3、 document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions
4、 and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the curre
5、nt status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No par
6、t may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the forego
7、ing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the be
8、nefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 118 112 V2.0.0 (2016-09)3oneM2M TS-0012 version 2.0.0 Release 2Contents Intellectual Property Rights 6g3Foreword . 6g31 Scope 7g32 References 7
9、g32.1 Normative references . 7g32.2 Informative references 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Conventions 9g35 General information on the oneM2M Base Ontology (informative) 9g35.1 Motivation and intended use of the ontology . 9g35.1.1 Why using ontolo
10、gies in oneM2M? 9g35.1.1.1 Introduction to ontologies . 9g35.1.1.2 The purpose of the oneM2M Base Ontology 10g35.1.1.2.0 Introduction . 10g35.1.1.2.1 Syntactic interoperability . 10g35.1.1.2.2 Semantic interoperability. 11g35.1.2 How are the Base Ontology and external ontologies used? 11g35.1.2.1 Ov
11、erview . 11g35.1.2.2 Introduction to usage of classes, properties and restrictions . 11g35.1.2.3 Methods for jointly using the Base Ontology and external ontologies . 12g35.2 Insights into the Base Ontology . 13g35.2.1 General design principles of the Base Ontology . 13g35.2.1.1 General Principle .
12、13g35.2.1.2 Essential Classes and Properties of the Base Ontology . 14g35.2.2 Use of ontologies for Generic interworking with Area Networks 17g35.2.2.1 General Principle . 17g36 Description of Classes and Properties 19g36.1 Classes 19g36.1.1 Class: Thing 19g36.1.2 Class: ThingProperty 20g36.1.3 Clas
13、s: Aspect 21g36.1.4 Class: MetaData 22g36.1.5 Class: Device 23g36.1.6 Class: InterworkedDevice . 25g36.1.7 Class: AreaNetwork 26g36.1.8 Class: Service 27g36.1.9 Class: Functionality 28g36.1.9.0 General description . 28g36.1.9.1 Class: ControllingFunctionality 29g36.1.9.2 Class: MeasuringFunctionalit
14、y 30g36.1.10 Class: Operation 31g36.1.10.0 General description . 31g36.1.10.1 Class: GET_InputDataPoint 32g36.1.10.2 Class: SET_OutputDataPoint 33g36.1.11 Class: Command . 34g36.1.12 Class: OperationInput . 35g36.1.13 Class: OperationOutput . 36g36.1.14 Class: OperationState 38g36.1.15 Class: InputD
15、ataPoint . 39g36.1.16 Class: OutputDataPoint . 41g36.1.17 Class: Variable 42g36.1.18 Class: SimpleTypeVariable 44g3ETSI ETSI TS 118 112 V2.0.0 (2016-09)4oneM2M TS-0012 version 2.0.0 Release 26.2 Object Properties 45g36.2.1 Void 45g36.2.2 Void 45g36.2.3 Object Property: consistsOf 45g36.2.4 Object Pr
16、operty: describes 45g36.2.5 Object Property: exposesCommand 45g36.2.6 Object Property: exposesFunctionality . 46g36.2.7 Object Property: hasCommand . 46g36.2.8 Object Property: hasFunctionality 46g36.2.9 Object Property: hasInput . 46g36.2.10 Object Property: hasInputDataPoint . 47g36.2.11 Object Pr
17、operty: hasMetaData 47g36.2.12 Void 47g36.2.13 Object Property: hasOperation 47g36.2.14 Object Property: hasOperationState 47g36.2.15 Void 48g36.2.16 Object Property: hasOutput 48g36.2.17 Object Property: hasOutputDataPoint . 48g36.2.18 Object Property: hasService 48g36.2.19 Object Property: hasSubS
18、tructure . 48g36.2.20 Object Property: hasThingProperty 49g36.2.21 Object Property: hasThingRelation . 49g36.2.22 Void 49g36.2.23 Void 49g36.2.24 Void 49g36.2.25 Object Property: isPartOf 49g36.2.26 Object Property: refersTo . 49g36.3 Data Properties . 50g36.3.1 Data Property: hasDataType . 50g36.3.
19、2 Data Property: hasDataRestriction 51g36.3.2.0 General description . 51g36.3.2.1 Data Property: hasDataRestriction_minInclusive . 52g36.3.2.2 Data Property: hasDataRestriction_maxInclusive. 52g36.3.2.3 Data Property: hasDataRestriction_minExclusive 52g36.3.2.4 Data Property: hasDataRestriction_maxE
20、xclusive 52g36.3.2.5 Data Property: hasDataRestriction_length 52g36.3.2.6 Data Property: hasDataRestriction_minLength . 52g36.3.2.7 Data Property: hasDataRestriction_maxLength 52g36.3.2.8 Data Property: hasDataRestriction_pattern . 52g36.3.2.9 Data Property: hasDataRestriction_langRange . 52g36.3.3
21、Data Property: hasValue . 52g36.3.4 Data Property: netTechnologyCommunicationProtocol . 53g36.3.5 Data Property: netTechnologyPhysicalStandard. 53g36.3.6 Data Property: netTechnologyProfile . 53g36.3.7 Data Property: oneM2MTargetURI 53g36.3.8 Data Property: oneM2MAttribute . 54g36.3.9 Data Property:
22、 oneM2MMethod . 54g36.4 Annotation Properties . 55g36.4.1 Annotation Property: resourceDescriptorLink 55g37 Instantiation of the Base Ontology and external ontologies to the oneM2M System 55g37.1 Instantiation rules for the Base Ontology . 55g37.1.1 Instantiation of classes of the oneM2M Base Ontolo
23、gy and derived external ontologies in the oneM2M System: 55g37.1.1.1 General on instantiating classes of the Base Ontology in the oneM2M System . 55g37.1.1.2 Instantiation of individual classes of the Base Ontology 56g37.1.2 Instantiation of Object Properties . 61g37.1.3 Instantiation of Data Proper
24、ties 61g37.1.4 Instantiation of Annotation Properties 61g37.2 Common mapping principles between the Base Ontology and external ontologies . 62g38 Functional specification of communication with the Generic interworking IPE . 63g3ETSI ETSI TS 118 112 V2.0.0 (2016-09)5oneM2M TS-0012 version 2.0.0 Relea
25、se 28.1 Usage of oneM2M resources for IPE communication . 63g38.1.1 General design principles (informative) . 63g38.1.2 Parent-child and linking resource relationships 63g38.2 Specification of the IPE for Generic interworking . 65g38.2.1 General functionality of a Generic interworking IPE . 65g38.2.
26、2 Interworked Device discovery 65g38.2.3 Handling of DataPoints by the IPE . 66g38.2.4 Handling of Operations by the IPE . 66g38.2.5 Removing Devices. . 68g38.3 Specification of the behavior of a communicating entity in message flows between IPE and the communicating entity . 68g38.3.1 Preconditions
27、 on the communicating entity 68g38.3.2 Flow from the communicating entity to the IPE using InputDataPoints of a Service . 68g38.3.2.1 Flow from the communicating entity to the IPE using a type InputDataPoint . 68g38.3.2.2 Flow from the communicating entity to the IPE using a type InputDataPoint 69g3
28、8.3.3 Flow from the IPE to the communicating entity using OutputDataPoints of a Service 70g38.3.4 Flow from the communicating entity to the IPE using Operations of a Service . 70g38.3.5 Flow from the IPE to the communicating entity using Operations of a Service . 70g39 FlexContainer specializations
29、for Generic interworking 71g39.1 Introduction 71g39.2 Resource Type genericInterworkingService. 71g39.3 Resource Type genericInterworkingOperationInstance 73g3Annex A (normative): OWL representation of Base Ontology 78g3Annex B (informative): Mappings of selected external ontologies to the Base Onto
30、logy 79g3B.1 Mapping of SAREF 79g3B.1.1 Introduction to SAREF . 79g3B.1.2 Sub-class mapping relationship between SAREF and the Base Ontology . 80g3B.1.3 Mapping SAREF to oneM2M resource structure . 82g3B.1.3.1 Introduction. 82g3B.1.3.2 Mapping rules . 82g3B.1.3.3 Example showing the uses of the sema
31、nticDescriptor resource and instantiation in the oneM2M resource structure 82g3History 88g3ETSI ETSI TS 118 112 V2.0.0 (2016-09)6oneM2M TS-0012 version 2.0.0 Release 2Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The info
32、rmation pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the
33、 ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or th
34、e updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI TS 118 112 V2.0.0 (2016-09)7oneM2M TS-0012 version 2.0.0 Release 21 Scope The
35、present document contains the specification of the oneM2M base ontology. A formal OWL representation of the base ontology can be found at http:/www.onem2m.org/ontology/Base_Ontology. The present document also specifies an instantiation of the base ontology in oneM2M resources which is required for g
36、eneric interworking. In addition the present document contains the functional specification for an Interworking Proxy Application Entity (IPE), the oneM2M resources and their usage for generic interworking. Finally an example is given how external ontologies can be mapped to the base ontology. The e
37、xample uses the Smart Appliances REFerence (SAREF) ontology (http:/ontology.tno.nl/saref). 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version
38、 applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: While any hyperlinks included
39、 in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI TS 118 111: “oneM2M; Common Terminology (oneM2M TS-0011)“. 2 ETSI TS 118 001: “oneM2M; Functiona
40、l Architecture (oneM2M TS-0001)“. 3 W3C Recommendation: “RDF 1.1 Concepts and Abstract Syntax“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version appli
41、es. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not nece
42、ssary for the application of the present document but they assist the user with regard to a particular subject area. i.1 oneM2M Drafting Rules. NOTE: Available at http:/www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf. i.2 The Smart Appliances REFerence (SAREF) ontology. NOTE: Available at http
43、:/ontology.tno.nl/saref/. i.3 Open-source ontology editor PROTG. NOTE: Available at http:/protege.stanford.edu/. i.4 W3C OWL Working Group: “OWL 2 Web Ontology Language Document Overview“. ETSI ETSI TS 118 112 V2.0.0 (2016-09)8oneM2M TS-0012 version 2.0.0 Release 2NOTE: Available at http:/www.w3.org
44、/TR/owl2-overview/. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 1 and the following apply: annotation property: property that can be used to add information (metadata/data about data) to classes, individ
45、uals and Object/Data Properties class: OWL standard ontology language from the World Wide Web Consortium (W3C) (see i.4), Concepts are called “Classes“ concept: entity of an Ontology that has an agreed, well defined, meaning within the domain of interest of that ontology NOTE: A Concept is conceptua
46、lly grouping a set of Individuals. data property: property that relates an individual of a Class to data of a stecified type and range interworked device: non-oneM2M device (NoDN) for which communication with oneM2M entities can be achieved via an Interworking Proxy Application Entity (IPE) ontology
47、: formal specification of a conceptualization, that is defining Concepts as objects with their properties and relationships versus other Concepts generic interworking: generic interworking allows interworking with many types of non- oneM2M Area Networks and Devices that are described in the form of
48、a oneM2M compliant ontology which is derived from the oneM2M Base Ontology NOTE: Generic interworking supports the interworking variant “full mapping of the semantic of the non-oneM2M data model to Mca“ as indicated in clause F.2 of oneM2M TS-0001 2. object property: property that relates an individ
49、ual of a domain Class to an individual of a range Class property: in OWL standard ontology language Properties represent relations among individuals NOTE: Properties can be sub-categorized as Object Properties, Data Properties and Annotation Properties. proxied device: virtual Device (i.e. a set of oneM2M resources together with an IPE) that represents the Interworked Device in the oneM2M System relation: (also called “interrelation“ or “property“) stating a relationship among individuals restriction: describes a class of individuals based on the
