The CC/PP Working Group has released a Working Draft of Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies and the Modularization of XHTML has advanced to Proposed Recommendation status.
Background
There are currently significant efforts invested to integrate Web technologies into various devices. Web services are becoming accessible from a wide range of devices including cellular phones, TV, digital cameras and in-car computers. Commercial products and services are deployed or planned based on specifications which take the
J2EE CC/PP Processing technology lets developers write web applications that are accessed by a variety of networked client devices. This technology is developed by the Java Community Process. On this page, you will find links to the specification for the technology and the reference implementation (RI). You can download the specification and RI to start using the technology.
Write Content Once, Deliver It To Any Device!
Most web applications today are designed to be accessed from popular HTML browsers running on desktop clients. These applications
When expressing device capabilities, the strength of CC/PP is that it has the flexibility HTTP content negotiation lacks. Far from simply defining a fixed set of preferences that would be used to build
device profiles, the RDF-based framework also allows the creation of whole vocabularies, making the expression of device and agent capability, as well as user preference, infinitely extensible.
Using CC/PP, creators of Web devices and user agents can easily define precise profiles for their products. Web servers and proxies can use these profiles to
1. Place your web server(s) in a DMZ. Set your firewall to drop connections
to your web server on all ports but http (port 80) or https (port 443).
2. Remove all unneeded services from your web server, keeping FTP (but only
if you need it) and a secure login capability such as secure shell. An
unneeded service can become an avenue of attack.
3. Disallow all remote administration unless it is done using a one-time
password or an encrypted link.
4. Limit the number of persons having administrator or root level access.
5. Log all user
RSS/XML