Specifications and Profiles to which the content of resource representations may conform embody their own notions of conformance, which are out of scope for this specification.
-
- This specification includes several functional profiles of it that may be conformed to by systems claiming to implement a form of this specification.
- These profiles, given in the table below, are identified by URIs and conformance to them by Internet resources should be indicated as per this document (use of
- Content-Profile HTTP header).
-
- The namespace prefix for the functional profiles used in , the table below, is: -
-cnpr → http://www.w3.org/ns/dx/conneg/profile/| URI | -Name | -Description | -Usage Note | -
|---|---|---|---|
cnpr:http |
- HTTP Headers Functional Profile | -For conformance with the functional profile presented in . | -To be used if a resource conforms to the HTTP Headers Functional Profile | -
cnpr:qsa |
- QSA Functional Profile | -For conformance with the functional profile presented in . | -
- To be used if a resource conforms to the QSA Functional Profile using the Query String Arguments _profile and _mediatype as per the recommendations
- in .
- |
-
cnpr:qsa-alt |
- QSA Alternate Keywords Functional Profile | -For conformance with the functional profile presented in . | -
- To be used if a resource conforms to the QSA Functional Profile but uses alternate keywords for the Query String Arguments _profile and
- _mediatype, as allowed by the recommendations in .
- |
-
cp:rrd |
- Resource Representation Description | -For conformance with . | -- To be used if a resource representation is able to indicate which profile(s) it conforms to, in its appropriate functional profile, as per the abstract specification in - . - | -
- If a system wishes to show conformance to this specification, conformance to at least one of the profiles listed in MUST be indicated. -
-
- The namespace used for the above profiles, http://www.w3.org/ns/dx/conneg/profile/, is part of the Dataset Exchange Working Group's reserved W3C namespace,
- http://www.w3.org/ns/dx/, which is provisioned for all namespace requirements to do with issues addressed by that Working Group. The /profile/ path segment
- indicates a register of profile objects which currently contains just the 4 instances above from .
-
- This definition includes what are sometimes called "application profiles", "metadata application - profiles", "data profiles" (when applied to data specifications) or "metadata profiles". - In this document, these are all referred to as just "profiles" and no distinction, in wording, is made - between profiles of different types of specification: data, functional etc. + If the specification profiled is a specialized type of specification, for example a data or a functional + specification, the profile will be of the same sort - a data or functional profile. +
++ This Content Negotiation by Profile specification concerns negotiation for data profiles, and specifies functional profiles for different ways of achieving this. +
+ ++ A data specification that constrains, extends, combines, or provides guidance or explanation about the usage of other data specifications. +
++ This definition includes what are sometimes called "application profiles", "metadata profiles" or "metadata application profiles". +
+Source: deliberations of the DXWG.
++ A functional specification that constrains, extends, combines, or provides guidance or explanation about the usage of other functional specifications.
Source: deliberations of the DXWG.
- Implementations of this Abstract Model for different environments are called Functional Profiles and to be a valid functional profile they MUST implement these Abstract Model functions. How they do this will be + Implementations of this Abstract Model for different environments are called Functional Profiles and to be a valid functional profile they MUST implement these Abstract Model functions. How they do this will be environment-specific.
@@ -810,26 +745,101 @@
- This section describes profiles of this specification's Abstract Model which are implementations of it
- in different environments; they are profiles and may be referred to as "functional profiles". These profiles are
+
+ This section describes functional profiles of this specification's Abstract Model which are implementations of it
+ in different environments. These functional profiles are
formally identified in and are to be used as conformance targets for specific
implementations of systems within different environments wishing to conform to this specification.
-
- This document provides functional profiles for two environments - HTTP & human browser (Query String
- Argument functionality) only. For the human browser environment, two functional profiles are presented.
- Further functional profiles of this specification MAY be implemented either for other environments and or even for
- constrained scenarios within these environments and implementers are encouraged to do this by further profiling this
- specification.
-
+
+ This document provides functional profiles for two environments - HTTP & human browser (Query String
+ Argument functionality) only. For the human browser environment, two functional profiles are presented.
+ Further functional profiles of this specification MAY be implemented either for other environments and or even for
+ constrained scenarios within these environments and implementers are encouraged to do this by further profiling this
+ specification.
+
Implementers of Content Negotiation by Profile need not ensure systems conform to multiple functional profiles
of this specification. They need only conform to the functional profile(s) relevant to their environment. In some
cases, for example the Query String Argument-relevant human browser environment, there is a choice of more than
one functional profile. Since all functional profiles of this specification themselves must conform to this specification, by
design, conformance to any functional profile guarantees conformance to the specification.
+ This specification defines several functional profiles that may be conformed to by systems.
+ These functional profiles are identified by URIs and given in the table below.
+
+ The namespace prefix for the functional profiles used in , the table below, is:
+
+ If a system wishes to show conformance to this specification, conformance to at least one of the functional profiles listed in MUST be indicated.
+
+ The namespace used for the above functional profiles,
@@ -1900,8 +1910,8 @@
- This specification contains a number of distinct profiles that are identified and described in words in
- . This appendix presents descriptions of these profiles, and the relations
+ This specification contains a number of distinct functional profiles that are identified and described in words in
+ . This appendix presents descriptions of these functional profiles, and the relations
between them, according to the Profiles Vocabulary [[PROF]].
@@ -2165,10 +2175,6 @@
The Alternate Profiles Data Model may be extended to include additional information of use in
content negotiation by profile situations. One obviously useful extension is the inclusion of information about
Functional Profiles of this specification
+ Conformance to Functional Profiles
+
+
+ cnpr → http://www.w3.org/ns/dx/conneg/profile/
+
+
+
+
+
+
+ URI
+ Name
+ Description
+ Usage Note
+
+
+ cnpr:httpHTTP Headers Functional Profile
+ For conformance with the functional profile presented in .
+ To be used if a resource conforms to the HTTP Headers Functional Profile
+
+
+ cnpr:qsaQSA Functional Profile
+ For conformance with the functional profile presented in .
+
+ To be used if a resource conforms to the QSA Functional Profile using the Query String Arguments
+ _profile and _mediatype as per the recommendations
+ in .
+
+
+ cnpr:qsa-altQSA Alternate Keywords Functional Profile
+ For conformance with the functional profile presented in .
+
+ To be used if a resource conforms to the QSA Functional Profile but uses alternate keywords for the Query String Arguments
+ _profile and
+ _mediatype, as allowed by the recommendations in .
+
+
+
+ cp:rrdResource Representation Description
+ For conformance with .
+
+ To be used if a resource representation is able to indicate which profile(s) it conforms to, in its appropriate functional profile, as per the abstract specification in
+ .
+
+ http://www.w3.org/ns/dx/conneg/profile/, is part of the Dataset Exchange Working Group's reserved W3C namespace,
+ http://www.w3.org/ns/dx/, which is provisioned for all namespace requirements to do with issues addressed by that Working Group. The /profile/ path segment
+ indicates a register of profile objects which currently contains just the 4 instances above from .
+ Hypertext Transfer Protocol Headers
Appendices
Profiles of this specification
Implementations
Extensions
-