This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: Device Independence and Content Adaptation.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Standards
|
2004-01-15
|
translations
·
errata
This document describes CC/PP (Composite Capabilities/Preference
Profiles) structure and vocabularies. A CC/PP profile is a
description of device capabilities and user preferences. This is
often referred to as a device's delivery context and can be used to
guide the adaptation of content presented to that device.
The Resource Description Framework (RDF) is used to create
profiles that describe user agent capabilities and preferences. The
structure of a profile is discussed. Topics include:
- structure of client capability and preference descriptions,
AND
- use of RDF classes to distinguish different elements of a
profile, so that a schema-aware RDF processor can handle CC/PP
profiles embedded in other XML document types.
CC/PP vocabulary is identifiers (URIs) used to refer to specific
capabilities and preferences, and covers:
- the types of values to which CC/PP attributes may refer,
- an appendix describing how to introduce new vocabularies,
- an appendix giving an example small client vocabulary covering
print and display capabilities, and
- an appendix providing a survey of existing work from which new
vocabularies may be derived.
|
Group Notes
|
2010-06-29
|
This document describes CC/PP (Composite Capabilities/Preference Profiles)
Structure and Vocabularies 2.0. A CC/PP profile is a description of device
capabilities and user preferences. This is often referred to as a device's
delivery context and can be used to guide the adaptation of content presented
to that device.
The Resource Description Framework (RDF) is used to create profiles that
describe user agent capabilities and preferences. The structure of a profile
is discussed. Topics include:
- structure of client capability and preference descriptions, AND
- use of RDF classes to distinguish different elements of a profile, so
that a schema-aware RDF processor can handle CC/PP profiles embedded in
other XML document types.
Version 2.0 of CC/PP ensures its alignment with the latest version of RDF.
CC/PP vocabulary uses identifiers (URIs) to refer to specific
capabilities and preferences, and covers:
- the types of values to which CC/PP attributes may refer,
- an appendix describing how to introduce new vocabularies,
- an appendix giving an example small client vocabulary covering print
and display capabilities, and
- an appendix providing a survey of existing work from which new
vocabularies may be derived.
|
|
2001-12-20
|
This document describes how existing vocabularies for different
classes of devices and user agents can be used in CC/PP components,
and how to create schemas that encapsulate existing vocabularies.
It discusses the results of the coordination with the IETF CONNEG
Working Group, as well as the WAP Forum UAPROF Working Group and
several other groups, which have related activities. It contains a
number of schemas and software examples which has been contributed
voluntarily by individuals.
It also gives an example of heuristics, which can be used to
adapt content to a CC/PP profile, thus giving some guidelines for
those who want to use CC/PP to implement content adaptation. It
also serves to provide vocabulary and schema designers with key
guidelines regarding extensions to existing vocabularies or
development of new ones.
|
|
1999-07-27
|
In this note we describe a method for using RDF, the Resource
Description Format of the W3C, to create a general, yet extensible
framework for describing user preferences and device capabilities.
This information can be provided by the user to servers and content
providers. The servers can use this information describing the
user's preferences to customize the service or content provided.
The ability of RDF to reference profile information via URLs
assists in minimizing the number of network transactions required
to adapt content to a device, while the framework fits well into
the current and future protocols being developed a the W3C and the
WAP Forum.
|
Obsolete Specifications
These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.
Retired
|
2001-12-20
|
This document gives implementors advice on how to protect the
privacy of a CC/PP user, and outlines how this can be applied using
P3P in HTTP with the CC/PP Exchange protocol.
|
|
2000-07-21
|
This document outlines the requirements for a CC/PP framework,
vocabulary, and trust model, and provides an overview of an
architecture that satisfies these requirements. It represents the
current consensus of the working group.
|
|
2000-07-21
|
This document contains terminology and abbreviations that are
used in other CC/PP documents. For a detailed description of CC/PP,
please see [CC/PP].
|
W3C
