Merge branch 'v1.0-dev' into publish-jrt

APIs/ConfigurationAPI.raml

@@ -27,7 +27,7 @@ documentation:
 /rolePaths:
   displayName: 'Role Paths'
   get:
-    description: 'Returns the Role Paths of the Device Model'
+    description: 'Returns the Role Paths of the Device Model. Each rolePath MUST be created by appending NcObject roles starting with the root block and using "." as the delimiter'
     responses:
       200:
         body:
@@ -63,7 +63,7 @@ documentation:
     /properties:
       displayName: 'Properties'
       get:
-        description: 'Get Properties of the object'
+        description: 'Get Properties of the object. This response MUST include all object properties including all the inherited properties'
         responses:
           200:
             body:
@@ -112,7 +112,7 @@ documentation:
         /descriptor:
           displayName: 'Datatype Descriptor of property'
           get:
-            description: 'Get MS-05 Datatype Descriptor of property'
+            description: 'Get MS-05 Datatype Descriptor of property. This descriptor MUST include all inherited elements'
             responses:
               200:
                 body:
@@ -125,7 +125,7 @@ documentation:
     /methods:
       displayName: 'Methods'
       get:
-        description: 'Get Methods of this object.'
+        description: 'Get Methods of this object. This response MUST include all object methods including all the inherited methods'
         responses:
           200:
             body:
@@ -158,7 +158,7 @@ documentation:
     /descriptor:
       displayName: 'Class Descriptor'
       get:
-        description: 'Get MS-05 Class Descriptor of this object.'
+        description: 'Get MS-05 Class Descriptor of this object. This descriptor MUST include all inherited elements'
         responses:
           200:
             body:

APIs/schemas/method-patch-request.json

@@ -4,32 +4,12 @@
   "description": "PATCH request body for invoking a method",
   "title": "Invoke method body",
   "required": [
-    "methodId"
+    "arguments"
   ],
   "properties": {
-    "methodId": {
-      "type": "object",
-      "description": "ID structure for the target method",
-      "required": [
-        "level",
-        "index"
-      ],
-      "properties": {
-        "level": {
-          "type": "integer",
-          "description": "Level component of the method ID",
-          "minimum": 1
-        },
-        "index": {
-          "type": "integer",
-          "description": "Index component of the method ID",
-          "minimum": 1
-        }
-      }
-    },
     "arguments": {
       "type": "object",
-      "description": "Method arguments. Arguments are specified as nested properties inside this object and their types are dictated by the specific MS-05-02 model for the method targeted. Arguments only need to be included for methods which have arguments and MUST be omitted if the method does not require any arguments."
+      "description": "Method arguments. Arguments are specified as nested properties inside this object and their types are dictated by the specific MS-05-02 model for the method targeted. For methods which do not have arguments defined the object MUST be an empty object."
     }
   }
 }

docs/Transport and message encoding.md

@@ -1,5 +1,5 @@
 # Transport and message encoding
 
-Implementations MUST use `HTTP` as the communication transport.
+Implementations MUST use `HTTP` or `HTTPS` as the communication transport.
 
 Implementations MUST use `JSON` as the message encoding data format.