-
Notifications
You must be signed in to change notification settings - Fork 47
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
[wg/sdw] Spatial Data on the Web Working Group Charter #474
Comments
Overall the charter looks good. I was unsure what this sentence was intended to mean:
|
I see that it does now have that section. |
APA would like to be listed in the liaison groups. so we want to hear about work in the early stages, is that, whilst you are developing low-level APIs, there may be semantic metadata that have an impact on accessibility – either things we’d like you to include to promote accessibility, or accessibility risks relating to things you are proposing to include. |
no comment or request from i18n |
No comment from PING |
Some copy-editing improvements:
|
No comments from Security |
no comments from APA. |
You could delete
|
Deleted. |
The spec name in the 4th bullet of the Scope Sec. is missing. |
Fixed. |
New charter proposal, reviewers please take note.
Charter Review
Proposed SDW WG charter
diff from charter template
Diff from previous charter
chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach:
Known or potential areas of concern:
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...): w3c/charter-drafts
Anything else we should think about as we review?
Note: proposed chairs should be copied @... on this issue: @ldesousa, @rob-metalinkage
The text was updated successfully, but these errors were encountered: