Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tm optional fix #339

Merged
merged 5 commits into from
Aug 19, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 17 additions & 17 deletions packages/assertions/assertions-csv/assertions.csv

Large diffs are not rendered by default.

8 changes: 4 additions & 4 deletions packages/assertions/assertions-csv/implemented.csv
Original file line number Diff line number Diff line change
Expand Up @@ -363,8 +363,8 @@
"tm-placeholder-value","null","",
"tm-protocol-security-restriction","null","",
"tm-td-generation-inconsistencies","null","",
"tm-tmOptional","null","",
"tm-tmOptional-JSONPointer","null","",
"tm-tmOptional-array","null","",
"tm-tmRef-usecase","null","",
"tm-tmRef1","null","",
"tm-tmRequired","null","",
"tm-tmRequired-JSONPointer","null","",
"tm-tmRequired-array","null","",
"tm-tmRef1","null","",
Original file line number Diff line number Diff line change
Expand Up @@ -400,6 +400,7 @@
"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."
"ID","Status","Comment","Assertion"
"tm-compose-instanceName","not-impl",,
"tm-compose-submodel","not-impl",,
"tm-context-requirement","pass",,
Expand All @@ -411,8 +412,8 @@
"tm-placeholder-value","pass",,
"tm-protocol-security-restriction","pass",,
"tm-td-generation-inconsistencies","pass",,
"tm-tmOptional","not-impl","data must have required property 'tm:optional'",
"tm-tmOptional-JSONPointer","not-impl","data must have required property 'tm:optional'",
"tm-tmOptional-array","not-impl","data must have required property 'tm:optional'",
"tm-tmRef-usecase","not-impl",,
"tm-tmRef1","not-impl",,
"tm-tmRequired","not-impl","data must have required property 'tm:required'",
"tm-tmRequired-JSONPointer","not-impl","data must have required property 'tm:required'",
"tm-tmRequired-array","not-impl","data must have required property 'tm:required'",
15 changes: 7 additions & 8 deletions packages/assertions/assertions-csv/manual.csv
Original file line number Diff line number Diff line change
Expand Up @@ -51,40 +51,39 @@
"privacy-centralized-ids","null","TD identifiers SHOULD NOT be generated using a centralized authority.",""
"privacy-essential-metadata-only","null","Only the amount of information needed for the level of authorization and the use case SHOULD be provided in a TD.",""
"privacy-immutable-id-as-property","null","Ideally, any required immutable identifiers SHOULD only be made available via affordances, such as a property, whose value can only be obtained after appropriate authentication and authorization, and managed separately from the TD identifier.",""
"privacy-mutable-id-ownership","null","TD identifiers SHOULD be updated upon major changes in configuration or reinitialization.",""
"privacy-mutable-identifiers","null","All identifiers used in a TD SHOULD be mutable, and in particular there should be a mechanism to update the id of a Thing when necessary.",""
"privacy-td-pii","null","A Thing Description associated with a personal device SHOULD be treated as if it contained personally identifiable information, even if this information is not explicit.",""
"privacy-temp-id-metadata","null","Any temporary ID generated to manage TDs, for example an ID for a database or directory service, SHOULD NOT contain metadata describing the Thing or from the TD itself.",""
"sec-body-name-json-pointer-type","null",".",""
"sec-inj-no-intl-markup","null","HTML markup SHOULD NOT be used for internationalization purposes in TD strings.",""
"sec-inj-sanitize","null","Strings sourced from TDs MUST either be sanitized using a carefully vetted HTML sanitizer that disables any markup or should be inserted into an HTML template using DOM node manipulation APIs that will escape any markup.",""
"security-context-secure-fetch","null","If it is necessary to fetch a context definition file, an implementation SHOULD first attempt to use HTTP over TLS even when only an HTTP URL is given.",""
"security-jsonld-expansion","null","Consumers SHOULD set and enforce limits on memory usage to prevent buffer overflow and resource exhaustion during JSON-LD processing.",""
"security-mutual-auth-td","null","Thing Descriptions SHOULD be obtained only through mutually authenticated secure channels.",""
"security-no-execution","null","A WoT Thing Description JSON-LD serialization MUST NOT be passed through a code execution mechanism such as JavaScript's eval() function to be parsed.",""
"security-oauth-limits","null","To limit the scope and duration of access to Things, tokens SHOULD be used to manage access.",""
"security-remote-context","null","Constrained implementations SHOULD NOT follow links to remote contexts.",""
"security-server-auth-td","null","In cases where the Consumer is associated with a person, e.g. browsers, TDs MAY be obtained through a channel where only the TD provider is authenticated.",""
"security-static-context","null","Constrained implementations SHOULD use statically managed and vetted versions of their supported context extensions.",""
"security-update-contexts","null","Supported context extensions on constrained implementations MAY be managed through secure software update mechanisms.",""
"security-static-context","null","Constrained implementations SHOULD use vetted versions of their supported context extensions managed statically or as part of a secure update process.",""
"td-context-ns-td10-namespacev10","null","TD 1.1 consumers MUST accept TDs satisfying the W3C WoT Thing Description 1.0 [[wot-thing-description]] specification.",""
"td-default-AdditionalResponseContentType","null","AdditionalExpectedResponse contentType value of the contentType of the Form element it belongs to.",""
"td-default-observable","null","PropertyAffordance observable false",""
"td-processor-bidi-isolation","null","TD Processors SHOULD take care to use bidi isolation when presenting strings to users, particularly when embedding in surrounding text (e.g., for Web user interface)",""
"td-producer-mixed-direction","null","TD producers SHOULD attempt to provide mixed direction strings in a way that can be displayed successfully by a naive user agent.",""
"td-security-extension","null","Additional security schemes MUST be Subclasses of the Class SecurityScheme.",""
"td-text-direction-first-strong","null","When metadata such as @direction is not present, TD Consumers SHOULD use [=first-strong detection=] as a fallback.",""
"td-text-direction-language-tag","null","For the MultiLanguage Map, TD Consumers MAY infer the [=base direction=] from the language tag of the individual strings.",""
"thing-model-td-generation-processor-extends","null","If used",""
"thing-model-td-generation-processor-forms","null","Missing communication and/or security metadata details MUST be completed in the Thing Description instance based on Section and/or .",""
"thing-model-td-generation-processor-imports","null","Copy all definitions from the input Thing Model to the resulting Partial TD instance. If used, the extension and imports feature MUST be resolved and represented in the Partial TD instance according to .",""
"thing-model-td-generation-processor-optional","null","All optional interactions (listed in tm:optional) MAY be taken over to the Partial TD instance.",""
"thing-model-td-generation-processor-placeholder","null","If used, all placeholders (see Section ) in the Thing Model MUST be replaced with a valid corresponding value in the Partial TD.",""
"thing-model-td-generation-processor-required","null","If the tm:required feature is used based on Section , the required interactions MUST be taken over to the Partial TD instance.",""
"thing-model-td-generation-processor-required","null","All required interactions (not listed in tm:optional) MUST be taken over to the Partial TD instance.",""
"thing-model-td-generation-processor-type","null","The tm:ThingModel value of the top-level @type MUST be removed in the Partial TD instance.",""
"tm-overwrite-interaction","null","A Thing Model SHOULD NOT overwrite the JSON names defined within the properties, actions, and/or events Map of the extended Thing Model.",""
"tm-overwrite-types","null","Definitions SHOULD NOT be overwritten in such a way that possible instance values are no longer valid compared to the origin extended definitions.",""
"tm-placeholder-replacement","null","The placeholder labeling MUST be substituted with a concrete value (e.g., as JSON number, JSON string, JSON object, etc) when TD instance is created from the Thing Model.",""
"tm-ref-recursive-extensions","null","Recursive extensions leading to an infinite loop MUST NOT be defined.",""
"tm-tmOptional-resolver","null","The JSON Pointers of tm:optional MUST resolve to an entire interaction affordance Map definition.",""
"tm-tmRef-overwrite-possibility","null","If the intention is 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 declaration that provides a new value.",""
"tm-tmRef-overwrite-process","null","The process to overwrite MUST follow the JSON Merge Patch algorithm as defined in [RFC7396] where the content of the referenced definition is patched with the new provided JSON name-value pairs.",""
"tm-tmRef-overwrite-semantic-meaning","null","Similar to tm:extends and to keep the semantic meaning, definitions SHOULD NOT be overwritten in such a way that possible instance values are no longer valid compared to the origin referenced definition.",""
"tm-tmRef2","null","Every time tm:ref is used, the referenced pre-definition and its dependencies (e.g., by context extension) MUST be assumed at the new defined definition.",""
"tm-tmRequired-resolver","null","The JSON Pointers of tm:required MUST resolve to an entire interaction affordance Map definition.",""
"tm-tmRef2","null","Every time tm:ref is used, the referenced pre-definition and its dependencies (e.g., by context extension) MUST be assumed at the new defined definition.",""
15 changes: 7 additions & 8 deletions packages/assertions/assertions-csv/needsReview.csv
Original file line number Diff line number Diff line change
Expand Up @@ -3,40 +3,39 @@
"privacy-centralized-ids","null","TD identifiers SHOULD NOT be generated using a centralized authority.",""
"privacy-essential-metadata-only","null","Only the amount of information needed for the level of authorization and the use case SHOULD be provided in a TD.",""
"privacy-immutable-id-as-property","null","Ideally, any required immutable identifiers SHOULD only be made available via affordances, such as a property, whose value can only be obtained after appropriate authentication and authorization, and managed separately from the TD identifier.",""
"privacy-mutable-id-ownership","null","TD identifiers SHOULD be updated upon major changes in configuration or reinitialization.",""
"privacy-mutable-identifiers","null","All identifiers used in a TD SHOULD be mutable, and in particular there should be a mechanism to update the id of a Thing when necessary.",""
"privacy-td-pii","null","A Thing Description associated with a personal device SHOULD be treated as if it contained personally identifiable information, even if this information is not explicit.",""
"privacy-temp-id-metadata","null","Any temporary ID generated to manage TDs, for example an ID for a database or directory service, SHOULD NOT contain metadata describing the Thing or from the TD itself.",""
"sec-body-name-json-pointer-type","null",".",""
"sec-inj-no-intl-markup","null","HTML markup SHOULD NOT be used for internationalization purposes in TD strings.",""
"sec-inj-sanitize","null","Strings sourced from TDs MUST either be sanitized using a carefully vetted HTML sanitizer that disables any markup or should be inserted into an HTML template using DOM node manipulation APIs that will escape any markup.",""
"security-context-secure-fetch","null","If it is necessary to fetch a context definition file, an implementation SHOULD first attempt to use HTTP over TLS even when only an HTTP URL is given.",""
"security-jsonld-expansion","null","Consumers SHOULD set and enforce limits on memory usage to prevent buffer overflow and resource exhaustion during JSON-LD processing.",""
"security-mutual-auth-td","null","Thing Descriptions SHOULD be obtained only through mutually authenticated secure channels.",""
"security-no-execution","null","A WoT Thing Description JSON-LD serialization MUST NOT be passed through a code execution mechanism such as JavaScript's eval() function to be parsed.",""
"security-oauth-limits","null","To limit the scope and duration of access to Things, tokens SHOULD be used to manage access.",""
"security-remote-context","null","Constrained implementations SHOULD NOT follow links to remote contexts.",""
"security-server-auth-td","null","In cases where the Consumer is associated with a person, e.g. browsers, TDs MAY be obtained through a channel where only the TD provider is authenticated.",""
"security-static-context","null","Constrained implementations SHOULD use statically managed and vetted versions of their supported context extensions.",""
"security-update-contexts","null","Supported context extensions on constrained implementations MAY be managed through secure software update mechanisms.",""
"security-static-context","null","Constrained implementations SHOULD use vetted versions of their supported context extensions managed statically or as part of a secure update process.",""
"td-context-ns-td10-namespacev10","null","TD 1.1 consumers MUST accept TDs satisfying the W3C WoT Thing Description 1.0 [[wot-thing-description]] specification.",""
"td-default-AdditionalResponseContentType","null","AdditionalExpectedResponse contentType value of the contentType of the Form element it belongs to.",""
"td-default-observable","null","PropertyAffordance observable false",""
"td-processor-bidi-isolation","null","TD Processors SHOULD take care to use bidi isolation when presenting strings to users, particularly when embedding in surrounding text (e.g., for Web user interface)",""
"td-producer-mixed-direction","null","TD producers SHOULD attempt to provide mixed direction strings in a way that can be displayed successfully by a naive user agent.",""
"td-security-extension","null","Additional security schemes MUST be Subclasses of the Class SecurityScheme.",""
"td-text-direction-first-strong","null","When metadata such as @direction is not present, TD Consumers SHOULD use [=first-strong detection=] as a fallback.",""
"td-text-direction-language-tag","null","For the MultiLanguage Map, TD Consumers MAY infer the [=base direction=] from the language tag of the individual strings.",""
"thing-model-td-generation-processor-extends","null","If used",""
"thing-model-td-generation-processor-forms","null","Missing communication and/or security metadata details MUST be completed in the Thing Description instance based on Section and/or .",""
"thing-model-td-generation-processor-imports","null","Copy all definitions from the input Thing Model to the resulting Partial TD instance. If used, the extension and imports feature MUST be resolved and represented in the Partial TD instance according to .",""
"thing-model-td-generation-processor-optional","null","All optional interactions (listed in tm:optional) MAY be taken over to the Partial TD instance.",""
"thing-model-td-generation-processor-placeholder","null","If used, all placeholders (see Section ) in the Thing Model MUST be replaced with a valid corresponding value in the Partial TD.",""
"thing-model-td-generation-processor-required","null","If the tm:required feature is used based on Section , the required interactions MUST be taken over to the Partial TD instance.",""
"thing-model-td-generation-processor-required","null","All required interactions (not listed in tm:optional) MUST be taken over to the Partial TD instance.",""
"thing-model-td-generation-processor-type","null","The tm:ThingModel value of the top-level @type MUST be removed in the Partial TD instance.",""
"tm-overwrite-interaction","null","A Thing Model SHOULD NOT overwrite the JSON names defined within the properties, actions, and/or events Map of the extended Thing Model.",""
"tm-overwrite-types","null","Definitions SHOULD NOT be overwritten in such a way that possible instance values are no longer valid compared to the origin extended definitions.",""
"tm-placeholder-replacement","null","The placeholder labeling MUST be substituted with a concrete value (e.g., as JSON number, JSON string, JSON object, etc) when TD instance is created from the Thing Model.",""
"tm-ref-recursive-extensions","null","Recursive extensions leading to an infinite loop MUST NOT be defined.",""
"tm-tmOptional-resolver","null","The JSON Pointers of tm:optional MUST resolve to an entire interaction affordance Map definition.",""
"tm-tmRef-overwrite-possibility","null","If the intention is 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 declaration that provides a new value.",""
"tm-tmRef-overwrite-process","null","The process to overwrite MUST follow the JSON Merge Patch algorithm as defined in [RFC7396] where the content of the referenced definition is patched with the new provided JSON name-value pairs.",""
"tm-tmRef-overwrite-semantic-meaning","null","Similar to tm:extends and to keep the semantic meaning, definitions SHOULD NOT be overwritten in such a way that possible instance values are no longer valid compared to the origin referenced definition.",""
"tm-tmRef2","null","Every time tm:ref is used, the referenced pre-definition and its dependencies (e.g., by context extension) MUST be assumed at the new defined definition.",""
"tm-tmRequired-resolver","null","The JSON Pointers of tm:required MUST resolve to an entire interaction affordance Map definition.",""
"tm-tmRef2","null","Every time tm:ref is used, the referenced pre-definition and its dependencies (e.g., by context extension) MUST be assumed at the new defined definition.",""
3 changes: 2 additions & 1 deletion packages/assertions/assertions-csv/old.csv
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
"ID","Status","Assertion","Comment"
"ID","Status","Assertion","Comment"
"ID",,"Assertion",
2 changes: 1 addition & 1 deletion packages/assertions/assertions-csv/report.json
Original file line number Diff line number Diff line change
@@ -1 +1 @@
{"generationDate":"Fri, 29 Jul 2022 13:06:16 GMT","assertionsSize":453,"implementedSize":369,"manualSize":89,"oldSize":0,"needsReviewSize":41}
{"generationDate":"Fri, 19 Aug 2022 11:27:42 GMT","assertionsSize":453,"implementedSize":369,"manualSize":88,"oldSize":1,"needsReviewSize":40}
Loading