Skip to content
Permalink
Browse files

removed all references to PROF in normative sections; reinforced that…

… Appendices are non-normative
  • Loading branch information
Nicholas Car
Nicholas Car committed Oct 8, 2019
1 parent 244230c commit fa0bb801fd03d664e6f58e4ffdc6f0898752dc18
Showing with 11 additions and 10 deletions.
  1. +11 −10 conneg-by-ap/index.html
@@ -10,7 +10,7 @@
<section id="abstract">
<h2>Abstract</h2>
<p>
This document describes how Internet clients may negotiate for content provided by servers based on the
This document describes how Internet clients may negotiate for content provided by servers based on the
+ <em>profile</em> to which the content conforms. This is distinct from negotiating by Media Type or Language: a <em>profile</em> may
specify the content of information returned, which may be a subset of the information the responding server has about the requested resource, and may be structured in a specific way to meet interoperability requirements of a community of practice.
</p>
@@ -97,10 +97,11 @@ <h2>Introduction</h2>
<section id="conformance">
<p>
For the purpose of compliance, the normative sections of this document are
<a href="#definitions">Section 3</a>,
<a href="#abstractmodel">Section 6</a>,
<a href="#functional-profiles">Section 7</a> and
<a href="#testsuites">Section 8</a>.
<a href="#definitions"></a>,
<a href="#abstractmodel"></a>,
<a href="#functional-profiles"></a> and
<a href="#testsuites"></a>.
Appendices are non-normative.
</p>
<p class="note">Specifications and Profiles to which the content of resource representations may conform will embody their own definitions of conformance, which are out of scope for this specification.</p>
</section>
@@ -795,7 +796,7 @@ <h3>Conformance to Functional Profiles</h3>
<p>
If a system wishes to show conformance to this specification, conformance to at least one functional profile of
it, such as those listed <a href="#fig-table-profiles"></a> MUST be indicated. <a href="#fig-table-profiles"></a>
is not an exhaustive list of functional profiles of this specification and users MAY instead make other or additional
is not an exhaustive list of functional profiles of this specification and users MAY instead make other or additional
functional profiles for their environments, as described in the previous section.
</p>
<p>
@@ -1040,7 +1041,7 @@ <h4>HTTP Alternate Representations Data Model Implementation</h4>
<td><code>altp:Representation</code></td><td>the <em>link target</em> URI indicates an instance altp:Representation</td>
</tr>
<tr>
<td><code>prof:Profile</code></td><td>a <em>target attribute</em> of <code>profile</code> indicates the URI of an instance of prof:Profile, if present</td>
<td><code>dct:Standard</code></td><td>a <em>target attribute</em> of <code>profile</code> indicates the URI of an instance of dct:Standard, if present</td>
</tr>
<tr>
<td><code>dct:conformsTo</code></td><td>the implicit relation between the <em>link target</em> URI and the <em>target attribute</em> <code>profile</code> URI</td>
@@ -1155,7 +1156,7 @@ <h3>Token mappings</h3>
# The profile URI in the "anchor" element is linked to the token "igsn-r1"

# Further, the relation "type" is used to inform
# that the anchor resource is of type "prof:Profile"
# that the anchor resource is of type "dct:Standard"

Link: &lt;http://www.w3.org/ns/dx/prof/Profile&gt;;
rel="type";
@@ -1262,7 +1263,7 @@ <h4>QSA Functional Profile description</h4>
<div class="note">
Conformance of a system to any one, or perhaps multiple, of these functional profiles may be demonstrated as per
<a href="#conformancetoprofiles"></a>. Note that it is not required that a system, perhaps a server, indicate
conformance to one or more of the functional profiles described in this specification since not all systems will
conformance to one or more of the functional profiles described in this specification since not all systems will
do so. Systems may also show conformance to
functional profiles in multiple ways, such as with annotated entries in a services catalogue.
</div>
@@ -1759,7 +1760,7 @@ <h3>Token</h3>
# The profile URI in the "anchor" element is linked to the token "igsn-r1"

# Further, the relation "type" is used to inform
# that the anchor resource is of type "prof:Profile"
# that the anchor resource is of type "dct:Standard"

Link: &lt;http://www.w3.org/ns/dx/prof/Profile&gt;;
rel="type";

0 comments on commit fa0bb80

Please sign in to comment.
You can’t perform that action at this time.