RDF Reference IRI #255
Open
RDF Reference IRI #255
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
niklasl
reviewed
Oct 23, 2025
| resource regardless of where the IRI reference is used. | ||
| [[RFC3987]] defines a syntax that can express | ||
| IRIs which do not meet the requirement of being a global reference. | ||
| URI schemes add addition requirements; for example, the |
There was a problem hiding this comment.
Suggested change
| URI schemes add addition requirements; for example, the | |
| URI schemes add additional requirements; for example, the |
There was a problem hiding this comment.
Suggested change
| URI schemes add addition requirements; for example, the | |
| Some URI schemes add additional requirements; for example, the |
hartig
reviewed
Oct 23, 2025
| resource regardless of where the IRI reference is used. | ||
| [[RFC3987]] defines a syntax that can express | ||
| IRIs which do not meet the requirement of being a global reference. | ||
| URI schemes add addition requirements; for example, the |
There was a problem hiding this comment.
Suggested change
| URI schemes add addition requirements; for example, the | |
| URI schemes add further requirements; for example, the |
| </p> | ||
| <p> | ||
| An <dfn data-lt="RDF reference">RDF Reference IRI</dfn>, | ||
| sometimes just <a>RDF Reference</a>, |
There was a problem hiding this comment.
Suggested change
| sometimes just <a>RDF Reference</a>, | |
| sometimes just called<a>RDF Reference</a>, |
There was a problem hiding this comment.
Suggested change
| sometimes just <a>RDF Reference</a>, | |
| sometimes just called <a>RDF Reference</a>, |
| <section id="reference-iris" class="informative"> | ||
| <h4>RDF Reference IRIs</h4> | ||
| <p> | ||
| This section is advice to data publishers. |
There was a problem hiding this comment.
Suggested change
| This section is advice to data publishers. | |
| This section provides advice to data publishers. |
| This section is advice to data publishers. | ||
| </p> | ||
| <p> | ||
| <a>IRIs</a> are used to denote <a>resources</a> and should identify the same |
There was a problem hiding this comment.
Suggested change
| <a>IRIs</a> are used to denote <a>resources</a> and should identify the same | |
| <a>IRIs</a> are used to denote <a>resources</a>, and each IRI should identify the same |
There was a problem hiding this comment.
Suggested change
| <a>IRIs</a> are used to denote <a>resources</a> and should identify the same | |
| <a>IRIs</a> are used to denote <a>resources</a>, and each IRI should always identify the same |
| </p> | ||
| <p> | ||
| <a>IRIs</a> are used to denote <a>resources</a> and should identify the same | ||
| resource regardless of where the IRI reference is used. |
There was a problem hiding this comment.
Suggested change
| resource regardless of where the IRI reference is used. | |
| resource regardless of where that IRI is used. |
| <p> | ||
| <a>IRIs</a> are used to denote <a>resources</a> and should identify the same | ||
| resource regardless of where the IRI reference is used. | ||
| [[RFC3987]] defines a syntax that can express |
There was a problem hiding this comment.
Suggested change
| [[RFC3987]] defines a syntax that can express | |
| Yet, the syntax for IRIs, as defined by [[RFC3987]], can express |
There was a problem hiding this comment.
Suggested change
| [[RFC3987]] defines a syntax that can express | |
| Note that the general syntax for IRIs, defined by [[RFC3987]], can express |
| <a data-cite="rfc7230#http-URI">`http-URI`</a>, which | ||
| requires the presence of a non-empty host name, and, as a consequence, | ||
| the path component will start with `/`. | ||
| The [[RFC3987]] syntax permits `http:abcd` and `http:///abcd` |
There was a problem hiding this comment.
Suggested change
| The [[RFC3987]] syntax permits `http:abcd` and `http:///abcd` | |
| The [[RFC3987]] syntax permits IRI such as `http:abcd` and `http:///abcd`, |
There was a problem hiding this comment.
Suggested change
| The [[RFC3987]] syntax permits `http:abcd` and `http:///abcd` | |
| The [[RFC3987]] syntax permits IRIs such as `http:abcd` and `http:///abcd`, |
| publishing location. | ||
| Relative IRI references must be | ||
| <dfn id="dfn-relative-iri" data-lt="relative iri reference">relative IRI references</dfn> | ||
| (production `irelative-ref` in the <a href="#iri-abnf">IRI Grammar</a>) |
There was a problem hiding this comment.
Suggested change
| (production `irelative-ref` in the <a href="#iri-abnf">IRI Grammar</a>) | |
| (see the `irelative-ref` production in the <a href="#iri-abnf">IRI Grammar</a>) |
TallTed
reviewed
Oct 24, 2025
| requires the presence of a non-empty host name, and, as a consequence, | ||
| the path component will start with `/`. | ||
| The [[RFC3987]] syntax permits `http:abcd` and `http:///abcd` | ||
| which do not meet the HTTP URI scheme. |
There was a problem hiding this comment.
Suggested change
| which do not meet the HTTP URI scheme. | |
| but these are invalid, because they do not satisfy the HTTP URI scheme definition. |
TallTed
reviewed
Oct 24, 2025
Comment on lines
+1046
to
+1053
| <b>Reference Resolution:</b> | ||
| An <a>RDF Reference IRI</a> is unchanged by | ||
| <a data-cite="RFC3986#section-5">reference resolution</a>. | ||
| The <a data-cite="RFC3986#section-3.3">path component</a> | ||
| starts with a `/` character and does not contain `.` or `..` segments. | ||
| </p> | ||
| <p> | ||
| <strong>Relative IRI references:</strong> |
There was a problem hiding this comment.
It seems like Reference Resolution: should have the same semantic importance and styling as Relative IRI references:, so either both should be <b> or both should be <strong>. I think the latter is probably better, so that's my suggestion here.
Suggested change
| <b>Reference Resolution:</b> | |
| An <a>RDF Reference IRI</a> is unchanged by | |
| <a data-cite="RFC3986#section-5">reference resolution</a>. | |
| The <a data-cite="RFC3986#section-3.3">path component</a> | |
| starts with a `/` character and does not contain `.` or `..` segments. | |
| </p> | |
| <p> | |
| <strong>Relative IRI references:</strong> | |
| <strong>Reference Resolution:</strong> | |
| An <a>RDF Reference IRI</a> is unchanged by | |
| <a data-cite="RFC3986#section-5">reference resolution</a>. | |
| The <a data-cite="RFC3986#section-3.3">path component</a> | |
| starts with a `/` character and does not contain `.` or `..` segments. | |
| </p> | |
| <p> | |
| <strong>Relative IRI references:</strong> |
TallTed
reviewed
Oct 24, 2025
Comment on lines
+1058
to
+1059
| as a convenient shorthand that allows authoring of documents independently from their final | ||
| publishing location. Relative IRI references must be |
There was a problem hiding this comment.
Suggested change
| as a convenient shorthand that allows authoring of documents independently from their final | |
| publishing location. Relative IRI references must be | |
| as a convenient shorthand that allows RDF documents to be authored without knowing | |
| their final publishing location. Relative IRI references must be |
TallTed
reviewed
Oct 24, 2025
| Implementations are encouraged to follow the scheme-specific rules of | ||
| the common schemes, such as the | ||
| <a data-cite="RFC7230#section-2.7.1">scheme rules for HTTP/HTTPS</a> and the | ||
| <a data-cite="RFC7230#section-2.7">scheme rules for HTTP/HTTPS</a> and the |
There was a problem hiding this comment.
Suggested change
| <a data-cite="RFC7230#section-2.7">scheme rules for HTTP/HTTPS</a> and the | |
| scheme rules for <a data-cite="RFC7230#section-2.7">HTTP/HTTPS</a> and the |
pchampin
approved these changes
Oct 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This closes #223.
This closes #169 by referring to the
irelative-iriproduction of the IRI grammar.Add an informative section about minting IRIs, with defined terminology
RDF Reference IRIfor IRIs suitable for use in published RDF. The basic syntax of IRIs (RFC3986/7) is for other uses of IRIs and is too broad (e.g.http:abcd).The section is "informative" because advice can not be checked or enforced when consuming published RDF. For example, the data consumer can not be assumed to know URI scheme rules.
Changes are in section 3.3.
Preview | Diff