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

address #630 #638

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

address #630 #638

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5257c91
address #630
pchampin Feb 27, 2025
0321fbe
fix 'changed' markup
pchampin Feb 27, 2025
74e7153
Update common/terms.html
pchampin Feb 28, 2025
913511d
turn into a candidate addition
pchampin Feb 28, 2025
b037802
Update index.html
pchampin Mar 12, 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
2 changes: 2 additions & 0 deletions common/terms.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -383,6 +383,8 @@
Its value is either a string (<dfn data-cite="JSON-LD11#dfn-simple-term-definition" data-lt="simple term definition|simple term" data-lt-noDefault>simple term definition</dfn>),
expanding to an <a>IRI</a>,
or a map (<a>expanded term definition</a>).
<ins cite="#change_api_638"><br/>
For <a data-cite="JSON-LD11-API#context-processing-algorithms">context processing</a>, <a>term definition</a> values are converted internally to a dedicated data structure that is easier to process.</ins>
Comment on lines +386 to +387
Copy link
Member

Choose a reason for hiding this comment

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

The problem with this is that that will show up in syntax and framing, as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes, that's why I named it change_api_638 insteal of change_8. That way, we can add a change marker in the other specs without an ID clash.

Copy link
Member

Choose a reason for hiding this comment

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

We'll need issues for those other specs to have their own version of this update.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good point. This is now done:

</dd>
<dt class="changed"><dfn data-cite="JSON-LD11#dfn-type-map">type map</dfn></dt><dd class="changed">
A <a>type map</a> is a <a>map</a> value of a <a>term</a>
Expand Down
15 changes: 13 additions & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1071,10 +1071,19 @@ <h2>RDF Serialization/Deserialization</h2>
using information provided by the <a>active context</a>. This
section describes how to produce an <a>active context</a>.</p>

<div id="change_api_638" class="candidate correction">
<span class="marker">Candidate Correction 8</span>
<p>Change the type of <a>term definition</a> from <a>array</a> to <a>map</a> in <a>active context</a>,
to be consistent with the way it is used in the algorithms.
Clarify the notion <a>term definition</a>.
For more information, refer to <a href="https://github.com/w3c/json-ld-api/issues/630">issue 630</a>.
</p>
</div>

<p>The <a>active context</a> consists of:</p>
<ul>
<li>the active <a>term definitions</a> which specify how
keys and values have to be interpreted (<a>array</a> of <a>term definitions</a>),</li>
keys and values have to be interpreted (<del cite="#change_api_638"><a>array</a></del><ins cite="#change_api_638"><a>map</a></ins> of <a>term definitions</a>),</li>
<li>the current <dfn data-lt="context-base-iri" data-lt-noDefault>base IRI</dfn> (<a>IRI</a>),</li>
<li class="changed">the <dfn>original base URL</dfn> (<a>IRI</a>),</li>
<li class="changed">an <dfn data-lt="context-inverse" data-lt-noDefault>inverse context</dfn> (<a>inverse context</a>),</li>
Expand All @@ -1085,7 +1094,7 @@ <h2>RDF Serialization/Deserialization</h2>
used when a non-propagated <a>context</a> is defined.</li>
</ul>

<p>Each <a>term definition</a> consists of:</p>
<p>Each <a>term definition</a><ins cite="#change_api_638">'s value</ins> consists of:</p>
<ul>
<li>an <dfn>IRI mapping</dfn> (<a>IRI</a>),</li>
<li class="changed">a <dfn>prefix flag</dfn> (<a>boolean</a>),</li>
Expand Down Expand Up @@ -7092,6 +7101,8 @@ <h2>Change log</h2>
<li>2024-10-31: Abstract JSON serialization from WebIDL interfaces to allow
for alternative formats,
as described in <a href="#change_7">Candidate Correction 7</a></li>
<li>2025-02-28: Clarifiy language about <a>term definitions</a>,
as described in <a href="#change_api_638">Candidate Correction 8</a></li>
</ul>
</details>

Expand Down
Loading