The OCF specifications are divided into two sets of documents:<\/p>\n
Core Specification documents: The Core Specification documents specify the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems.<\/p>\n<\/li>\n
Vertical Profiles Specification documents: The Vertical Profiles Specification documents specify the OCF profiles to enable IoT usages for different market segments such as smart home, industrial, healthcare, and automotive. The Application Profiles Specification is built upon the interfaces and network security of the OCF core architecture defined in the Core Specification.<\/p>\n<\/li>\n<\/ul>\n
This document is the OCF Core specification which specifies the Framework and core architecture.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 4<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 3 Terms, definitions, symbols and abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 3.2 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 3.3 Conventions 3.4 Data types <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 4 Document conventions and organization <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 5 Architecture 5.1 Overview <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 5.2 Principle <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 5.3 Functional block diagram <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 5.4 Framework 5.5 Example Scenario with roles <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 5.6 Example Scenario: Bridging to Non- OCF ecosystem <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 6 Identification and addressing 6.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 6.2 Identification 6.2.1 Resource identification and addressing <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 6.3 Namespace: 6.4 Network addressing 7 Resource model 7.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 7.2 Resource <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 7.3 Property 7.3.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 7.3.2 Common Properties 7.3.2.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 7.3.2.2 Property Name and Property Value definitions 7.3.2.3 Resource Type 7.3.2.4 Interface 7.3.2.5 Name 7.3.2.6 Resource Identity 7.4 Resource Type 7.4.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 7.4.2 Resource Type Property 7.4.3 Resource Type definition <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 7.4.4 Multi-value “rt” Resource 7.5 Device Type <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 7.6 Interface 7.6.1 Introduction 7.6.2 Interface Property <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 7.6.3 Interface methods 7.6.3.1 Overview 7.6.3.2 Baseline Interface 7.6.3.2.1 Overview 7.6.3.2.2 Use of RETRIEVE <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 7.6.3.2.3 Use of UPDATE 7.6.3.3 Link List Interface 7.6.3.3.1 Overview 7.6.3.3.2 Example: \u201clinks list\u201d Interface <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 7.6.3.4 Batch Interface 7.6.3.4.1 Overview <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 7.6.3.4.2 Use of Query Parameters with Batch 7.6.3.4.3 Examples: Batch Interface <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 7.6.3.5 Actuator Interface <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 7.6.3.6 Sensor Interface <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | 7.6.3.7 Read-only Interface 7.6.3.8 Read-write Interface <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 7.7 Resource representation 7.8 Structure 7.8.1 Introduction 7.8.2 Resource Relationships <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 7.8.2.1 Parameters 7.8.2.1.1 \u201cins\u201d or Link Instance Parameter 7.8.2.1.2 \u201cp\u201d or Policy Parameter <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | 7.8.2.1.3 \u201ctype\u201d or Media Type Parameter 7.8.2.1.4 \u201cbp\u201d or the Batch Interface Parameter <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | 7.8.2.1.5 \u201cdi\u201d or Device ID parameter 7.8.2.1.6 \u201ceps\u201d Parmeter <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | 7.8.2.2 Formatting 7.8.2.3 List of Links in a Collection 7.8.3 Collections 7.8.3.1 Overview <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | 7.8.3.2 Collection Properties <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | 7.8.3.3 Default Resource Type 7.9 Third (3rd) party specified extensions <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | 8 CRUDN 8.1 Overview <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | 8.2 CREATE <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | 8.2.1 CREATE request 8.2.2 Processing by the Server 8.2.3 CREATE response 8.3 RETRIEVE <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | 8.3.1 RETRIEVE request 8.3.2 Processing by the Server 8.3.3 RETRIEVE response 8.4 UPDATE <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | 8.4.1 UPDATE request 8.4.2 Processing by the Server 8.4.3 UPDATE response 8.5 DELETE <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | 8.5.1 DELETE request 8.5.2 Processing by the Server 8.5.3 DELETE response 8.6 NOTIFY 8.6.1.1 NOTIFICATION response <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | 9 Network and connectivity 9.1 Introduction 9.2 Architecture <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | 9.3 IPv6 network layer requirements 9.3.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | 9.3.2 IPv6 node requirements 9.3.2.1 Introduction 9.3.2.2 IP Layer 10 Endpoint 10.1 Endpoint definition <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | 10.2 Endpoint information 10.2.1 Introduction 10.2.2 \u201cep\u201d 10.2.3 \u201cpri\u201d <\/td>\n<\/tr>\n | ||||||
| 76<\/td>\n | 10.2.4 Endpoint information in “eps” Parameter 10.3 Endpoint discovery 10.3.1 Introduction 10.3.2 Implicit discovery 10.3.3 Explicit discovery with \u201c\/oic\/res\u201d response <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | 10.4 CoAP based Endpoint discovery <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | 11 Functional interactions 11.1 Introduction 11.2 Onboarding, Provisioning and Configuration <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | 11.3 Resource discovery 11.3.1 Introduction 11.3.2 Resource based discovery: mechanisms 11.3.2.1 Overview <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | 11.3.2.2 Direct discovery 11.3.2.3 Indirect discovery of Resources (resource directory based discovery) <\/td>\n<\/tr>\n | ||||||
| 85<\/td>\n | 11.3.2.4 Advertisement Discovery 11.3.3 Resource based discovery: Information publication process <\/td>\n<\/tr>\n | ||||||
| 86<\/td>\n | 11.3.4 Resource based discovery: Finding information <\/td>\n<\/tr>\n | ||||||
| 92<\/td>\n | 11.3.5 Resource discovery using \u201c\/oic\/res\u201d <\/td>\n<\/tr>\n | ||||||
| 94<\/td>\n | 11.3.6 Resource directory (RD) based discovery 11.3.6.1 Introduction 11.3.6.1.1 Indirect discovery for lookup of the resources <\/td>\n<\/tr>\n | ||||||
| 95<\/td>\n | 11.3.6.1.2 Resource directory <\/td>\n<\/tr>\n | ||||||
| 97<\/td>\n | 11.3.6.2 RD discovery 11.3.6.2.1 Discovering a resource directory <\/td>\n<\/tr>\n | ||||||
| 99<\/td>\n | 11.3.6.2.2 RD selection process 11.3.6.2.2.1 Selection criteria <\/td>\n<\/tr>\n | ||||||
| 100<\/td>\n | 11.3.6.2.2.2 Selection scenarios 11.3.6.3 Resource publish 11.3.6.3.1 Publish resources 11.3.6.3.1.1 Overview <\/td>\n<\/tr>\n | ||||||
| 101<\/td>\n | 11.3.6.3.1.2 Publish: Push resource information <\/td>\n<\/tr>\n | ||||||
| 103<\/td>\n | 11.3.6.3.2 Update resource information 11.3.6.3.3 Delete resource information <\/td>\n<\/tr>\n | ||||||
| 104<\/td>\n | 11.3.6.3.4 Transfer resource information from one RD to another 11.3.6.4 Resource exposure 11.3.6.4.1 \u201c\/oic\/res\u201d and retrieving of the resources <\/td>\n<\/tr>\n | ||||||
| 108<\/td>\n | 11.4 Notification 11.4.1 Overview 11.4.2 Observe <\/td>\n<\/tr>\n | ||||||
| 109<\/td>\n | 11.4.2.1 RETRIEVE request with observe indication 11.4.2.2 Processing by the Server 11.4.2.3 RETRIEVE response with observe indication <\/td>\n<\/tr>\n | ||||||
| 110<\/td>\n | 11.4.2.4 Resource monitoring by the Server 11.4.2.5 Additional RETRIEVE responses with observe indication 11.4.2.6 Cancelling Observe 11.5 Device management 11.5.1 Overview 11.5.2 Diagnostics and maintenance <\/td>\n<\/tr>\n | ||||||
| 111<\/td>\n | 11.6 Scenes 11.6.1 Introduction 11.6.2 Scenes 11.6.2.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 112<\/td>\n | 11.6.2.2 Scene creation <\/td>\n<\/tr>\n | ||||||
| 113<\/td>\n | 11.6.2.3 Interacting with Scenes <\/td>\n<\/tr>\n | ||||||
| 115<\/td>\n | 11.6.2.4 Summary of Resource Types defined for Scene functionality 11.6.3 Security considerations 11.7 Icons 11.7.1 Overview <\/td>\n<\/tr>\n | ||||||
| 116<\/td>\n | 11.7.2 Resource 11.8 Introspection 11.8.1 Overview <\/td>\n<\/tr>\n | ||||||
| 118<\/td>\n | 11.8.2 Usage of introspection <\/td>\n<\/tr>\n | ||||||
| 119<\/td>\n | 12 Messaging 12.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 120<\/td>\n | 12.2 Mapping of CRUDN to CoAP 12.2.1 Overview 12.2.2 URIs 12.2.3 CoAP method with request and response 12.2.3.1 Overview <\/td>\n<\/tr>\n | ||||||
| 121<\/td>\n | 12.2.3.2 CREATE with POST or PUT 12.2.3.2.1 With POST 12.2.3.2.2 With PUT 12.2.3.3 RETRIEVE with GET <\/td>\n<\/tr>\n | ||||||
| 122<\/td>\n | 12.2.3.4 UPDATE with POST 12.2.3.5 DELETE with DELETE 12.2.4 Content-Format negotiation <\/td>\n<\/tr>\n | ||||||
| 123<\/td>\n | 12.2.5 OCF-Content-Format-Version information 12.2.6 Content-Format policy <\/td>\n<\/tr>\n | ||||||
| 124<\/td>\n | 12.2.7 CRUDN to CoAP response codes 12.2.8 CoAP block transfer <\/td>\n<\/tr>\n | ||||||
| 125<\/td>\n | 12.3 CoAP serialization over TCP 12.3.1.1 Introduction 12.3.1.2 Indication of support 12.3.1.3 Message type and header 12.3.1.4 URI scheme 12.3.1.5 KeepAlive 12.3.1.5.1 Overview 12.3.1.5.2 KeepAlive Mechanism <\/td>\n<\/tr>\n | ||||||
| 126<\/td>\n | 12.4 Payload Encoding in CBOR 13 Security <\/td>\n<\/tr>\n | ||||||
| 128<\/td>\n | Annex A (informative) Operation Examples A.1 Introduction A.2 When at home: From smartphone turn on a single light <\/td>\n<\/tr>\n | ||||||
| 129<\/td>\n | A.3 GroupAction execution A.4 When garage door opens, turn on lights in hall; also notify smartphone A.5 Device management <\/td>\n<\/tr>\n | ||||||
| 131<\/td>\n | Annex B (informative) OCF interaction scenarios and deployment models B.1 OCF interaction scenarios <\/td>\n<\/tr>\n | ||||||
| 132<\/td>\n | B.2 Deployment model <\/td>\n<\/tr>\n | ||||||
| 134<\/td>\n | Annex C (informative) Other Resource Models and OCF Mapping C.1 Multiple resource models C.2 OCF approach for support of multiple resource models <\/td>\n<\/tr>\n | ||||||
| 135<\/td>\n | C.3 Resource model indication C.4 An Example Profile (IPSO profile) C.4.1 Conceptual equivalence <\/td>\n<\/tr>\n | ||||||
| 138<\/td>\n | Annex D (normative) Resource Type definitions D.1 List of Resource Type definitions <\/td>\n<\/tr>\n | ||||||
| 139<\/td>\n | D.2 OCF Collection D.2.1 Introduction D.2.2 Example URI D.2.3 Resource Type D.2.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 144<\/td>\n | D.2.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 145<\/td>\n | D.2.6 CRUDN behavior D.2.7 Referenced JSON schemas D.2.8 oic.oic-link-schema.json <\/td>\n<\/tr>\n | ||||||
| 147<\/td>\n | D.3 Device Configuration D.3.1 Introduction D.3.2 Example URI D.3.3 Resource Type D.3.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 152<\/td>\n | D.3.5 Property Definition D.3.6 CRUDN behavior D.4 Platform Configuration D.4.1 Introduction D.4.2 Example URI D.4.3 Resource Type D.4.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 155<\/td>\n | D.4.5 Property Definition D.4.6 CRUDN behavior D.5 Device D.5.1 Introduction D.5.2 Wellknown URI D.5.3 Resource Type <\/td>\n<\/tr>\n | ||||||
| 156<\/td>\n | D.5.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 158<\/td>\n | D.5.5 Property Definition D.5.6 CRUDN behavior <\/td>\n<\/tr>\n | ||||||
| 159<\/td>\n | D.6 Maintenance D.6.1 Introduction D.6.2 Wellknown URI D.6.3 Resource Type D.6.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 161<\/td>\n | D.6.5 Property Definition D.6.6 CRUDN behavior <\/td>\n<\/tr>\n | ||||||
| 162<\/td>\n | D.7 Platform D.7.1 Introduction D.7.2 Wellknown URI D.7.3 Resource Type D.7.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 164<\/td>\n | D.7.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 165<\/td>\n | D.7.6 CRUDN behavior D.8 Ping D.8.1 Introduction D.8.2 Wellknown URI D.8.3 Resource Type D.8.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 167<\/td>\n | D.8.5 Property Definition D.8.6 CRUDN behavior D.9 Discoverable Resources Baseline Interface D.9.1 Introduction D.9.2 Wellknown URI D.9.3 Resource Type D.9.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 169<\/td>\n | D.9.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 170<\/td>\n | D.9.6 CRUDN behavior D.10 Discoverable Resources Link List interface D.10.1 Introduction D.10.2 Wellknown URI D.10.3 Resource Type D.10.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 171<\/td>\n | D.10.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 172<\/td>\n | D.10.6 CRUDN behavior <\/td>\n<\/tr>\n | ||||||
| 173<\/td>\n | D.10.7 Referenced JSON schemas D.10.8 oic.oic-link-schema.json <\/td>\n<\/tr>\n | ||||||
| 175<\/td>\n | D.11 Scenes (Top level) D.11.1 Introduction D.11.2 Example URI D.11.3 Resource Type D.11.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 177<\/td>\n | D.11.5 Property Definition D.11.6 CRUDN behavior D.12 Scene Collections D.12.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 178<\/td>\n | D.12.2 Example URI D.12.3 Resource Type D.12.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 181<\/td>\n | D.12.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 182<\/td>\n | D.12.6 CRUDN behavior D.13 Scene Member D.13.1 Introduction D.13.2 Example URI D.13.3 Resource Type D.13.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 184<\/td>\n | D.13.5 Property Definition D.13.6 CRUDN behavior D.14 Resource directory resource D.14.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 185<\/td>\n | D.14.2 Wellknown URI D.14.3 Resource Type D.14.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 190<\/td>\n | D.14.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 191<\/td>\n | D.14.6 CRUDN behavior D.15 Icon D.15.1 Introduction D.15.2 Example URI D.15.3 Resource Type D.15.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 192<\/td>\n | D.15.5 Property Definition D.15.6 CRUDN behavior <\/td>\n<\/tr>\n | ||||||
| 193<\/td>\n | D.16 Introspection Resource D.16.1 Introduction D.16.2 Example URI D.16.3 Resource Type D.16.4 RAML Definition <\/td>\n<\/tr>\n | ||||||
| 194<\/td>\n | D.16.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 195<\/td>\n | D.16.6 CRUDN behavior <\/td>\n<\/tr>\n | ||||||
| 196<\/td>\n | Annex E (informative) Swagger2.0 definitions E.1 Icon E.1.1 Introduction E.1.2 Example URI E.1.3 Resource Type E.1.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 198<\/td>\n | E.1.5 Property Definition E.1.6 CRUDN behavior <\/td>\n<\/tr>\n | ||||||
| 199<\/td>\n | E.2 Introspection Resource E.2.1 Introduction E.2.2 Example URI E.2.3 Resource Type E.2.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 201<\/td>\n | E.2.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 202<\/td>\n | E.2.6 CRUDN behavior E.3 OCF Collection E.3.1 Introduction E.3.2 Example URI E.3.3 Resource Type E.3.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 215<\/td>\n | E.3.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 218<\/td>\n | E.3.6 CRUDN behavior E.4 Platform Configuration E.4.1 Introduction E.4.2 Example URI E.4.3 Resource Type E.4.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 222<\/td>\n | E.4.5 Property Definition E.4.6 CRUDN behavior E.5 Device Configuration E.5.1 Introduction E.5.2 Example URI E.5.3 Resource Type E.5.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 228<\/td>\n | E.5.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 229<\/td>\n | E.5.6 CRUDN behavior E.6 Device E.6.1 Introduction E.6.2 Wellknown URI E.6.3 Resource Type E.6.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 232<\/td>\n | E.6.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 233<\/td>\n | E.6.6 CRUDN behavior E.7 Maintenance E.7.1 Introduction E.7.2 Wellknown URI <\/td>\n<\/tr>\n | ||||||
| 234<\/td>\n | E.7.3 Resource Type E.7.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 236<\/td>\n | E.7.5 Property Definition E.7.6 CRUDN behavior E.8 Platform E.8.1 Introduction E.8.2 Wellknown URI E.8.3 Resource Type <\/td>\n<\/tr>\n | ||||||
| 237<\/td>\n | E.8.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 240<\/td>\n | E.8.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 241<\/td>\n | E.8.6 CRUDN behavior E.9 Ping E.9.1 Introduction E.9.2 Wellknown URI E.9.3 Resource Type E.9.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 243<\/td>\n | E.9.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 244<\/td>\n | E.9.6 CRUDN behavior E.10 Resource directory resource E.10.1 Introduction E.10.2 Wellknown URI E.10.3 Resource Type E.10.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 253<\/td>\n | E.10.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 254<\/td>\n | E.10.6 CRUDN behavior E.11 Discoverable Resources E.11.1 Introduction E.11.2 Wellknown URI E.11.3 Resource Type E.11.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 261<\/td>\n | E.11.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 263<\/td>\n | E.11.6 CRUDN behavior E.12 Scenes E.12.1 Introduction E.12.2 Example URI E.12.3 Resource Type E.12.4 Swagger2.0 Definition <\/td>\n<\/tr>\n | ||||||
| 277<\/td>\n | E.12.5 Property Definition <\/td>\n<\/tr>\n | ||||||
| 280<\/td>\n | E.12.6 CRUDN behavior <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Information technology. Open Connectivity Foundation (OCF) Specification – Core specification<\/b><\/p>\n |