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

Various errata from 1.1 #4

Closed
3 tasks done
gkellogg opened this issue Jan 21, 2023 · 2 comments
Closed
3 tasks done

Various errata from 1.1 #4

gkellogg opened this issue Jan 21, 2023 · 2 comments

Comments

@gkellogg
Copy link
Member

gkellogg commented Jan 21, 2023

From RDF 1.1 Errata:

@gkellogg
Copy link
Member Author

@afs commented on the IRI issue in w3c/EasierRDF#75 (comment).

https://www.w3.org/International/wiki/IRIStatus raises issues about encoding of Internationalized Domain Names and presentation of Bidirectional Language.

The grammar for IRIs in RFC3987 over Unicode codepoint is solid.

RDF 1.1 uses IRIs but it doesn't define them, nor create them, encode or decode them. To some extent, it's garbage-in-garbage-out like any other data. The unicode string must conform to RFC3987 grammar and what it refers is consistent between the creator and any app receiving the data.

The %XX issues are not specific to IRIs - it applies to URIs as well. %7E for example. RFC 3986 section 2.3 says "don't do that" and add that normalization should put the real character in. There is discussion in RDF spec section 3.2.

Consider making reference informative, and duplicating the important parts in an appendix, which is probably limited to the grammar and maybe normalization.

@gkellogg
Copy link
Member Author

IRI Terminology issues now in #15.

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

1 participant