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

feat: uses IRI rather than URI or URL #67

Closed
wants to merge 3 commits into from
Closed

feat: uses IRI rather than URI or URL #67

wants to merge 3 commits into from

Conversation

jacoscaz
Copy link
Collaborator

@jacoscaz jacoscaz commented Mar 18, 2024

This PR closes long-standing #10 by replacing usages of "URI" with "IRI" and expanding on the relationship between IRIs, URIs and URLs, referencing and deferring to higher-level specs.

Though theoretically a breaking change, in practice this PR changes little to nothing. Setting the deadline for review in two weeks, on 2024-04-01.

Do not bother reviewing the spec/identity/index.html as that's automatically updated by our current CI setup based on the contents of spec/identity/index.bs. We'll sort this out in a separate issue / PR.

EDIT: links to the rendered files:

@jacoscaz jacoscaz linked an issue Mar 18, 2024 that may be closed by this pull request
spec/identity/index.html Outdated Show resolved Hide resolved
spec/identity/index.html Outdated Show resolved Hide resolved
spec/identity/index.html Outdated Show resolved Hide resolved
spec/identity/index.html Outdated Show resolved Hide resolved
spec/identity/index.html Outdated Show resolved Hide resolved
spec/identity/index.html Outdated Show resolved Hide resolved
@jacoscaz
Copy link
Collaborator Author

Thank you @TallTed for reviewing!

the respective [=WebID Profile Document=].
A WebID is an IRI with a HTTP(S) scheme that refers to an Agent (Person,
Organization, Group, Device, etc.); a description of the Agent named by the
WebID can be found in the respective [=WebID Profile Document=].
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably just a chicken-or-the-egg thing, so just noting that this will need to change once this other PR is merged: #69:

Suggested change
WebID can be found in the respective [=WebID Profile Document=].
WebID can be found in the respective [=WebID Document=].

which itself indicates that it describes the Agent named by the WebID.
:: An identifier in the form of an IRI with a HTTP(S) scheme that
unambiguously names an Agent and, when dereferenced, always leads to a
[=WebID Profile Document=] which itself indicates that it describes the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably just a chicken-or-the-egg thing, so just noting that this will need to change once this other PR is merged: #69:

Suggested change
[=WebID Profile Document=] which itself indicates that it describes the
[=WebID Document=] which itself indicates that it describes the

Copy link

@pmcb55 pmcb55 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For what it's worth(!), I'm happy to approve this PR (as I assume PR #69 will handle the 'WebID Document' renaming comments).

@melvincarvalho
Copy link

FWIW still have security concerns regarding phishing attacks, with characters that look similar, regarding this change.

@pmcb55
Copy link

pmcb55 commented Mar 27, 2024

FWIW still have security concerns regarding phishing attacks, with characters that look similar, regarding this change.

Yep @melvincarvalho, I think that's well understood, and clearly articulated even on the simple and accessible (i.e., readable for anyone, techie or not) Wikipedia page: https://en.wikipedia.org/wiki/Internationalized_Resource_Identifier (i.e., there's no need to read an entire spec for that to be made clear to people).

But I'm sure you'd agree with the entire RDF community for these past 20+ years that that understandable concern doesn't outweigh the clear advantages for our billions of non-Latin-alphabet-aware friends on the planet, as also clearly articulated on that Wikipedia page, i.e.: "mostly, it makes it easier for users who are unfamiliar with the Latin (A–Z) alphabet".

@melvincarvalho
Copy link

But I'm sure you'd agree with the entire RDF community for these past 20+ years that that understandable concern doesn't outweigh the clear advantages for our billions of non-Latin-alphabet-aware friends on the planet, as also clearly articulated on that Wikipedia page, i.e.: "mostly, it makes it easier for users who are unfamiliar with the Latin (A–Z) alphabet".

This is the wrong issue for that conversation, as it's off topic. WebID is more about your username on the web. That has different considerations from general RDF, and a higher interop burden. In theory a WebID would never be seen by the end user, except for URI verification, but a foaf name could have lots of characters. In any case, this is the wrong thread for such a debate. Nevertheless interesting, thanks for the comment!

@jacoscaz jacoscaz closed this by deleting the head repository May 28, 2024
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

Successfully merging this pull request may close these issues.

Switch from URI to IRI terminology in WebID spec
4 participants