CC/PP

1. CC/PP
2. Basic Scenario
3. Specific usage example
4. CC/PP is an RDF Application
5. CC/PP Architecture
6. Components and Properties Example
7. Some More Details
8. Defaults
9. Modified (HTTP) Scenario: Defaults
10. Current Position
11. Exisiting Vocabularies
12. Implementations

CC/PP

Basic Scenario

• A usual request is extended with a Profile
  • the exact form of the protocol extension is not yet standardized by CC/PP
    • subject of onging work, see later
  • the exact form of the protocol extension is not yet standardized

    by CC/PP

    • subject of onging work, see later
• Profiles describe features of a category of user agents
• Server returns an adapted information

Specific usage example

CC/PP is an RDF Application

• CC/PP profiles are described in terms of RDF:
  • formalism for metadata
  • describes properties on resources
  • can be represented in terms of directed graphs
• RDF has a representation in XML, too
  • we will not use it here…
  • …but may be used in transferring profiles over the wire

CC/PP Architecture

• CC/PP has a two-level hierarchy
  • each CC/PP Profile has a number of Components, and …
  • each Component has at least one or more Attributes
• Example for components: hardware platform, user agent, …
• Example for attributes: OS type, browser version, …

Components and Properties Example

Some More Details

• The overall structure is defined by CC/PP
  • through RDF types like “ccpp:component”
• But CC/PP does not define the property values like “display”
• Instead, application areas define their own terms
  • eg, how to characterize a browser, an operating system
  • in the previous example: “name”, “htmlVersionSupported”, etc
• CC/PP is a framework where communities can plug in their own vocabularies
• CC/PP is a framework where communities can plug in
• their own vocabularies

Defaults

• Some information can be stored on servers
• Usage of ccpp:defaults can greatly reduce the profile size
  • it may refer to properties stored elsewhere

Modified (HTTP) Scenario: Defaults

Current Position

• CC/PP Structure and Vocabularies is a Rec. (Jan. 2004)
• Current work:
  • “Processing and Protocol”
    • binding to HTTP 1.1, SOAP, etc
    • behaviour of intermediaries
      • e.g., a proxy/intermediary can transform XHTML to WML on the fly…
  • adjustment with revised RDF:
    • “old” RDF does not have datatypes for literals..
    • …hence CC/PP defines attributes like ccpp:integer, ccpp:rational
    • with a revised RDF this becomes unnecessary
      • RDF will include references to XML Schema datatypes for literals
  • work done by the W3C Device Independence Working Group

Exisiting Vocabularies

• IETF Media Feture Registration (CONNEG)
  • IANA registrty for feature tags
    • screen colour depth, type of available printer paper, available fonts,…
    • the vocabulary could be expressed in CC/PP
• Other media data (WAVE, MPEG, TIFF) vocabularies could also be expressed in CC/PP
• Other media data (WAVE, MPEG, TIFF) vocabularies could

  also be expressed in CC/PP

• User Agent Profile Specification (UAPROF):
  • originates from the WAP Forum (now: OMA)
  • aims at WAP mobile devices like, e.g., cell phones
  • includes terms like “BitsPerPixel”, “CPU”, “Keyboard” (ie, QWERTY, PhoneKeypad, etc), “ScreenSize”, etc.
  • includes terms like “BitsPerPixel”, “CPU”, “ScreenSize”,

    “Keyboard” (ie, QWERTY, PhoneKeypad, …), etc.

  • structure is like CC/PP but with specific attribute definitions
  • CC/PP model follows UAPROF, albeit more general
  • cooperation is in place for harmonization

Implementations

• A number of implementations exist, including
  • reference implementations in, eg, Java
  • mobile application servers
  • validators, test environments
• Check project page: http://www.w3.org/Mobile/CCPP/