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

Add an explanation on step 2.1 of the canonicalization algorithm #52

Merged
merged 3 commits into from
Dec 6, 2022
Merged

Add an explanation on step 2.1 of the canonicalization algorithm #52

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a711fcf
Add an explanation on step 2.1 of the canonicalization algorithm
gkellogg Dec 5, 2022
515159d
Apply suggestions from code review
gkellogg Dec 5, 2022
5845897
Update spec/index.html
gkellogg Dec 6, 2022
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
38 changes: 27 additions & 11 deletions spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -497,7 +497,6 @@ <h2>Canonicalization Algorithm</h2>
<div class="issue" data-number="8"></div>
<div class="issue" data-number="10"></div>
<div class="issue" data-number="11"></div>
<div class="issue" data-number="15"></div>
<div class="issue" data-number="16"></div>
<div class="issue" data-number="38"></div>
<div class="issue" data-number="41"></div>
Expand Down Expand Up @@ -903,12 +902,24 @@ <h3>Algorithm</h3>
<a>blank node identifier</a> <var>identifier</var>
in the <a>blank node to quads map</a>,
creating a new entry if necessary.
<div class="issue" data-number="15">
It seems that <var>Q</var> must be normalized,
so that literals with different syntactic representations
but the same semantic representations are merged,
and that two graphs differing in the syntactic representation
of a literal will produce the same set of blank node identifiers.</div>
<details>
<summary>Explanation</summary>
<p>This establishes the <a>blank node to quads map</a>,
relating each <a>blank node</a> with the set of <a>quads</a>
of which it is a component.</p>
<p class="note">
<a data-cite="RDF11-CONCEPTS#dfn-literal">Literal</a> components of
<a>quads</a> are not subject to any normalization.
As noted in
<a data-cite="RDF11-CONCEPTS#section-Graph-Literal">Section 3.3</a>
of [[RDF11-CONCEPTS]],
<a data-cite="RDF11-CONCEPTS#dfn-literal-term-equality">literal term equality</a>
is based on the
<a data-cite="RDF11-CONCEPTS#dfn-lexical-form">lexical form</a>,
rather than the <a data-cite="RDF11-CONCEPTS#dfn-literal-value">literal value</a>,
so two literals `"01"^^xs:integer` and `"1"^^xs:integer` are treated as distinct resources.
</p>
</details>
</li>
</ol>
</li>
Expand Down Expand Up @@ -1351,10 +1362,6 @@ <h3>Algorithm</h3>
</ol>
</li>
</ol>
<p class="issue" data-number="15">
Note potential need to normalize literals to their
canonical representation here as well,
if not done on the original <a>input dataset</a>.</p>
</li>
</ol>
</li>
Expand Down Expand Up @@ -2201,6 +2208,15 @@ <h2>Changes since the First Public Working Draft of 24 November 2022</h2>
be a citation from [[N-Quads]], when it is updated.
<a>Canonical n-quads form</a> is used in <a href="#hash-1d-quads" class="sectionRef"></a>.
</li>

<li>Removed issue marker for
<a href="https://github.com/w3c/rdf-canon/issues/15">Issue 15</a>
in <a href="#canon-algorithm" class="sectionRef"></a>,
adding a note that
<a data-cite="RDF11-CONCEPTS#dfn-literal">literal</a>
components of <a>quads</a> are not normalized,
and two literals with different syntactic representations
remain distinct resources.</li>
</ul>
</section>

Expand Down