Extra Assertions

These are a collection of additional assertions used for testing, but which are (currently) not included in the specification. These are candidates for being put in the specification and are given here only to stage them in order to facilitate timely generation of the implementation report. In the final report this list should probably be empty.

• The vocabulary term idempotent MUST be serialized as a JSON name within an Action object.
• The vocabulary term forms MUST be serialized as a JSON name within an Action object.
• The vocabulary term descriptions MUST be serialized as a JSON name within an Action object.
• The vocabulary term description MUST be serialized as a JSON name within an Action object.
• The type of the member links MUST be a JSON array.
• The type of the member forms MUST be a JSON array.
• Actions collected in the JSON-object based actions member MUST have unique JSON names.
• Actions offered by a Thing MUST be collected in the JSON-object based actions member.
• The type of the members output MUST be serialized as a JSON object.
• The type of the members input MUST be serialized as a JSON object.
• The vocabulary term uriVariables MUST be serialized as a JSON name within an Action object.
• The vocabulary term @type MUST be serialized as a JSON name within an Action object.
• The vocabulary term input MUST be serialized as a JSON name within an Action object.
• The vocabulary term titles MUST be serialized as a JSON name within an Action object.
• The vocabulary term title MUST be serialized as a JSON name within an Action object.
• The vocabulary term safe MUST be serialized as a JSON name within an Action object.
• The vocabulary term output MUST be serialized as a JSON name within an Action object.
• The value of the member enum MUST be serialized as a JSON array with a DataSchema object.
• The value of the member oneOf MUST be serialized as a JSON array with a DataSchema object.
• The value of the member required MUST be serialized as a JSON array with a DataSchema object.
• The @type vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The const vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The contentEncoding vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The contentMediaType vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The maxLength vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The minLength vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The multipleOf vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The multipleOf vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The description vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The descriptions vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The enum vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The exclusiveMaximum vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The exclusiveMaximum vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The exclusiveMinimum vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The exclusiveMinimum vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The format vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The items vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The maxItems vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The maximum vocabulary term as defined in the class DataSchema for numbers MUST be serialized as a JSON name.
• The maximum vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The minItems vocabulary term as defined in the class DataSchema MUST be serialized as a JSON name.
• The minimum vocabulary term as defined in the class DataSchema for numbers MUST be serialized as a JSON name.
• The minimum vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The oneOf vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The pattern vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The properties vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The readOnly vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The required vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The title vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The titles vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The type vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The unit vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The writeOnly vocabulary term as defined in the class DataSchema for integers MUST be serialized as a JSON name.
• The vocabulary term @type MUST be serialized as a JSON name within an Event object.
• The vocabulary term cancellation MUST be serialized as a JSON name within an Event object.
• The vocabulary term data MUST be serialized as a JSON name within an Event object.
• The vocabulary term dataResponse MUST be serialized as a JSON name within an Event object.
• The vocabulary term description MUST be serialized as a JSON name within an Event object.
• The vocabulary term descriptions MUST be serialized as a JSON name within an Event object.
• The vocabulary term forms MUST be serialized as a JSON name within an Event object.
• The vocabulary term subscription MUST be serialized as a JSON name within an Event object.
• The vocabulary term title MUST be serialized as a JSON name within an Event object.
• The vocabulary term titles MUST be serialized as a JSON name within an Event object.
• The vocabulary term uriVariables MUST be serialized as a JSON name within an Event object.
• The type of the members cancellation MUST be serialized as a JSON object.
• The type of the members data MUST be serialized as a JSON object.
• The type of the members dataResponse MUST be serialized as a JSON object.
• The type of the members subscription MUST be serialized as a JSON object.
• Events offered by a Thing MUST be collected in the JSON-object based events member.
• Events collected in the JSON-object based events member MUST have unique JSON names.
• Whenever the vocabulary terms descriptions can be used it MUST be serialized as JSON object. The member names of the JSON Object MUST be the language tags as defined in [[BCP47]] (e.g., "en", "de", "ja", "zh-Hans", "zh-Hant"). The value of each member MUST be serialized as JSON string.
• Whenever the vocabulary terms titles can be used it MUST be serialized as JSON object. The member names of the JSON Object MUST be the language tags as defined in [[BCP47]] (e.g., "en", "de", "ja", "zh-Hans", "zh-Hant"). The value of each member MUST be serialized as JSON string.
• The type of the members actions MUST be serialized as a JSON object.
• The type of the members events MUST be serialized as a JSON object.
• The type of the members properties MUST be serialized as a JSON object.
• The type of the members securityDefinitions MUST be serialized as a JSON object.
• The type of the members version MUST be serialized as a JSON object.
• The type of the members descriptions MUST be serialized as a JSON object.
• The type of the members schemaDefinitions MUST be serialized as a JSON object.
• The type of the members uriVariables MUST be serialized as a JSON object.
• Type: MUST be string or Array of string (invokeaction).
• Type: MUST be string or Array of string (cancelaction).
• Type: MUST be string or Array of string (queryaction).
• Type: MUST be string or Array of string (observeproperty).
• Type: MUST be string or Array of string (readproperty).
• Type: MUST be string or Array of string (subscribeevent).
• Type: MUST be string or Array of string (unobserveproperty).
• Type: MUST be string or Array of string (unsubscribeevent).
• Type: MUST be string or Array of string (writeproperty).
• Type: MUST be string or Array of string (readallproperties).
• Type: MUST be string or Array of string (writeallproperties).
• Type: MUST be string or Array of string (readmultipleproperties).
• Type: MUST be string or Array of string (writemultipleproperties).
• Type: MUST be string or Array of string (observeallproperties).
• Type: MUST be string or Array of string (unobserveallproperties).
• Type: MUST be string or Array of string (queryallactions).
• Type: MUST be string or Array of string (subscribeallevents).
• Type: MUST be string or Array of string (unsubscribeallevents).
• Properties offered by a Thing MUST be collected in the JSON-object based properties member.
• Properties collected in the JSON-object based properties member MUST have unique JSON names.
• The vocabulary term @type MUST be serialized as a JSON name within a Property object.
• The vocabulary term const MUST be serialized as a JSON name within a Property object.
• The vocabulary term contentEncoding MUST be serialized as a JSON name within a Property object.
• The vocabulary term contentMediaType MUST be serialized as a JSON name within a Property object.
• The vocabulary term description MUST be serialized as a JSON name within a Property object.
• The vocabulary term descriptions MUST be serialized as a JSON name within a Property object.
• The vocabulary term enum MUST be serialized as a JSON name within a Property object.
• The vocabulary term exclusiveMaximum MUST be serialized as a JSON name within a Property object.
• The vocabulary term exclusiveMinimum MUST be serialized as a JSON name within a Property object.
• The vocabulary term forms MUST be serialized as a JSON name within a Property object.
• The vocabulary term format MUST be serialized as a JSON name within a Property object.
• The vocabulary term items MUST be serialized as a JSON name within a Property object.
• The vocabulary term maxItems MUST be serialized as a JSON name within a Property object.
• The vocabulary term maximum MUST be serialized as a JSON name within a Property object.
• The vocabulary term minItems MUST be serialized as a JSON name within a Property object.
• The vocabulary term minimum MUST be serialized as a JSON name within a Property object.
• The vocabulary term maxLength MUST be serialized as a JSON name within a Property object.
• The vocabulary term minLength MUST be serialized as a JSON name within a Property object.
• The vocabulary term multipleOf MUST be serialized as a JSON name within a Property object.
• The vocabulary term observable MUST be serialized as a JSON name within a Property object.
• The vocabulary term oneOf MUST be serialized as a JSON name within a Property object.
• The vocabulary term properties MUST be serialized as a JSON name within a Property object.
• The vocabulary term readOnly MUST be serialized as a JSON name within a Property object.
• The vocabulary term required MUST be serialized as a JSON name within a Property object.
• The vocabulary term title MUST be serialized as a JSON name within a Property object.
• The vocabulary term titles MUST be serialized as a JSON name within a Property object.
• The vocabulary term type MUST be serialized as a JSON name within a Property object.
• The vocabulary term unit MUST be serialized as a JSON name within a Property object.
• The vocabulary term uriVariables MUST be serialized as a JSON name within a Property object.
• The vocabulary term writeOnly MUST be serialized as a JSON name within a Property object.
• Other algorithms for bearer tokens MAY be specified in vocabulary extensions.
• Other formats for bearer tokens MAY be specified in vocabulary extensions.
• If description and descriptions are defined at the same time at the JSON level, description MAY be seen as default text.
• If title and titles are defined at the same time at the JSON level, title MAY be seen as default text.
• scheme: Identification of security mechanism being configured MAY be set to "apikey".
• scheme: Identification of security mechanism being configured MAY be set to "auto".
• scheme: Identification of security mechanism being configured MAY be set to "basic".
• scheme: Identification of security mechanism being configured MAY be set to "bearer".
• scheme: Identification of security mechanism being configured MAY be set to "digest".
• scheme: Identification of security mechanism being configured MAY be set to "nosec".
• scheme: Identification of security mechanism being configured MAY be set to "oauth2".
• scheme: Identification of security mechanism being configured MAY be set to "psk".
• type: Assignment of JSON-based data types MUST be compatible with JSON Schema (array).
• type: Assignment of JSON-based data types MUST be compatible with JSON Schema (boolean).
• type: Assignment of JSON-based data types MUST be compatible with JSON Schema (integer).
• type: Assignment of JSON-based data types MUST be compatible with JSON Schema (null).
• type: Assignment of JSON-based data types MUST be compatible with JSON Schema (number).
• type: Assignment of JSON-based data types MUST be compatible with JSON Schema (object).
• type: Assignment of JSON-based data types MUST be compatible with JSON Schema (string).