This section explains how to make a valid claim that a product conforms to
this specification. Anyone may make a claim (e.g., vendors about
their own products, third parties about those products, journalists
about products, etc.). Claims may be published anywhere (e.g., on
the Web or in product documentation). Claimants are solely
responsible for their claims. If the subject of the claim (e.g.,
the software) changes after the date of the claim, the claimant is
responsible for updating the claim. Claimants are expected to
modify or retract a claim if it may be demonstrated that the claim
is not valid. Claimants are encouraged to conform to the most
recent specification available.
There are three classes of products of CC/PP:
- documents (e.g. a web resource)
- producers (e.g. a web client)
- consumers (e.g. a web server)
5.1 CC/PP Document
Documents may exist as resources accessible via a URL, or may be
transmitted as data in a message. A document is CC/PP conformant
when it meets the following criteria:
- The document MUST be valid RDF
serialized in XML, conforming to the RDF Schema in appendix B. See
- The document MUST use valid syntax for namespace declarations.
See section 2.2.
- The profile element MUST contain one or more components. See
- Each component in the profile MUST contain one or more
attributes. See section
- The component names MAY be in rdf:type statements. See
- Components MUST be associated with the CC/PP namespace or some
subclass thereof. See section
- Component names, component types, and attribute names must all
refer to different URIs within a profile. See section 3.
- If a component type is given as an element name and as an
rdf:type element, they MUST refer to the same URI. See section 3.1.
- Default references MUST be valid URLs. See section 3.3.
- Defaults MAY be written as ccpp:defaults or ccpp:Defaults. See
- Defaults MUST be associated with the CC/PP namespace or some
subclass thereof. See section
- Component attributes MAY contain both a default value and a
directly applied value, with the directly applied value taking
precedence. See section 3.3.
- Components MAY contain inline defaults. See section 3.3.
- Components MUST NOT contain both inline and referenced
defaults. See section 3.3.
- Components MAY reference a default document which does not have
an rdf:type. See section 3.3.
- Attributes MAY have sets of values (Bags). See section 220.127.116.11.
- Attributes MAY have sequences of values (Seq). See section 18.104.22.168.
- Attributes MAY have Text values. See section 22.214.171.124.
- Attributes MAY have Integer number values. See section 126.96.36.199.
- Attributes MAY have Rational number values. See section 188.8.131.52.
- A component MUST NOT contain more than one attribute with the
same name. See section 3.2.
- Attributes of the same name MAY be in different components. See
- Profiles MAY use multiple namespaces for attributes. See
5.3 CC/PP Producer
A producer is CC/PP conformant when any CC/PP profile document
generated by the producer is a CC/PP conformant document.
5.4 CC/PP Consumer
A consumer is CC/PP conformant when the consumer accepts any
CC/PP conformant document and extracts appropriate information.
Support for the RDF Schema in appendix B by CC/PP consumers is
There are two categories of conformance for CC/PP consumers,
depending on the treatment of invalid profiles:
- validating: A consumer
is a CC/PP conformant validating consumer when it rejects
all non-conformant CC/PP documents.
- non-validating: A
consumer is a CC/PP conformant non-validating consumer when it does
not reject all non-conformant CC/PP documents.
NOTE: A consumer
implementation may be configurable to act as either a validating or
a non-validating consumer at different times.
5.5 Conformance Claims
A conformance claim is valid if it is well formed and meets the
appropriate conformance criteria for the applicable product class
as given above.
A conformance claim is well-formed if it includes the following
- the date of the claim
- the product class (document, producer, or consumer)
- the consumer category (validating or non-validating) if
- the title and dated URI of this document