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

Verify the presence of new new context value for submitted TDs #265

Open
egekorkan opened this issue Mar 17, 2022 · 2 comments
Open

Verify the presence of new new context value for submitted TDs #265

egekorkan opened this issue Mar 17, 2022 · 2 comments

Comments

@egekorkan
Copy link
Contributor

Validation script will accept TDs that have the old context URL. However, since we are generating the implementation report for TD 1.1, the TDs that are submitted MUST have the new URL.

@danielpeintner
Copy link
Contributor

Validation script will accept TDs that have the old context URL.

Should this read?
Validation script will accept TDs that have ONLY the old context URL.

@egekorkan
Copy link
Contributor Author

No. Playground is not designed to test only for generating the implementation report. So it will follow the assertion of the TD spec that says:

The @context name-value pair MUST contain the anyURI https://www.w3.org/2022/wot/td/v1.1 in order to identify the document as a TD 1.1 which would allow Consumers to use the newly introduced terms. When there are possibly TD 1.0 consumers the anyURI https://www.w3.org/2019/wot/td/v1 MUST be the first entry and the https://www.w3.org/2022/wot/td/v1.1 MUST be the second entry.

The final behavior of playground during the V1.1 standardization should be:

  • accept @context with only v1 context
  • accept @context with only v1.1 context
  • accept @context with v1 followed by v1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants