From a20e9793a02282f50a9cd9f1552e20018b19bf8c Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Wed, 24 Apr 2024 12:21:47 +0200 Subject: [PATCH 01/11] the domain of model and instance classes changed to versioninfo --- ontology/td.ttl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ontology/td.ttl b/ontology/td.ttl index a27083a52..23f9d0806 100644 --- a/ontology/td.ttl +++ b/ontology/td.ttl @@ -153,13 +153,13 @@ :instance rdf:type owl:DatatypeProperty ; rdfs:label "instance" ; rdfs:comment "Provides a version identicator of this TD instance."@en ; - schema:domainIncludes :Thing ; + schema:domainIncludes :versionInfo ; rdfs:isDefinedBy . :model rdf:type owl:DatatypeProperty ; rdfs:label "model" ; rdfs:comment "Provides a version indicator of the underlying TM."@en ; - schema:domainIncludes :Thing ; + schema:domainIncludes :versionInfo ; rdfs:isDefinedBy . :isSafe rdf:type owl:DatatypeProperty ; From 28b48cdc94d156b10683838910c1c5918073675b Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Wed, 24 Apr 2024 12:26:00 +0200 Subject: [PATCH 02/11] render script changes --- ontology/td.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ontology/td.html b/ontology/td.html index 846c503a0..fee2c1c0a 100644 --- a/ontology/td.html +++ b/ontology/td.html @@ -116,7 +116,7 @@

Terminology

InteractionAffordance

IRI: https://www.w3.org/2019/wot/td#InteractionAffordance

Metadata of a Thing that shows the possible choices to Consumers, thereby suggesting how Consumers may interact with the Thing. There are many types of potential affordances, but W3C WoT defines three types of Interaction Affordances: Properties, Actions, and Events.
Super-class oftd:ActionAffordance
td:EventAffordance
td:PropertyAffordance
In the domain oftd:descriptionInLanguage
td:hasForm
td:hasUriTemplateSchema
td:name
td:titleInLanguage
tm:ref
In the range oftd:hasInteractionAffordance

OperationType

IRI: https://www.w3.org/2019/wot/td#OperationType

Enumeration of well-known operation types necessary to implement the WoT interaction model
Enumeration memberstd:cancelAction
td:invokeAction
td:observeAllProperties
td:observeProperty
td:queryAction
td:queryAllActions
td:readAllProperties
td:readMultipleProperties
td:readProperty
td:subscribeAllEvents
td:subscribeEvent
td:unobserveAllProperties
td:unobserveProperty
td:unsubscribeAllEvents
td:unsubscribeEvent
td:writeAllProperties
td:writeMultipleProperties
td:writeProperty

PropertyAffordance

IRI: https://www.w3.org/2019/wot/td#PropertyAffordance

An Interaction Affordance that exposes state of the Thing. This state can then be retrieved (read) and/or updated (write). Things can also choose to make Properties observable by pushing the new state after a change.
Sub-class oftd:InteractionAffordance
In the domain oftd:isObservable
In the range oftd:hasPropertyAffordance
-

Thing

IRI: https://www.w3.org/2019/wot/td#Thing

An abstraction of a physical or a virtual entity whose metadata and interfaces are described by a WoT Thing Description, whereas a virtual entity is the composition of one or more Things.
In the domain oftd:baseURI
td:definesSecurityScheme
td:descriptionInLanguage
td:followsProfile
td:hasForm
td:hasInteractionAffordance
td:hasSecurityConfiguration
td:instance
td:model
td:titleInLanguage

Object Properties

definesSecurityScheme

IRI: https://www.w3.org/2019/wot/td#definesSecurityScheme

A Thing may define abstract security schemes, used to configure the secure access of (a set of) affordance(s).
Domain includestd:Thing
+

Thing

IRI: https://www.w3.org/2019/wot/td#Thing

An abstraction of a physical or a virtual entity whose metadata and interfaces are described by a WoT Thing Description, whereas a virtual entity is the composition of one or more Things.
In the domain oftd:baseURI
td:definesSecurityScheme
td:descriptionInLanguage
td:followsProfile
td:hasForm
td:hasInteractionAffordance
td:hasSecurityConfiguration
td:titleInLanguage

Object Properties

definesSecurityScheme

IRI: https://www.w3.org/2019/wot/td#definesSecurityScheme

A Thing may define abstract security schemes, used to configure the secure access of (a set of) affordance(s).
Domain includestd:Thing

hasActionAffordance

IRI: https://www.w3.org/2019/wot/td#hasActionAffordance

All Action-based interaction affordance of the Thing.
Range includestd:ActionAffordance

hasCancellationSchema

IRI: https://www.w3.org/2019/wot/td#hasCancellationSchema

Defines any data that needs to be passed to cancel a subscription, e.g., a specific message to remove a Webhook
Domain includestd:EventAffordance

hasConfigurationInstance

IRI: https://www.w3.org/2019/wot/td#hasConfigurationInstance

Instantiation, as used here, is a form of non-symmetric equivalence between a scheme and a configuration: whatever statement on the scheme is also true of the configuration but not vice-versa.
Domain includeswotsec:SecurityScheme
@@ -135,12 +135,12 @@

Terminology

description

IRI: https://www.w3.org/2019/wot/td#description

Provides description of the Thing Model element.
Domain includestm:ThingModel
Range includesschema:Text

descriptionInLanguage

IRI: https://www.w3.org/2019/wot/td#descriptionInLanguage

description of the TD element (Thing, interaction affordance, security scheme or data schema) with language tag. By convention, a language tag must be added to the object of 'descriptionInLanguage' triples. Otherwise, use 'description'.
Domain includesjsonschema:DataSchema
wotsec:SecurityScheme
td:InteractionAffordance
td:Thing
Range includesschema:Text

followsProfile

IRI: https://www.w3.org/2019/wot/td#followsProfile

Indicates the WoT Profile mechanisms followed by this Thing Description and the corresponding Thing implementation.
Domain includestd:Thing
Range includes
-

instance

IRI: https://www.w3.org/2019/wot/td#instance

Provides a version identicator of this TD instance.
Domain includestd:Thing
+

instance

IRI: https://www.w3.org/2019/wot/td#instance

Provides a version identicator of this TD instance.
Domain includestd:versionInfo

isIdempotent

IRI: https://www.w3.org/2019/wot/td#isIdempotent

Indicates whether the action is idempotent (=true) or not. Informs whether the action can be called repeatedly with the same result, if present, based on the same input.
Domain includestd:ActionAffordance
Range includesschema:Boolean

isObservable

IRI: https://www.w3.org/2019/wot/td#isObservable

A hint that indicates whether Servients hosting the Thing and Intermediaries should provide a Protocol Binding that supports the observeproperty and unobserveproperty operations for this Property.
Domain includestd:PropertyAffordance
Range includesschema:Boolean

isSafe

IRI: https://www.w3.org/2019/wot/td#isSafe

Signals if the action is safe (=true) or not. Used to signal if there is no internal state (cf. resource state) is changed when invoking an Action. In that case responses can be cached as example.
Domain includestd:ActionAffordance
Range includesschema:Boolean

isSynchronous

IRI: https://www.w3.org/2019/wot/td#isSynchronous

Indicates whether the action is synchronous (=true) or not. A synchronous action means that the response of action contains all the information about the result of the action and no further querying about the status of the action is needed. Lack of this keyword means that no claim on the synchronicity of the action can be made.
Domain includestd:ActionAffordance
Range includesschema:Boolean
-

model

IRI: https://www.w3.org/2019/wot/td#model

Provides a version indicator of the underlying TM.
Domain includestd:Thing
+

model

IRI: https://www.w3.org/2019/wot/td#model

Provides a version indicator of the underlying TM.
Domain includestd:versionInfo

name

IRI: https://www.w3.org/2019/wot/td#name

