-
Notifications
You must be signed in to change notification settings - Fork 0
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
Better XML namespace #42
Comments
Well, technically it can be whatever unique URI we choose. If we are ever going to have a hostname for push, I think we could use it. Otherwise, we can directly use the repo URL, or even host some kind of schema on Github pages or similar and use it, even though it's not necessary by any means. If we need one right now, I'd go for the repo URL. |
Hm a good idea. https://www.rfc-editor.org/rfc/rfc3470#section-4.9 says:
By the way, can we just put it into
The repo URL would be unique and also point to the description (because the repo contains or links to the spec). The disadvantage is that the fate of the namespace is then bound to the RFC 4918 says:
So I think https://www.w3.org/TR/xml-names11/ talks about IRIs and URNs. What other specs use: |
Choose appropriate XML NS
Anyone knows what would be appropriate?
The text was updated successfully, but these errors were encountered: