On 24/11/2023 10:40, Marco Neumann wrote:
The URI syntax is defined by the Internet Engineering Task Force (IETF) in
RFC 3986.
W3C RDF is just a rule-taker here ;)
https://datatracker.ietf.org/doc/html/rfc3986
We've drafted a non-normative section:
https://www.w3.org/TR/rdf12-concepts/#iri-abnf
which is all the RFCs we could find and adopting the current state of
terminology.
Nowadays, URI and IRI are interchangeable. Only use in HTTP requests
worries about ASCII vs UTF-8 and then only in old software. Use a
toolkit and it'll sort it out.
Only the URI scheme name is restricted to A-Z.
Andy
Marco
On Fri, Nov 24, 2023 at 10:36 AM Laura Morales <laure...@mail.com> wrote:
What do you mean by human-readable here? For large technical systems it's
simply not feasible to encode meaning into the URI and I might even
consider it an anti-pattern.
This is my problem. I do NOT want to encode any meaning into URLs, but I
do want them to be human readable simply because I) properties are URLs
too, 2) they can be used online, and 3) they are simpler to work with, for
example editing in a Turtle file or writing a query.
:alice :knows :bob vs :dsa7hdsahdsa782j :d93ifg75jgueeywu
:s93oeirugj290sjf
I can avoid [ entirely, but it rises the question of what other characters
I MUST avoid.
{} {}
You can use () but hierarchical names are better.
Be careful about ':' because it can't be in the first segment of a path
of a relative URI (it looks like a scheme name).
Andy