Indexing property to store entity names when serializing them in a JSON-LD @index container.
Domain includestd:InteractionAffordance
Range includesschema:Text

title

IRI: https://www.w3.org/2019/wot/td#title

Provide the title of the Thing Model
Domain includestm:ThingModel
Range includesschema:Text

titleInLanguage

IRI: https://www.w3.org/2019/wot/td#titleInLanguage

title of the TD element (Thing, interaction affordance or data schema) with language tag. By convention, a language tag must be added to the object of 'titleInLanguage' triples. Otherwise, use 'title'.
Domain includesjsonschema:DataSchema
td:InteractionAffordance
td:Thing
Range includesschema:Text

Annotation Properties

supportContact

IRI: https://www.w3.org/2019/wot/td#supportContact

Provides information about the TD maintainer as URI scheme (e.g., mailto [[RFC6068]], tel [[RFC3966]], https[[RFC9112]]).
From bb35e9688a1d4afcf134e879863351a5484fa21a Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Wed, 24 Apr 2024 12:32:07 +0200 Subject: [PATCH 03/11] errata added for the mentioned issue --- errata.html | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/errata.html b/errata.html index 5d362de7e..a9c699f90 100644 --- a/errata.html +++ b/errata.html @@ -71,6 +71,10 @@

Substantive Issues

Editorial Issues

+
    +
  • 2024-04-24: In the Thing Description ontology and it's associated HTML page, the domain of classes model and instance has been changed to versionInfo to match the TD specification. This change does not affect the WoT TD 1.1. HTML specification. +
    • +
From 34a19eaaaf7defce806cccc6a0fdc9c1a75c2657 Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Fri, 5 Apr 2024 16:30:10 +0200 Subject: [PATCH 04/11] Term inconsistency The term is inconsistent with the one defined in the context file --- ontology/td.ttl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ontology/td.ttl b/ontology/td.ttl index 23f9d0806..7bc180031 100644 --- a/ontology/td.ttl +++ b/ontology/td.ttl @@ -130,8 +130,8 @@ schema:domainIncludes :Thing ; rdfs:isDefinedBy . -:hasConfigurationInstance rdf:type owl:ObjectProperty ; - rdfs:label "hasConfigurationInstance" ; +:hasInstanceConfiguration rdf:type owl:ObjectProperty ; + rdfs:label "hasInstanceConfiguration" ; rdfs:comment "Instantiation, as used here, is a form of non-symmetric equivalence between a scheme and a configuration: whatever statement on the scheme is also true of the configuration but not vice-versa." ; schema:domainIncludes wotsec:SecurityScheme ; rdfs:isDefinedBy . From ff30a391cbae504b066643913be4a827b3b2eefa Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Fri, 5 Apr 2024 16:44:28 +0200 Subject: [PATCH 05/11] changes affected with render script --- ontology/td.html | 2 +- ontology/wotsec.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ontology/td.html b/ontology/td.html index fee2c1c0a..36ff9cc42 100644 --- a/ontology/td.html +++ b/ontology/td.html @@ -119,10 +119,10 @@

Terminology

Thing

IRI: https://www.w3.org/2019/wot/td#Thing

An abstraction of a physical or a virtual entity whose metadata and interfaces are described by a WoT Thing Description, whereas a virtual entity is the composition of one or more Things.
In the domain oftd:baseURI
td:definesSecurityScheme
td:descriptionInLanguage
td:followsProfile
td:hasForm
td:hasInteractionAffordance
td:hasSecurityConfiguration
td:titleInLanguage

Object Properties

definesSecurityScheme

IRI: https://www.w3.org/2019/wot/td#definesSecurityScheme

A Thing may define abstract security schemes, used to configure the secure access of (a set of) affordance(s).
Domain includestd:Thing

hasActionAffordance

IRI: https://www.w3.org/2019/wot/td#hasActionAffordance

All Action-based interaction affordance of the Thing.
Range includestd:ActionAffordance

hasCancellationSchema

IRI: https://www.w3.org/2019/wot/td#hasCancellationSchema

Defines any data that needs to be passed to cancel a subscription, e.g., a specific message to remove a Webhook
Domain includestd:EventAffordance
-

hasConfigurationInstance

IRI: https://www.w3.org/2019/wot/td#hasConfigurationInstance

Instantiation, as used here, is a form of non-symmetric equivalence between a scheme and a configuration: whatever statement on the scheme is also true of the configuration but not vice-versa.
Domain includeswotsec:SecurityScheme

hasEventAffordance

IRI: https://www.w3.org/2019/wot/td#hasEventAffordance

All Event-based interaction affordance of the Thing.
Range includestd:EventAffordance

hasForm

IRI: https://www.w3.org/2019/wot/td#hasForm

Set of form hypermedia controls that describe how an operation can be performed. Forms are serializations of Protocol Bindings. The array cannot be empty
Domain includestd:InteractionAffordance
td:Thing
Range includeshctl:Form

hasInputSchema

IRI: https://www.w3.org/2019/wot/td#hasInputSchema

Used to define the input data schema of the action.
Domain includestd:ActionAffordance
+

hasInstanceConfiguration

IRI: https://www.w3.org/2019/wot/td#hasInstanceConfiguration

Instantiation, as used here, is a form of non-symmetric equivalence between a scheme and a configuration: whatever statement on the scheme is also true of the configuration but not vice-versa.
Domain includeswotsec:SecurityScheme

hasInteractionAffordance

IRI: https://www.w3.org/2019/wot/td#hasInteractionAffordance

Offers an affordance to interact with the Thing
Domain includestd:Thing
tm:ThingModel
Range includestd:InteractionAffordance

hasNotificationResponseSchema

IRI: https://www.w3.org/2019/wot/td#hasNotificationResponseSchema

Defines the data schema of the Event response messages sent by the consumer in a response to a data message.
Domain includestd:EventAffordance
diff --git a/ontology/wotsec.html b/ontology/wotsec.html index 4ab05f4ca..2c8cc1d83 100644 --- a/ontology/wotsec.html +++ b/ontology/wotsec.html @@ -95,7 +95,7 @@

Terminology

NoSecurityScheme

IRI: https://www.w3.org/2019/wot/security#NoSecurityScheme

A security configuration corresponding to identified by the term nosec (i.e., "scheme": "nosec"), indicating there is no authentication or other mechanism required to access the resource.
Sub-class ofwotsec:SecurityScheme

OAuth2SecurityScheme

IRI: https://www.w3.org/2019/wot/security#OAuth2SecurityScheme

OAuth 2.0 authentication security configuration for systems conformant with [[!RFC6749]] and [[!RFC8252]], identified by the Vocabulary Term oauth2 (i.e., "scheme": "oauth2"). For the code flow both authorization and token MUST be included. For the client flow token MUST be included. For the client flow authorization MUST NOT be included. The mandatory elements for each flow are summarized in the following table:
Elementcodeclient
authorizationmandatoryomit
tokenmandatorymandatory
refreshoptionaloptional

Sub-class ofwotsec:SecurityScheme
In the domain ofwotsec:authorization
wotsec:flow
wotsec:refresh
wotsec:scopes
wotsec:token

PSKSecurityScheme

IRI: https://www.w3.org/2019/wot/security#PSKSecurityScheme

Pre-shared key authentication security configuration identified by the term psk (i.e., "scheme": "psk"). This is meant to identify that a standard is used for pre-shared keys such as TLS-PSK [[rfc4279]], and that the ciphersuite used for keys will be established during protocol negotiation.
Sub-class ofwotsec:SecurityScheme
In the domain ofwotsec:identity
-

SecurityScheme

IRI: https://www.w3.org/2019/wot/security#SecurityScheme

Metadata describing the configuration of a security mechanism. 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.

For all security schemes, any keys, passwords, or other sensitive information directly providing access MUST NOT be stored in the TD and should instead be shared and stored out-of-band via other mechanisms. The purpose of a TD is to describe how to access a Thing if and only if a Consumer already has authorization, and is not meant be used to grant that authorization.

Each security scheme object used in a TD defines a set of requirements to be met before access can be granted. We say a security scheme is satisfied when all its requirements are met. In some cases requirements from multiple security schemes will have to be met before access can be granted.

Security schemes generally may require additional authentication parameters, such as a password or key. The location of this information is indicated by the value associated with the name in, often in combination with the value associated with name. The in name can take one of the following values:

header:
The parameter will be given in a header provided by the protocol, with the name of the header provided by the value of name.
query:
The parameter will be appended to the URI as a query parameter, with the name of the query parameter provided by name.
body:
The parameter will be provided in the body of the request payload, with the data schema element used provided by name. 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. Since this value is not a fragment identifier, and is not relative to the root of the TD but to whichever data schemas the security scheme is bound to, this value should not start with "#"; it is a "pure" JSON pointer. Since this value is not a fragment identifier, it also does not need to URL-encode special characters. The targeted element may or may not already exist at the specified location in the referenced data schema. If it does not, it will be inserted. This avoids having to duplicate definitions in the data schemas of every interaction. 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.. For example, pointing to a key of a Map where that key does not exist in the corresponding Data Schema, the key and its value, which is the credential, would be inserted to the Map at the specified location during the operation execution. On the other hand, pointing to an Array's item with a number as the item index, that number should be outside the range of the Array's already specified items in order to not alter the strict sequence of items. The JSON pointer used in the body locator MAY use the "-" character to indicate a non-existent array element when it is necessary to insert an element after the last element of an existing array. The element referenced (or created) by a body security information location MUST be required and of type "string". If name is not given, it is assumed the entire body is to be used as the security parameter.
cookie:
The parameter is stored in a cookie identified by the value of name.
uri:
The parameter is embedded in the URI itself, which is encoded in the relevant interaction using a URI template variable defined by the value of name. This is more general than the query mechanism but more complex. The value uri SHOULD be specified for in in a security scheme only if query is not applicable. The URIs provided in interactions where a security scheme using uri MUST be a URI template including the defined variable.
auto:
The location is determined as part of the protocol, or negotiated. If a value of auto is set for the in field of a SecurityScheme, then the name field SHOULD NOT be set. In this case, the application of the SecurityScheme is subject to the respective specification for the given protocol (e.g. [[!RFC8288]] when using the BasicSecurityScheme with HTTP).
If multiple parameters are needed for a security scheme, repeat the security scheme definition for each parameter and combine them using a combo security scheme and allOf. In some cases parameters may not actually be secret but a user may wish to leave them out of the TD to help protect privacy. As an example of this, some security mechanisms require both a client identifier and a secret key. In theory, the client identifier is public however it may be hard to update and pose a tracking risk. In such a case it can be provided as an additional security parameter so it does not appear in the TD.

The names of URI variables declared in a SecurityScheme MUST be distinct from all other URI variables declared in the TD.

Super-class ofwotsec:APIKeySecurityScheme
wotsec:AutoSecurityScheme
wotsec:BasicSecurityScheme
wotsec:BearerSecurityScheme
wotsec:ComboSecurityScheme
wotsec:DigestSecurityScheme
wotsec:NoSecurityScheme
wotsec:OAuth2SecurityScheme
wotsec:PSKSecurityScheme
In the domain ofwotsec:proxy
td:descriptionInLanguage
td:hasConfigurationInstance

Object Properties

allOf

IRI: https://www.w3.org/2019/wot/security#allOf

Array of two or more strings identifying other named security scheme definitions, all of which must be satisfied for access.
Domain includeswotsec:ComboSecurityScheme
+

SecurityScheme

IRI: https://www.w3.org/2019/wot/security#SecurityScheme

Metadata describing the configuration of a security mechanism. 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.

