OCF: update device and platform properties according to OIC spec 1.1.0

Signed-off-by: Zoltan Kis <[email protected]>

Author: zolkis

api/ocf/README.md

@@ -64,7 +64,6 @@ The `options` optional parameter is an object that may contain the following pro
 
 The method runs the following steps:
 - Return a [`Promise`](../README.md/#promise) object `promise` and continue [in parallel](https://html.spec.whatwg.org/#in-parallel).
-- Let `ocf` denote the API object (equal to the `this` property of `start()`).
 - If the `mode` argument is `undefined`, let `mode` be `"client-server"`.
 - Otherwise if the `mode` argument is not `"client"`, or `"server"`, or `"client-server"`, reject `promise` with a `TypeError` and abort these steps.
 - If the `mode` parameter is `"client"`, then run the following sub-steps:
@@ -93,31 +92,39 @@ Exposes information about the OCF device that runs the current OCF stack instanc
 |Property           |Type     |Optional |Default value |Represents |
 | ---               | ---     | ---     | ---          | ---       |
 | `uuid`            | string  | no      | `undefined` | UUID of the device |
-| `url`             | string  | yes     | `undefined` | host:port  |
 | `name`            | string  | yes     | `undefined` | Name of the device |
 | `types`           | array of strings  | no  | `[]` | List of supported OCF device types |
 | `dataModels`      | array of strings  | no  | `[]` | List of supported OCF data models |
 | `coreSpecVersion` | string  | no  | `undefined` | OCF Core Specification version |
 
-The `types` property is a list of the OCF Device types that are supported. It comforms to the same syntax constraints as [resource](./client.md/#resource) types. OCF mandates that every device supports at least the properties defined in the `"oic.wk.d"` resource type, that represents a resource for a "basic device". Other specifications, such as the OCF Smart Home Device Specification can define more device types, for instance `"oic.d.fan"`, `"oic.d.thermostat"`, `"oic.d.light"`, `"oic.d.airconditioner"`, etc. The properties exposed by these device types are defined in [oneiota.org](http://www.oneiota.org). The values in `types` may be used in [device discovery](./client.md/#finddevices) filters. For a client-only device `types` is an empty array.
+The `uuid` property is generated by the underlying OCF stack during the on-boarding process. Applications may provide this property, but it may be changed by the implementation after the device is started.
 
-The `dataModels` property is in the following format: `vertical.major.minor` where `major` and `minor` are numbers and `vertical` is a string such as `"Smart Home"`.
+The `name` property represents the device name as provided by the application. Users can also set a free-form device name using the [configure()](./client.md/#configure) method that updates the `oic.wk.con` resource, hence does not alter `name`.
+
+The `types` property is a list of the OCF Device types that are supported. It comforms to the same syntax constraints as [resource](./client.md/#resource) types. OCF mandates that every device supports at least the properties defined in the `"oic.wk.d"` resource type, that represents a resource for a "basic device". Other specifications, such as the OCF Smart Home Device Specification can define more device types, for instance `"oic.d.fan"`, `"oic.d.thermostat"`, `"oic.d.light"`, `"oic.d.airconditioner"`, etc. The properties exposed by these device types are defined in [oneiota.org](http://www.oneiota.org). The values in `types` may be used in [device discovery](./client.md/#finddevices) filters. For a client-only device `types` is an empty array. When a server device registers a new resource with a new resource type, this property SHOULD be updated by the implementation.
+
+Elements of the `dataModels` property are in the following format: `vertical.major.minor.version` where `major`, `minor` and `version` are numbers and `vertical` is a string. For instance, in the OIC 1.1.0 Core Specification the supported data model version is `"res.1.1.0"`.
+
+The `coreSpecVersion` is `"1.1.0"` in this version of the specification.
 
 <a name="ocfplatform"></a>
 ### The `OcfPlatform` object
 Exposes information about the OCF platform that hosts the current device.
 
-|Property            |Type     |Optional |Default value |Represents |
-| ---                | ---     | ---     | ---          | ---       |
-| `id`               | string  | no  | `undefined` | Platform identifier |
-| `osVersion`        | string  | yes  | `undefined` | OS version  |
-| `model`            | string  | yes  | `undefined` | Model of the hardware |
-| `manufacturerName` | string  | no  | `undefined` | Manufacturer name |
-| `manufacturerURL`  | string  | no  | `undefined` | Manufacturer web page |
-| `manufacturerDate` | Date    | no  | `undefined` | Manufacturing date |
-| `platformVersion`  | string  | no  | `undefined` | Platform version |
-| `firmwareVersion`  | string  | no  | `undefined` | Firmware version |
-| `supportURL`       | string  | no  | `undefined` | Product support web page |
+|Property            |Type     |Optional |Default value |Represents            |
+| ---                | ---     | ---     | ---          | ---                  |
+| `id`               | string  | no  | `undefined` | Platform identifier       |
+| `model`            | string  | yes | `undefined` | Model of the hardware     |
+| `manufacturerName` | string  | no  | `undefined` | Manufacturer name         |
+| `manufacturerLink` | string  | yes | `undefined` | Manufacturer URI          |
+| `manufactureDate`  | Date    | yes | `undefined` | Manufacturing date        |
+| `vendorId`         | string  | yes | `undefined` | Vendor ID                 |
+| `osVersion`        | string  | yes | `undefined` | OS version                |
+| `platformVersion`  | string  | yes | `undefined` | Platform version          |
+| `firmwareVersion`  | string  | yes | `undefined` | Firmware version          |
+| `hardwareVersion`  | string  | yes | `undefined` | Firmware version          |
+| `supportURL`       | string  | yes | `undefined` | Product support web page  |
+| `datetime`         | Date    | yes | `undefined` | System time of the device |
 
 <a name="ocferror"></a>
 ### Error handling

api/ocf/examples.md

@@ -46,7 +46,7 @@ require('ocf').start("client").then(function(client) {
 var deviceInit = {
   name: "led",
   types: [ "oic.wk.d", "oic.wk.p", "oic.wk.res", "oic.d.light" ],
-  dataModels: [“res.1.1.0”],
+  dataModels: ["res.1.1.0"],
   coreSpecVersion: "OIC 1.1"
 };
 

api/ocf/server.md

@@ -52,6 +52,7 @@ The method runs the following steps:
 - Send a request to register the given `resource`, and wait for the answer.
 - If there is an error during the request, reject `promise` with that error.
 - When the answer is received, update `resource` to be a [`ServerResource`](#serverresource) object.
+- Update the [device's](./README.md/#ocfdevice) `types` property, if `resourceType` of `resource` is not in `types`.
 - Resolve `promise` with `resource`.
 
 <a name="oncreate"></a>