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.

Sign up for GitHub

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

GH-135: Follow URI scheme rules #136

Merged
merged 3 commits into from
Jan 29, 2025
Merged

GH-135: Follow URI scheme rules #136

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c381419
GH-135: Follow URI scheme rules
afs Jan 17, 2025
9eff5b3
Add that IRIs must not be relative references
afs Jan 17, 2025
8225f18
Update note from review comments
afs Jan 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -588,9 +588,12 @@ <h3>IRIs</h3>
is a <a>string</a> that conforms to the syntax
defined in RFC 3987 [[!RFC3987]].</p>

<p>IRIs in the RDF abstract syntax MUST be <a data-cite="RFC3986#section-5">resolved</a>
per [[RFC3986]],
and MAY contain a fragment identifier.</p>
<p>An IRI in the RDF abstract syntax
MUST be <a data-cite="RFC3986#section-5">resolved</a> per [[RFC3986]] and
MUST NOT be a <a data-cite="RFC3986#section-4.2">relative reference</a>.
An IRI MAY contain a <a data-cite="RFC3986#section-3.5">fragment identifier</a>.
An IRI SHOULD follow rules defined by the <a data-cite="RFC3986#section-3.1">IRI scheme</a>.
</p>

<p><dfn>IRI equality</dfn>:
Two IRIs are the same if and only if they consist of the same sequence of
Expand Down Expand Up @@ -644,6 +647,15 @@ <h3>IRIs</h3>
if a <a data-cite="rfc3986#section-5.1">base IRI
can be established</a> [[RFC3986]].</p>

<p><strong>URI Schemes:</strong>
Implementations are encouraged to enforce 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="did-core#identifier">DID syntax</a>.
Implementations ignore URI scheme rules
afs marked this conversation as resolved.
Show resolved Hide resolved
for schemes they do not recognize.
</p>

<p><strong>IRI normalization:</strong>
Interoperability problems can be avoided by minting
only IRIs that are normalized according to
Expand Down
Loading