Merge pull request #474 from thingweb/assertion-csv-sync

Update assertions.csv and generate manual.csv

packages/assertions/assertions-csv/assertions.csv

@@ -10,7 +10,6 @@
 "privacy-distributed-ids","null","TD identifiers SHOULD be generated using a distributed mechanism such as UUIDs that provides a high probability of uniqueness."
 "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-id-metadata","null","The value of the id of a TD SHOULD NOT contain metadata describing the Thing or from the TD itself."
-"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-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-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","null","When used in the context of a body security information location, the value of name MUST be in the form of a JSON pointer [[!RFC6901]] relative to the root of the input DataSchema for each interaction it is used with."
@@ -20,7 +19,6 @@
 "sec-inj-no-intl-markup","null","HTML markup SHOULD NOT be used for internationalization purposes in TD strings."
 "sec-security-vocab-auto-in-no-name","null","If a value of auto is set for the in field of a SecurityScheme, then the name field SHOULD NOT be set."
 "sec-vuln-auto","null","The auto security scheme MAY be used if vulnerability scanning is a concern."
-"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."
@@ -246,7 +244,6 @@
 "td-security-oauth2-client-flow","null","For the client flow token vocabulary term MUST be included."
 "td-security-oauth2-client-flow-no-auth","null","For the client flow authorization vocabulary term MUST NOT be included."
 "td-security-oauth2-code-flow","null","For the code flow both authorization and token vocabulary terms MUST be included."
-"td-security-oauth2-device-flow","null","For the device flow both authorization and token vocabulary terms MUST be included."
 "td-security-overrides","null","Security definitions MAY also be activated at the level of the form elements by including a security member in form objects, which overrides (i.e., completely replace) all definitions activated at the Thing level."
 "td-security-scheme-name","null","The value assigned to the name scheme MUST be defined within a Vocabulary included in the Thing Description, either in the standard Vocabulary defined in § 5. TD Information Model or in a TD Context Extension."
 "td-security-schemes","null","All name-value pairs of an instance of one of the Subclasses of SecurityScheme, where the name is a Vocabulary Term included in the Signature of that Subclass or in the Signature of SecurityScheme, MUST be serialized as members of the JSON object that results from serializing the SecurityScheme Subclass's instance, with the Vocabulary Term as name."
@@ -273,7 +270,7 @@
 "td-vocab-at-type--SecurityScheme","null","@typeJSON-LD keyword to label the object with semantic tags (or types).optionalstring or Array of string"
 "td-vocab-at-type--Thing","null","@typeJSON-LD keyword to label the object with semantic tags (or types).optionalstring or Array of string"
 "td-vocab-authorization--BearerSecurityScheme","null","authorizationURI of the authorization server.optionalanyURI"
-"td-vocab-authorization--OAuth2SecurityScheme","null","authorizationURI of the authorization server. In the case of the device flow, the URI provided for the authorization value refers to the device authorization endpoint [[!RFC8628]].optionalanyURI"
+"td-vocab-authorization--OAuth2SecurityScheme","null","authorizationURI of the authorization server.optionalanyURI"
 "td-vocab-base--Thing","null","baseDefine the base URI that is used for all relative URI references throughout a TD document. In TD instances, all relative URIs are resolved relative to the base URI using the algorithm defined in [RFC3986]. base does not affect the URIs used in @context and the IRIs used within Linked Data [LINKED-DATA] graphs that are relevant when semantic processing is applied to TD instances.optionalanyURI"
 "td-vocab-cancellation--EventAffordance","null","cancellationDefines any data that needs to be passed to cancel a subscription, e.g., a specific message to remove a Webhook.optionalDataSchema"
 "td-vocab-const--DataSchema","null","constProvides a constant value.optionalany type"
@@ -301,7 +298,7 @@
 "td-vocab-exclusiveMaximum--NumberSchema","null","exclusiveMaximumSpecifies a maximum numeric value, representing an exclusive upper limit. Only applicable for associated number or integer types.optionaldouble"
 "td-vocab-exclusiveMinimum--IntegerSchema","null","exclusiveMinimumSpecifies a minimum numeric value, representing an exclusive lower limit. Only applicable for associated number or integer types.optionalinteger"
 "td-vocab-exclusiveMinimum--NumberSchema","null","exclusiveMinimumSpecifies a minimum numeric value, representing an exclusive lower limit. Only applicable for associated number or integer types.optionaldouble"
-"td-vocab-flow--OAuth2SecurityScheme","null","flowAuthorization flow.mandatorystring (e.g., code, client, or device)"
+"td-vocab-flow--OAuth2SecurityScheme","null","flowAuthorization flow.mandatorystring (e.g., code, or client)"
 "td-vocab-format--BearerSecurityScheme","null","formatSpecifies format of security authentication information.with defaultstring (e.g., jwt, cwt, jwe, or jws)"
 "td-vocab-format--DataSchema","null","formatAllows validation based on a format pattern such as ""date-time"", ""email"", ""uri"", etc. (Also see below.)optionalstring"
 "td-vocab-forms--InteractionAffordance","null","formsSet of form hypermedia controls that describe how an operation can be performed. Forms are serializations of Protocol Bindings. The array cannot be empty.mandatoryArray of Form"

packages/assertions/assertions-csv/changelog.md

@@ -1,7 +1,48 @@
 
