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.

Sign up for GitHub

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

Jump to bottom

Rule "recursive All proposed XML namespaces created by the publication of the document MUST follow URIs for W3C Namespaces . " #101

Open
dontcallmedom opened this issue Nov 21, 2014 · 3 comments
Open

Rule "recursive All proposed XML namespaces created by the publication of the document MUST follow URIs for W3C Namespaces . " #101

dontcallmedom opened this issue Nov 21, 2014 · 3 comments
Labels
how-to-check wd-feature-parity

Comments

@dontcallmedom
Copy link
Member

Is it implemented?
@dontcallmedom dontcallmedom self-assigned this Nov 21, 2014
@dontcallmedom dontcallmedom modified the milestones: Specberus ready to replace existing pubrules checker, Parity in automatic checks Nov 21, 2014
@dontcallmedom
Copy link
Member Author

I propose this doesn't need to be part of the automated workflow since there will be many false positives in any case. moving to different milestone

@deniak deniak added the v1.5 label Dec 18, 2014
@dontcallmedom dontcallmedom removed their assignment Jan 18, 2016
@deniak deniak removed the v1.5 label May 19, 2016
@deniak deniak self-assigned this Jun 6, 2016
@plehegar
Copy link
Member

👍

@deniak deniak removed this from the Replacement of old pubrules checker milestone Jun 21, 2016
@deniak
Copy link
Member

deniak commented Jun 21, 2016

This won't be part of the official release on Aug 1st, 2016

@deniak deniak removed their assignment Sep 17, 2018
@NOUIY NOUIY mentioned this issue May 20, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
how-to-check wd-feature-parity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@dontcallmedom @tripu @plehegar @deniak @jennyliang220