Skip to content

Add version announcement section #187

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

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

Add version announcement section #187

Changes from 3 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
fce3d52
Add version announcement section
rubensworks Apr 15, 2025
e770006
Apply suggestions from code review
rubensworks Apr 16, 2025
dbe48ae
Remove normative terms in version announcement
rubensworks Apr 16, 2025
5b9423e
Apply suggestions from code review
rubensworks Apr 16, 2025
903119c
Make indentation consistent
rubensworks Apr 16, 2025
c6ad433
Move version announcement after RDF Documents and Syntaxes
rubensworks Apr 16, 2025
bb585c5
Update spec/index.html
rubensworks Apr 18, 2025
e98c438
Update spec/index.html
rubensworks Apr 18, 2025
a4324dc
Fix indentation
rubensworks Apr 18, 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
35 changes: 35 additions & 0 deletions spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,6 +363,39 @@ <h3>Triple Terms and Reification</h3>

<p>Note that a <a>triple term</a> may also have another <a>triple term</a> as an <a>object</a>.</p>
</section>

<section id="section-version-announcement">
<h3>RDF Version Announcement</h3>

<p>To allow RDF parsers to error or warn about unsupported RDF versions as early as possible,
RDF serialization formats are expected to allow a version to be specified,
via either the HTTP Content-Type header,
a version announcement in the format-specific syntax,
or both.</p>

<p>If the version is announced in both the Content-Type header and in the syntax, they are expected to be equal.</p>

<p>To retain compability that is as broad as possible with older parsers,
only RDF documents that make use of RDF 1.2-specific functionality
are encouraged to announce their version (i.e., RDF documents that do not make use
of RDF 1.2-specific functionality SHOULD NOT announce their version).</p>

<p>To announce the version in the HTTP responses using the Content-Type header, the <code>version</code> parameter is expected to be used.</p>

<pre class="box http">HTTP/1.1 200 OK
Content-Type: text/turtle; version=1.2
Location: http://example.com/document.ttl
</pre>

<p>When requesting an RDF document from an HTTP server, the <code>version</code> parameter
can be used during <a data-cite="webarch#frag-coneg">content negotiation</a> [[WEBARCH]]
by including it in the <code>Accept</code> request header.</p>

<pre class="box http">GET /document.ttl HTTP/1.1
Host: example.com
Accept: text/turtle; version=1.2
</pre>
</section>

<section id="change-over-time">
<h3>RDF and Change over Time</h3>
Expand Down Expand Up @@ -2279,6 +2312,8 @@ <h3>Acknowledgments for RDF 1.2</h3>
<h2>Changes between RDF 1.1 and RDF 1.2</h2>

<ul>
<li>Added <a href="#section-version-announcement"class="sectionRef"></a>
for announcing RDF versions in RDF documents via the HTTP Content-Type header and/or syntax.</li>
<li>Added <a href="#section-classic-full-interop" class="sectionRef"></a>
for informative mappings between RDF [=Full=] and RDF [=Classic=].</li>
<li>Added <a href="#section-dataset-quad" class="sectionRef"></a>
Expand Down
Loading