Skip to content

add intro, emphasizing why this spec is only a note #9

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

Merged
pchampin merged 2 commits into from
Dec 9, 2025
+14 −5
Merged

add intro, emphasizing why this spec is only a note #9

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5dd08c3
add intro, emphasizing why this spec is only a note
pchampin Dec 4, 2025
883c8d3
Apply suggestions from code review
pchampin Dec 9, 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
19 changes: 14 additions & 5 deletions spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,19 @@

<section id="introduction">
<h2>Introduction</h2>
<p class=issue>
TODO write a nice intro
<p>
RDF 1.2 [[RDF12-CONCEPTS]] defines two classes of conformance, namely <i>RDF 1.2 Full</i> and <i>RDF 1.2 Basic</i>,
which can also be understood as two variants of the RDF 1.2 syntax.
More specifically, RDF 1.2 Basic is the subset of RDF 1.2 where no [=triple term=] is used.
This raises a challenge when Basic and Full implementations need to interoperate.
</p>

<p>
This specification aims to provide guidance to solve these interoperability challenges.
Note that the methods and tools provided here are not normative,
as they are not meant to be the only and authoritative way to achieve interoperability across heterogeneous implementations.
As pointed out in the <a data-cite="RDF12-CONCEPTS#conformance">Conformance section of RDF 1.2 Concepts</a>,
different strategies are acceptable, depending on the context.
</p>
</section>

Expand All @@ -59,14 +70,12 @@ <h2>Notation and Terminology</h2>
<dfn data-cite="RDF12-CONCEPTS#dfn-reifier">reifier</dfn>,
<dfn data-cite="RDF12-CONCEPTS#dfn-subject">subject</dfn>,
<dfn data-cite="RDF12-CONCEPTS#dfn-triple">triple</dfn>,
<dfn data-cite="RDF12-CONCEPTS#dfn-triple term">triple term</dfn>.
<dfn data-cite="RDF12-CONCEPTS#dfn-triple-term">triple term</dfn>.
</section>

<section id="section-basic-full-interop">
<h2>Interoperability between RDF [=Basic=] and RDF [=Full=]</h2>

<p class=issue>Should we make this section normative?</p>

<p>This section provides transformations between [=Full=] [=RDF graphs=] (respectively, [=RDF datasets=]) and [=Basic=] [=RDF graphs=] (respectively, [=RDF datasets=]),
to provide some level of interoperability between the different classes of <a data-cite="RDF12-CONCEPTS#conformance">Conformance</a>.

Expand Down
Loading