-# CSV Changelog - 21/05/2023
+# CSV Changelog - 27/05/2023
 
 [Old CSV Path](assertions-csv/oldManual.csv)  
 [New CSV Path](assertions-csv/manual.csv)
 
-There are no changes between both files
+
+## REMOVED
+
+- `privacy-immutable-id-as-property` was removed
+- `security-context-secure-fetch` was removed
+
+
+## LINE-CHANGE
+
+- `privacy-mutable-identifiers` was moved from Line 51 to 50
+- `privacy-temp-id-metadata` was moved from Line 52 to 51
+- `sec-body-name-json-pointer-type` was moved from Line 53 to 52
+- `sec-inj-no-intl-markup` was moved from Line 54 to 53
+- `security-jsonld-expansion` was moved from Line 56 to 54
+- `security-mutual-auth-td` was moved from Line 57 to 55
+- `security-no-execution` was moved from Line 58 to 56
+- `security-oauth-limits` was moved from Line 59 to 57
+- `security-remote-context` was moved from Line 60 to 58
+- `security-server-auth-td` was moved from Line 61 to 59
+- `security-static-context` was moved from Line 62 to 60
+- `td-context-ns-td10-namespacev10` was moved from Line 63 to 61
+- `td-default-AdditionalResponseContentType` was moved from Line 64 to 62
+- `td-default-observable` was moved from Line 65 to 63
+- `td-processor-bidi-isolation` was moved from Line 66 to 64
+- `td-producer-mixed-direction` was moved from Line 67 to 65
+- `td-security-extension` was moved from Line 68 to 66
+- `td-text-direction-first-strong` was moved from Line 69 to 67
+- `td-text-direction-language-tag` was moved from Line 70 to 68
+- `thing-model-td-generation-processor-extends` was moved from Line 71 to 69
+- `thing-model-td-generation-processor-forms` was moved from Line 72 to 70
+- `thing-model-td-generation-processor-placeholder` was moved from Line 73 to 71
+- `thing-model-td-generation-processor-required` was moved from Line 74 to 72
+- `tm-derivation-validity` was moved from Line 75 to 73
+- `tm-overwrite-interaction` was moved from Line 76 to 74
+- `tm-overwrite-types` was moved from Line 77 to 75
+- `tm-placeholder-replacement` was moved from Line 78 to 76
+- `tm-ref-recursive-extensions` was moved from Line 79 to 77
+- `tm-tmRef-overwrite-possibility` was moved from Line 80 to 78
+- `tm-tmRef-overwrite-process` was moved from Line 81 to 79
+- `tm-tmRef-overwrite-semantic-meaning` was moved from Line 82 to 80
+- `tm-tmRef2` was moved from Line 83 to 81
+- `tm-versioning-1` was moved from Line 84 to 82

packages/assertions/assertions-csv/implemented.csv

@@ -182,7 +182,6 @@
 "td-security-oauth2-client-flow","null",,"For the client flow token MUST be included."
 "td-security-oauth2-client-flow-no-auth","null",,""
 "td-security-oauth2-code-flow","null",,"For the code flow both authorization and token MUST be included."
-"td-security-oauth2-device-flow","null",,"For the device flow both authorization and token MUST be included."
 "td-security-overrides","null",,""
 "td-security-scheme-name","null",,""
 "td-security-schemes","null",,""

packages/assertions/assertions-csv/manual.csv

@@ -48,12 +48,10 @@
 "privacy-auth-users-only","null","not testable with Assertion Tester","Only authorized users SHOULD be provided access to the Thing Description for a Thing."
 "privacy-centralized-ids","null","not testable with Assertion Tester","TD identifiers SHOULD NOT be generated using a centralized authority."
 "privacy-essential-metadata-only","null","not testable with Assertion Tester","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","not testable with Assertion Tester","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-identifiers","null","not testable with Assertion Tester","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-temp-id-metadata","null","not testable with Assertion Tester","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","not testable with Assertion Tester","."
 "sec-inj-no-intl-markup","null","not testable with Assertion Tester","HTML markup SHOULD NOT be used for internationalization purposes in TD strings."
-"security-context-secure-fetch","null","not testable with Assertion Tester","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","not testable with Assertion Tester","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","not testable with Assertion Tester","Thing Descriptions SHOULD be obtained only through mutually authenticated secure channels."
 "security-no-execution","null","not testable with Assertion Tester","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."

packages/assertions/assertions-csv/old.csv

@@ -1 +1,4 @@
-"ID","Status","Comment","Assertion"
+"ID","Status","Comment","Assertion"
+"td-security-oauth2-device-flow",,"not testable with Assertion Tester","For the device flow both authorization and token MUST be included."
+"privacy-immutable-id-as-property",,"not testable with Assertion Tester","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."
+"security-context-secure-fetch",,"not testable with Assertion Tester","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."

packages/assertions/assertions-csv/report.json

@@ -1 +1 @@
-{"generationDate":"Sun, 21 May 2023 01:04:31 GMT","assertionsSize":454,"implementedSize":373,"manualSize":84,"oldSize":0,"needsReviewSize":0}
+{"generationDate":"Sat, 27 May 2023 01:02:28 GMT","assertionsSize":451,"implementedSize":372,"manualSize":82,"oldSize":3,"needsReviewSize":0}