From d1d410ca1ec203c7318162d1f3e5c054f0b206b2 Mon Sep 17 00:00:00 2001 From: Fady Salama Date: Thu, 10 Jun 2021 18:17:20 +0200 Subject: [PATCH] new manual assertions for v1.1 --- packages/assertions/manual.csv | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/packages/assertions/manual.csv b/packages/assertions/manual.csv index 8348f2590..4102d83b9 100644 --- a/packages/assertions/manual.csv +++ b/packages/assertions/manual.csv @@ -9,6 +9,10 @@ "iana-security-execution","null","not testable with Assertion Tester","Since WoT Thing Description is intended to be a pure data exchange format for Thing metadata, the serialization SHOULD NOT be passed through a code execution mechanism such as JavaScript's eval() function to be parsed." "iana-security-expansion","null","not testable with Assertion Tester","Consumers SHOULD treat any TD metadata with due skepticism." "iana-security-remote","null","not testable with Assertion Tester","While implementations on resource-constrained devices are expected to perform raw JSON processing (as opposed to JSON-LD processing), implementations in general SHOULD statically cache vetted versions of their supported context extensions and not to follow links to remote contexts." +"processors-preserve-array-order","null","not testable with Assertion Tester","In order to support canonicalization, implementations of TD Processors MUST preserve the order of elements in all arrays." +"processors-preserve-prefixes-1","null","not testable with Assertion Tester","In order to support canonicalization, implementations of TD Processors MUST preserve the prefixes used for extension vocabularies." +"processors-preserve-prefixes-2","null","not testable with Assertion Tester","In order to support canonicalization, implementations of TD Processors MUST NOT modify input URLs." +sec-body-name-json-pointer-creatable,"null","not testable with Assertion Tester","When an element of a data schema indicated by a JSON pointer indicated in a body locator does not already exist in the indicated schema, it MUST be possible to insert the indicated element at the location indicated by the pointer. ", "server-data-schema","null","not testable with Assertion Tester","A WoT Thing Description MUST accurately describe the data returned and accepted by each interaction." "server-data-schema-extras","null","not testable with Assertion Tester","A Thing MAY return additional data from an interaction even when such data is not described in the data schemas given in its WoT Thing Description." "server-uri-template","null","not testable with Assertion Tester","URI Templates, base URIs, and href members in a WoT Thing Description MUST accurately describe the WoT Interface of the Thing." @@ -37,6 +41,7 @@ "td-default-qop","null","not testable with Assertion Tester","The value associated with member qop if not given MUST be assumed to have the default value auth." "td-default-readOnly","null","not testable with Assertion Tester","The value associated with member readOnly if not given MUST be assumed to have the default value false." "td-default-safe","null","not testable with Assertion Tester","The value associated with member safe if not given MUST be assumed to have the default value false." +"td-default-success","null","not testable with Assertion Tester","The value associated with member ""success"" if not given MUST be assumed to have the default value ""false""." "td-default-writeOnly","null","not testable with Assertion Tester","The value associated with member writeOnly if not given MUST be assumed to have the default value false." "td-expectedResponse-contentType","null","not testable with Assertion Tester","If the content type of the expected response differs from the content type of the form, the Form instance MUST include a name-value pair with the name response." "td-expectedResponse-default-contentType","null","not testable with Assertion Tester","If no response name-value pair is provided, it MUST be assumed that the content type of the response is equal to the content type assigned to the Form instance." @@ -45,11 +50,15 @@ "td-json-open","null","not testable with Assertion Tester","TDs MUST be serialized according to the requirements defined in Section 8.1 of RFC8259 for open ecosystems." "td-json-open_accept-byte-order","null","not testable with Assertion Tester","TD Processors MAY ignore the presence of a byte order mark rather than treating it as an error." "td-json-open_no-byte-order","null","not testable with Assertion Tester","Implementations MUST NOT add a byte order mark (U+FEFF) to the beginning of a TD document." +"td-model-tmRef-2","null","not testable with Assertion Tester","Every time tm:ref is used, the referenced pre-definition and its dependencies (e.g., by context extension) MUST be assumed at this point." +"td-model-tmRef-overwrite","null","not testable with Assertion Tester","If it is intended to override an existing JSON name-value pair definition from tm:ref, the same JSON name MUST be used at the same level of the tm:ref declearation that provides a new value." "td-ns-multilanguage-content-negotiation","null","not testable with Assertion Tester","In cases where the default language has been negotiated, an @language member MUST be present to indicate the result of the negotiation and the corresponding default language of the returned content." "td-ns-multilanguage-content-negotiation-no-multi","null","not testable with Assertion Tester","When the default language has been negotiated successfully, TD documents SHOULD include the appropriate matching values for the members title and description in preference to MultiLanguage objects in titles and descriptions members. " "td-ns-multilanguage-content-negotiation-optional","null","not testable with Assertion Tester","Note however that Things MAY choose to not support such dynamically-generated TDs nor to support language negotiation (e.g., because of resource constraints)." "td-processor-serialization","null","not testable with Assertion Tester","A TD Processor MUST be able to serialize Thing Descriptions into the JSON format and/or deserialize Thing Descriptions from that format, according to the rules noted in and." "td-security-binding","null","not testable with Assertion Tester","If a Thing requires a specific access mechanism for an interaction, that mechanism MUST be specified in the security configuration of the Thing Description." +"td-security-in-query-over-uri","null","not testable with Assertion Tester", "The value uri SHOULD be specified for the name in in a security scheme only if query is not applicable." "td-security-no-extras","null","not testable with Assertion Tester","If a Thing does not require a specific access mechanism for an interaction, that mechanism MUST NOT be specified in the security configuration of the Thing Description." +"td-security-no-secrets","null","not testable with Assertion Tester","For all security schemes, any private keys, passwords, or other sensitive information directly providing access should be shared and stored out-of-band and MUST NOT be stored in the TD." "td-vocabulary-defaults","null","not testable with Assertion Tester","When assignments in a TD are missing, a TD Processor MUST follow the Default Value assignments expressed in the table of." -"well-known-operation-types-only","null","not testable with Assertion Tester","operations types SHOULD NOT be arbitrarily set by servients. \ No newline at end of file +"well-known-operation-types-only","null","not testable with Assertion Tester","operations types SHOULD NOT be arbitrarily set by servients." \ No newline at end of file