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

Jump to bottom

Specify version & state test suites for conformance #141

Merged
merged 2 commits into from
Apr 15, 2024
Merged

Specify version & state test suites for conformance #141

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
91851db
Specify version & state test suites for conformance
anatoly-scherbakov Apr 14, 2024
0d5cb61
Update spec/index.html
anatoly-scherbakov Apr 15, 2024
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
39 changes: 38 additions & 1 deletion spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -579,7 +579,7 @@ <h2>Namespace Prefixes</h2>
A <a>YAML-LD document</a> complies with
the <a>YAML-LD Basic profile</a> of this specification
if it follows the normative statements from this specification
and can be transformed into a JSON-LD representation,
and can be transformed into a [[JSON-LD11]] representation,
then back to a conforming YAML-LD document,
without loss of semantic information.
</p>
Expand All @@ -588,6 +588,43 @@ <h2>Namespace Prefixes</h2>
For convenience, normative statements for documents are often phrased
as statements on the properties of the document.
</p>

<section id="v11">
<h2>JSON-LD Version</h2>

<p>YAML-LD supports JSON-LD versions starting from 1.1 [[JSON-LD11]].</p>
anatoly-scherbakov marked this conversation as resolved.
Show resolved Hide resolved
</section>

<section id="testing">
<h2>Test Suites</h2>

<p>To be conformant, an implementation MUST satisfy all test cases from the following test suites:</p>

<ul>
<li>
<a href="https://json-ld.github.io/yaml-ld/tests/">YAML-LD tests</a>;
</li>
<li>
<a href="https://w3c.github.io/json-ld-api/tests/">JSON-LD API tests</a>;
</li>
<li>
<a href="https://w3c.github.io/json-ld-framing/tests/">JSON-LD Framing tests</a>,
</li>
</ul>

<p>...with the exclusion of the test cases where:</p>

<ul>
<li>
<a href="#dom-jsonldoptions-processingmode">processingMode</a> option is provided and set to `json-ld-1.0`.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm, the intention here is to specify which test cases to ignore, these should be 1.0 test cases... or am I confusing something? @gkellogg

Copy link
Member

Choose a reason for hiding this comment

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

Indeed, I didn't read closely enough. I withdraw my suggestion.

</li>
</ul>

<p class="note">
Since YAML is a superset of JSON, testing a YAML-LD against
tests cases from JSON-LD test suites should be trivial.
</p>
</section>
</section>

<section id="basic-concepts" class="informative">
Expand Down
Loading