For all security schemes, any keys, passwords, or other sensitive information directly providing access MUST NOT be stored in the TD and should instead be shared and stored out-of-band via other mechanisms. The purpose of a TD is to describe how to access a Thing if and only if a Consumer already has authorization, and is not meant be used to grant that authorization.

Each security scheme object used in a TD defines a set of requirements to be met before access can be granted. We say a security scheme is satisfied when all its requirements are met. In some cases requirements from multiple security schemes will have to be met before access can be granted.

Security schemes generally may require additional authentication parameters, such as a password or key. The location of this information is indicated by the value associated with the name in, often in combination with the value associated with name. The in name can take one of the following values:

header:
The parameter will be given in a header provided by the protocol, with the name of the header provided by the value of name.
query:
The parameter will be appended to the URI as a query parameter, with the name of the query parameter provided by name.
body:
The parameter will be provided in the body of the request payload, with the data schema element used provided by name. 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. Since this value is not a fragment identifier, and is not relative to the root of the TD but to whichever data schemas the security scheme is bound to, this value should not start with "#"; it is a "pure" JSON pointer. Since this value is not a fragment identifier, it also does not need to URL-encode special characters. The targeted element may or may not already exist at the specified location in the referenced data schema. If it does not, it will be inserted. This avoids having to duplicate definitions in the data schemas of every interaction. 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.. For example, pointing to a key of a Map where that key does not exist in the corresponding Data Schema, the key and its value, which is the credential, would be inserted to the Map at the specified location during the operation execution. On the other hand, pointing to an Array's item with a number as the item index, that number should be outside the range of the Array's already specified items in order to not alter the strict sequence of items. The JSON pointer used in the body locator MAY use the "-" character to indicate a non-existent array element when it is necessary to insert an element after the last element of an existing array. The element referenced (or created) by a body security information location MUST be required and of type "string". If name is not given, it is assumed the entire body is to be used as the security parameter.
cookie:
The parameter is stored in a cookie identified by the value of name.
uri:
The parameter is embedded in the URI itself, which is encoded in the relevant interaction using a URI template variable defined by the value of name. This is more general than the query mechanism but more complex. The value uri SHOULD be specified for in in a security scheme only if query is not applicable. The URIs provided in interactions where a security scheme using uri MUST be a URI template including the defined variable.
auto:
The location is determined as part of the protocol, or negotiated. If a value of auto is set for the in field of a SecurityScheme, then the name field SHOULD NOT be set. In this case, the application of the SecurityScheme is subject to the respective specification for the given protocol (e.g. [[!RFC8288]] when using the BasicSecurityScheme with HTTP).
If multiple parameters are needed for a security scheme, repeat the security scheme definition for each parameter and combine them using a combo security scheme and allOf. In some cases parameters may not actually be secret but a user may wish to leave them out of the TD to help protect privacy. As an example of this, some security mechanisms require both a client identifier and a secret key. In theory, the client identifier is public however it may be hard to update and pose a tracking risk. In such a case it can be provided as an additional security parameter so it does not appear in the TD.

The names of URI variables declared in a SecurityScheme MUST be distinct from all other URI variables declared in the TD.

Super-class ofwotsec:APIKeySecurityScheme
wotsec:AutoSecurityScheme
wotsec:BasicSecurityScheme
wotsec:BearerSecurityScheme
wotsec:ComboSecurityScheme
wotsec:DigestSecurityScheme
wotsec:NoSecurityScheme
wotsec:OAuth2SecurityScheme
wotsec:PSKSecurityScheme
In the domain ofwotsec:proxy
td:descriptionInLanguage
td:hasInstanceConfiguration

Object Properties

allOf

IRI: https://www.w3.org/2019/wot/security#allOf

Array of two or more strings identifying other named security scheme definitions, all of which must be satisfied for access.
Domain includeswotsec:ComboSecurityScheme

authorization

IRI: https://www.w3.org/2019/wot/security#authorization

URI of the authorization server.
Domain includeswotsec:BearerSecurityScheme
wotsec:OAuth2SecurityScheme

oneOf

IRI: https://www.w3.org/2019/wot/security#oneOf

