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

JSON-LD compatible profile #70

Closed
wants to merge 4 commits into from
Closed

JSON-LD compatible profile #70

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
02801fa
Update index.html
rob-metalinkage Aug 3, 2022
d460566
Update spec/index.html
gkellogg Aug 15, 2022
596fa31
Apply suggestions from code review
gkellogg Aug 17, 2022
5903ce7
Merge branch 'main' into main
gkellogg Aug 17, 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
11 changes: 10 additions & 1 deletion spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -395,6 +395,13 @@ <h2>Namespace Prefixes</h2>
can be interpreted as [[JSON-LD]] after transformation into the <a>internal representation</a>.
For convenience, normative
statements for documents are often phrased as statements on the properties of the document.</p>

<p>A <a>YAML-LD document</a> complies with the YAML-LD-JSON profile of this specification if it follows
the normative statements from this specification and can be transformed into a JSON-LD
representation, then back to a conforming YAML-LD document, without loss of semantic information.
</p>


</section>

<section id="basic-concepts" class="informative">
Expand Down Expand Up @@ -429,11 +436,13 @@ <h2>Basic Concepts</h2>
<p>
The first goal of this specification is to allow a JSON-LD document to be
processed and serialized into YAML, and then back into JSON-LD, without
losing any information.
losing any information.

This is always possible, because a YAML representation graph can always represent
gkellogg marked this conversation as resolved.
Show resolved Hide resolved
a tree, because JSON data types are a subset of YAML's, and because
gkellogg marked this conversation as resolved.
Show resolved Hide resolved
JSON encoding is UTF-8.

The subset of YAML-LD which supports serialisation of JSON-LD documents is defined as the <em>YAML-LD-JSON profile</em> of YAML-LD.
gkellogg marked this conversation as resolved.
Show resolved Hide resolved
</p>

<p>Example: The JSON-LD document below</p>
Expand Down