-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
rubensworks
wants to merge
9
commits into
main
Choose a base branch
from
feature/version-announcement
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+41
−0
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
fce3d52
Add version announcement section
rubensworks e770006
Apply suggestions from code review
rubensworks dbe48ae
Remove normative terms in version announcement
rubensworks 5b9423e
Apply suggestions from code review
rubensworks 903119c
Make indentation consistent
rubensworks c6ad433
Move version announcement after RDF Documents and Syntaxes
rubensworks bb585c5
Update spec/index.html
rubensworks e98c438
Update spec/index.html
rubensworks a4324dc
Fix indentation
rubensworks File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -504,6 +504,45 @@ <h3>RDF Documents and Syntaxes</h3> | |||||||||||||||||||
effect on the convenience of working with the <a>RDF document</a>, | ||||||||||||||||||||
they are not significant for its meaning.</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 a media-type parameter, | ||||||||||||||||||||
a version announcement in a format-specific syntax, | ||||||||||||||||||||
or both.</p> | ||||||||||||||||||||
|
||||||||||||||||||||
<p>When the version is indicated both in a media-type parameter and in syntax, | ||||||||||||||||||||
they are expected to be the same. | ||||||||||||||||||||
If they differ, | ||||||||||||||||||||
parsers use the version from the media-type parameter and might emit a warning about the mismatch.</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., for RDF documents that do not make use | ||||||||||||||||||||
of RDF 1.2-specific functionality it is discouraged to announce a 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, | ||||||||||||||||||||
as illustrated in the following example response.</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, | ||||||||||||||||||||
as illustrated in the following example request.</p> | ||||||||||||||||||||
Comment on lines
+536
to
+539
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
<pre class="box http">GET /document.ttl HTTP/1.1 | ||||||||||||||||||||
Host: example.com | ||||||||||||||||||||
Accept: text/turtle; version=1.2 | ||||||||||||||||||||
</pre> | ||||||||||||||||||||
</section> | ||||||||||||||||||||
</section> | ||||||||||||||||||||
|
||||||||||||||||||||
<section id="conformance"> | ||||||||||||||||||||
|
@@ -2279,6 +2318,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> | ||||||||||||||||||||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.