We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments.
name of spec to be reviewed: Personalization Semantics Content Module 1.0
URL of spec: https://w3c.github.io/personalization-semantics/content/
What and when is your next expected transition? We want to start CR transiton process before November 2021.
What has changed since any previous review? This working draft is developed by APA WG, and we don't have any a11y review before.
Where and how to file issues arising? https://w3c.github.io/personalization-semantics/
Pointer to any explainer for the spec? https://github.com/w3c/personalization-semantics/issues
The text was updated successfully, but these errors were encountered:
No comments from APA (the publisher).
Sorry, something went wrong.
No branches or pull requests
In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments.
name of spec to be reviewed: Personalization Semantics Content Module 1.0
URL of spec: https://w3c.github.io/personalization-semantics/content/
What and when is your next expected transition? We want to start CR transiton process before November 2021.
What has changed since any previous review? This working draft is developed by APA WG, and we don't have any a11y review before.
Where and how to file issues arising? https://w3c.github.io/personalization-semantics/
Pointer to any explainer for the spec? https://github.com/w3c/personalization-semantics/issues
The text was updated successfully, but these errors were encountered: