Profiles
++ The WoT Profile Specification defines a WoT Core Profile, + which enables out of the box interoperability among things + and devices. Out of the box interoperability implies, + that devices can be integrated into various application + scenarios without deep level adaptations. + Typically only minor configuration operations are necessary + (such as entering a network key, or IP address) to use the + device in a certain scenario. + These actions can be done by anyone without specific training. +
++ In the core profile we define a mapping to + HTTP(S). It is envisioned, that future versions of this document + contain additional mapping to Web Sockets and other protocols. +
-Core Profile
-TODO: Create text for Core Profile <MichaelL> -
+Profiling Methodology
++ A profile is a set of constraints and rules, which + provide additional semantic guarantees that are applied + to the WoT Thing Description specification. These constraints define a + subset of valid WoT Thing Descriptions by defining + additional rules on various aspects of the WoT Thing + Description specification. +
+ +| Constraints on | +Rationale | +Examples | +
|---|---|---|
| vocabulary of Thing Description classes | +guaranteed set of metadata fields | +Make specific vocabulary terms mandatory, + remove others | +
| class relationships | +unambiguous structure | +limited cardinality, e.g. only one form per + operation per interaction affordance. | +
| values of vocabulary terms | +simplified processing | +Limit the length of characters per string. + Always use arrays, where the spec permits a + string or an array of strings. | +
| data schemas | +simplified processing | +No arbitrary nested objects or arrays of + arrays. | +
| security | +reduced implementation effort | +Only a restricted set of security + mechanisms. | +
| protocol binding | +guaranteed protocol semantics | +limited protocol(s) and protocol features, + Example: predefined mapping of http verbs (GET/PUT) to + operation verbs, similar constraints for other protocols. | +
These constraints and rules fall into two categories:
+-
+
- constraints for the data model. +
- constraints for the protocol binding. +
These two categories are orthogonal to each other, + i.e. a data model that conforms to a profile can be + mapped to different protocols. The protocol binding for + each protocol may contain additional (protocol-specific) + constraints.
+ +A profile is not exclusive, i.e. a thing may conform + to multiple profiles. Profiles can build on top of each + other or overlap, extended profiles can be built on top + of the core profile.
+ +
+