Skip to content

Commit

Permalink
chore(testing): sync assertions.csv with the current assertions in th…
Browse files Browse the repository at this point in the history
…e spec
  • Loading branch information
egekorkan committed Oct 4, 2022
1 parent d23ec25 commit a3af760
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions testing/assertions.csv
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
"ID","Status","Assertion"
"bindings-requirements-scheme","null","Every form in a WoT Thing Description MUST follow the requirements of the Protocol Binding Template indicated by the URI scheme [[!RFC3986]] of its href member as indicated by the Binding Templates specification at Creating a New Protocol Binding."
"bindings-server-accept","null","Every form in a WoT Thing Description MUST accurately describe requests (including request headers, if present) accepted by the Thing in an interaction."
"client-data-schema","null","A Thing acting as a Consumer when interacting with another target Thingdescribed in a WoT Thing Description MUST generate data organized according to the data schemas given in the correspondinginteractions."
"client-data-schema-accept-extras","null","A Thing acting as a Consumer when interacting with another Thing MUST accept withouterror any additional data not described in the data schemas given in the Thing Description of the target Thing."
"client-data-schema-no-extras","null","A Thing acting as a Consumer when interacting with another Thing MUST NOT generate datanot described in the data schemas given in the Thing Description of that Thing."
"client-uri-template","null","A Thing acting as a Consumer when interacting with another Thing MUST generate URIsaccording to the URI Templates, base URIs, and form href parametersgiven in the Thing Description of the target Thing."
"client-data-schema","null","A Consumer when interacting with another target Thingdescribed in a WoT Thing Description MUST generate data organized according to the data schemas given in the correspondinginteractions."
"client-data-schema-accept-extras","null","A Consumer when interacting with another Thing MUST accept withouterror any additional data not described in the data schemas given in the Thing Description of the target Thing."
"client-data-schema-no-extras","null","A Consumer when interacting with another Thing MUST NOT generate datanot described in the data schemas given in the Thing Description of that Thing."
"client-uri-template","null","A Consumer when interacting with another Thing MUST generate URIsaccording to the URI Templates, base URIs, and form href parametersgiven in the Thing Description of the target Thing."
"privacy-auth-users-only","null","Only authorized users SHOULD be provided access to the Thing Description for a Thing."
"privacy-centralized-ids","null","TD identifiers SHOULD NOT be generated using a centralized authority."
"privacy-distributed-ids","null","TD identifiers SHOULD be generated using a distributed mechanism such as UUIDs that provides a high probability of uniqueness."
Expand Down Expand Up @@ -440,7 +440,7 @@
"tm-ref-recursive-extensions","null","Recursive extensions leading to an infinite loop MUST NOT be defined."
"tm-rel-type-maximum","null","The links array MUST use the entry with ""rel"" : ""type"" a maximum of once."
"tm-td-generation-inconsistencies","null","A Thing Model MUST be defined in such a way that there are no inconsistencies that would result in a Thing Description not being able to meet the requirements as described in Section and ."
"tm-tmOptional","null","If interaction models are not manditory to be implemented in a Thing Description instance, Thing Model definitions MUST use the JSON member name tm:optional."
"tm-tmOptional","null","If interaction models are not mandatory to be implemented in a Thing Description instance, Thing Model definitions MUST use the JSON member name tm:optional."
"tm-tmOptional-JSONPointer","null","The value of tm:optional MUST provide JSON Pointer [[RFC6901]] references to the required interaction model definitions."
"tm-tmOptional-array","null","tm:optional MUST be a JSON array at the top level."
"tm-tmOptional-resolver","null","The JSON Pointers of tm:optional MUST resolve to an entire interaction affordance Map definition."
Expand Down

0 comments on commit a3af760

Please sign in to comment.