Array of two or more strings identifying other named security scheme definitions, any one of which, when satisfied, will allow access. Only one may be chosen for use.
Domain includeswotsec:ComboSecurityScheme

refresh

IRI: https://www.w3.org/2019/wot/security#refresh

URI of the refresh server.
Domain includeswotsec:OAuth2SecurityScheme
From 53092506c69bc3d1f339ad41feda467f10c1de41 Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Thu, 18 Apr 2024 10:13:07 +0200 Subject: [PATCH 06/11] ref and repository specification changed --- .github/workflows/prettify.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/prettify.yml b/.github/workflows/prettify.yml index e875b8f8c..b16d71f76 100644 --- a/.github/workflows/prettify.yml +++ b/.github/workflows/prettify.yml @@ -23,7 +23,8 @@ jobs: uses: actions/checkout@v3 with: # Make sure the actual branch is checked out when running on pull requests - ref: ${{ github.head_ref }} + ref: ${{ github.event.pull_request.head.ref }} + repository: ${{ github.event.pull_request.head.repo.full_name }} # This is important to fetch the changes to the previous commit fetch-depth: 0 From ee5a215638c72453babbb023389b89a2abf2aa80 Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Thu, 18 Apr 2024 09:39:35 +0200 Subject: [PATCH 07/11] errata modified for issue #1988, term inconsistency among ontology and context files --- errata11.html | 3 +++ 1 file changed, 3 insertions(+) diff --git a/errata11.html b/errata11.html index bb19c92af..3e272fc9a 100644 --- a/errata11.html +++ b/errata11.html @@ -72,6 +72,9 @@

Substantive Issues

Editorial Issues

+
From 554bec849664ea561d4ec42ceeb21475e551e3a5 Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Wed, 24 Apr 2024 11:48:51 +0200 Subject: [PATCH 08/11] Update errata11.html Co-authored-by: Ege Korkan --- errata11.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/errata11.html b/errata11.html index 3e272fc9a..f33a230e6 100644 --- a/errata11.html +++ b/errata11.html @@ -73,7 +73,8 @@

Substantive Issues

Editorial Issues

From 278a9d3fd047be563312c124747f0015d98a329e Mon Sep 17 00:00:00 2001 From: MahdaNoura Date: Wed, 24 Apr 2024 12:08:09 +0200 Subject: [PATCH 09/11] date added to the errata entry --- errata11.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/errata11.html b/errata11.html index f33a230e6..27d9ef394 100644 --- a/errata11.html +++ b/errata11.html @@ -73,7 +73,7 @@

Substantive Issues

Editorial Issues

From 069724b027260c1114003b4226bd96674545b3c4 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Thu, 25 Apr 2024 14:24:07 +0200 Subject: [PATCH 10/11] change the errata information from 1.0 to 1.1 --- errata.html | 2 -- errata11.html | 6 ++++++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/errata.html b/errata.html index a9c699f90..b6bb1da28 100644 --- a/errata.html +++ b/errata.html @@ -72,8 +72,6 @@

Substantive Issues

Editorial Issues

    -
  • 2024-04-24: In the Thing Description ontology and it's associated HTML page, the domain of classes model and instance has been changed to versionInfo to match the TD specification. This change does not affect the WoT TD 1.1. HTML specification. -
diff --git a/errata11.html b/errata11.html index 27d9ef394..edc1cc76f 100644 --- a/errata11.html +++ b/errata11.html @@ -75,6 +75,12 @@

Editorial Issues

From 5277ce3525779ad0ac1c1144aaa77f8e2e3605bb Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Thu, 25 Apr 2024 14:24:28 +0200 Subject: [PATCH 11/11] remove empty listing --- errata.html | 2 -- 1 file changed, 2 deletions(-) diff --git a/errata.html b/errata.html index b6bb1da28..5d362de7e 100644 --- a/errata.html +++ b/errata.html @@ -71,8 +71,6 @@

Substantive Issues

Editorial Issues

-
    -