Validation of TDs

[danielpeintner]

During the F2F the aspect was discussed that uploading TDs should guarantee accuracy.

Question: How much validation is done at the moment? JSON-LD processing?

Does it make sense to do a validation check via JSON schema and/or playground libraries?
Doing so guarantees that we have accurate TDs only in the directory.

[wiresio]

You can enable JSON-schema validation for the TD upload:
PUT TD to <WOT API URL>/things?check-schema=true

[danielpeintner]

You can enable JSON-schema validation for the TD upload:
PUT TD to <WOT API URL>/things?check-schema=true

Great, thanks! I missed that.
What kind of validation is used? JSON schema?

FYI: playground has some even more sophisticated validation, @egekorkan knows more.
see https://github.com/eclipse-thingweb/playground?tab=readme-ov-file#packages

[wiresio]

Great, thanks! I missed that. What kind of validation is used? JSON schema?

tdd/data/td-json-schema-validation.json

FYI: playground has some even more sophisticated validation, @egekorkan knows more. see https://github.com/eclipse-thingweb/playground?tab=readme-ov-file#packages

Happy to discuss which additional validations might make sense.

[egekorkan]

With the new charter, there are some linting discussions happening but there are still mandatory validations. One example of each:

• Linting: enum and const should not be present at the same time. JSON Schema rules take apply both so enum is not needed but will not throw a validation error during payload validation.
• Required Validation: security must link to an existing key within securityDefinitions

[Murloc6]

With the new charter, there are some linting discussions happening but there are still mandatory validations. One example of each:

* Linting: `enum` and `const` should not be present at the same time. JSON Schema rules take apply both so enum is not needed but will not throw a validation error during payload validation.

* Required Validation: `security` must link to an existing key within `securityDefinitions`

If I understand your comment, it means that the JSON Schema versioned here is not correct anymore and must be updated regarding the new JSON Schema specification from the W3C WG ?

[egekorkan]

If I understand your comment, it means that the JSON Schema versioned here is not correct anymore and must be updated regarding the new JSON Schema specification from the W3C WG ?

No I did not mean that. However, the schema here is older than the 1.1 Schema at https://github.com/w3c/wot-thing-description/blob/main/validation/td-json-schema-validation.json. I am not sure if this is intentional though.