This is a WORK IN PROGRESS. Incomplete items are marked with @@ symbols and includes such things as final names of new documents and roadmap dates. We have agreed to narrow the focus of the group, and have discussed closing UWA and reopening as Context Awareness and Personalization WG, though we may be able to just rename the group, as it represents a narrowing of scope from the UWA charter.
- 1 Context Awareness and Personalization Working Group Charter
- 2 Scope
- 3 Success Criteria
- 4 Out of Scope
- 5 Deliverables
- 6 Other Deliverables
- 7 Milestones
- 8 Timeline View Summary
- 9 Dependencies
- 10 Participation
- 11 Communication
- 12 Decision Policy
- 13 Patent Policy
- 14 About this Charter
Context Awareness and Personalization Working Group Charter
The Context Awareness and Personalization Working Group seeks to simplify the creation of Web applications that are aware of the context, including personal preferences, device capabilities, and the operating environment, through work on ontologies and associated mechanisms to support adaptation at all points along the delivery channel. This follows on from the former Ubiquitous Web Applications Working Group, and the name change is intended to reflect the narrower scope of the new charter.
- End date
- 31 July 2010
- Proceedings are Member-only
- Initial Chairs
- Dave Raggett
- Initial Team Contacts
- (FTE %: 20) Matt Womer
- Usual Meeting Schedule Teleconferences
- 1-2 per year
- "Virtual" Face-to-face
- 1-2 per year (full-day work sessions coordinated via conference call or instant messaging)
The cost of adding networking capabilities to devices is continuing to drop, resulting in an increasing range of devices and networking technologies. This brings with it the challenge of how to create applications in heterogeneous environments. Web technologies can reduce the barriers to creating applications through abstractions that describe the context using shared models.
The Context Awareness and Personalization Working Group will define extensible modular ontologies for personal preferences, device capabilities and environmental conditions. The ontologies form the basis for shared semantics across different devices and across different interfaces at all points along the delivery channel. These ontologies can include models of objects, states and events, as a basis for describing behavior. This will enable personalization and dynamic adaptation of applications, reducing development costs and improving usability. Methods for accessing these ontologies via markup or scripting languages will be described via two Recommendation Track documents, including @@DIAL 2.0/REDIAL and @@DCCI-lite.
The Group may hold a workshop on the role of the ontology and related work on application authoring and the challenges for addressing privacy, trust and security.
Describe Success Criteria. Example:
- Implementation expectations before requesting to advance to Proposed Recommendation
Out of Scope
Describe areas of work that are not in scope.
Recommendation Track Deliverables
- Delivery Context Ontology (DCO)
- Complete transition to Recommendation, currently at Last Call
- Modularize the DCO
- Content Selection for Device Independence (DISelect) 2.0
- Update DISelect to remove XPath dependency and include a mechanism by which authors select an expression language
- Device Independent Authoring Language (DIAL v2.0/REDIAL)
- Redesign to integrate with any host language
- Detail how to integrate with XHTML 1
- Update convenience functions
- Based on new DISelect
- Delivery Context Client Interface v2.0/DCCI lite
- a more author-friendly version of DCCI
- Proposed here
- Device Description Core Vocabulary v2.0
- Update vocabulary created by Device Description Working Group to tie into the DCO
Working Group Notes
- Delivery Context Ontology Primer
- An introduction to using the DCO
- Creating DCO Modules
- Best practices for creating modules for the DCO
- Personalization Ontology
- A DCO module for supporting personalization of Web applicatons
- DIAL v2.0/REDIAL Part 0: Primer
- An introduction to using DIAL v2.0
- W3C Personalization Roadmap
- Ubiquitous Web Integration of AccessForAll 1.0
- Plans for integrating the delivery context and AccessForAll
- Mapping between Delivery Context Ontology and IMS AccessForAll 2.0 specifications and implementation guidance
- How to translate DCO terms into AccessForAll and back
- Mapping between Delivery Context Ontology and SC36 Metadata for Learning Resources Technical Element draft standard input and implementation guidance
- How to translate DCO terms into SC36 and back
Describe any other deliverables such as test suites, tools, or reviews of other groups' deliverables.
Specification transition estimates and other milestones
Note: The group will document significant changes from this initial schedule on the group home page.
|Delivery Context Ontology||December 2007||June 2009||@@||@@||@@|
|DISelect||June 2004||October 2006||July 2007 * @@||@@||@@|
|DIAL v2.0/REDIAL||May 2006||July 2007 (most recent WD)||@@||@@||@@|
|DCCI v2.0/DCCI lite||July 2004||July 2007||December 2007 *||@@||@@|
|Device Description Core Vocabulary v2.0|
Items marked with a * will return to Last Call
|Working Group Note||FPWD||Note|
|W3C Personalization Roadmap|
|Mapping DCO to IMS Afa2.0||December 2009||July 2010|
|Mapping DCO to MLR Tech. Element||December 2009||July 2010|
|Creating DCO Modules|
|DIAL v2.0/REDIAL Part 0: Primer|
Timeline View Summary
Put here a timeline view of all deliverables.
- Month YYYY: First teleconference
- Month YYYY: First face-to-face meeting
- Month YYYY: Requirements and Use Cases for FooML
- Month YYYY: FPWD for FooML
- Month YYYY: Requirements and Use Cases for BarML
- Month YYYY: FPWD FooML Primer
@@ Review these groups, some were held over from UWA, some added by Matt on a whim
- Coordination on device aware layout
- Hypertext Coordination Group
- For general coordination across W3C activities
- The CAP WG will review Geolocation specifications with relevance to the DCCI, e.g. APIs exposing device capabilities
- Device APIs and Policy Working Group
- The CAP WG will review HTML WG specifications with relevance to APIs exposing device capabilities
- Web Applications Working Group
- The CAP WG will review Web Applications @@
- The CAP WG will review HTML WG specifications with relevance to context awareness
- Internationalization Activity
- For the applicabilty of CAP specifications in different languages
- Semantic Web Coordination Group
- For advice on the use of Semantic Web technologies in the context of work on leveraging the DCI
- Voice Browser
- For SCXML as a markup language for event-driven state machines
- WAI Protocols and Formats Working Group
- To ensure the accessibility of applications using CAP specifications
- Name of External Group
- Nature of coordination
- IMS Accessibility SIG
- technical harmonisation between DCO properties and IMS Afa elements undertaken by common members/editors
- ISO/IEC JTC1 SC36 Metadata for Learning Resources (MLR)
- Editors of Technical Element: harmonisation and mapping of properties across DCO and MLR Technical draft participating
- Open Mobile Terminal Platform
- Will request review of DCO and DCCI 2.0/Lite
- Open Mobile Alliance
- Will request review of DCO and DCCI 2.0/Lite, @@ we also anticipate the DCO being used in DPE, right?
- OpenAJAX Alliance
- @@ Considering dropping this -- looking at their website it seems their focus has shifted away from device API type stuff and are into interoperability of AJAX based technologies.
To be successful, the Ubiquitous Web Applications Working Group is expected to have 10 or more active participants for its duration. Effective participation to Ubiquitous Web Applications Working Group is expected to consume one work day per week for each participant; two days per week for editors. The Ubiquitous Web Applications Working Group will allocate also the necessary resources for building Test Suites for each specification.
Participants are reminded of the Good Standing requirements of the W3C Process.
In the interest of greater public involvement, it is expected that technical discussion will primarily take place in public through a number of channels, although any member has the right to keep any information or discussion to member-only channels.
@@ include details on virtual F2F's, wikis, editor's drafts and task-forces?
A public, archived mailing list <email@example.com> is used to conduct technical discussions, publish approved minutes of group meetings, track issues relating to material previously made public, distribute public versions of documents, conduct public discussion on published documents, and for other public communications.
A member-only, archived mailing list <firstname.lastname@example.org> is used to distribute member-only versions of documents, for member-only discussion on them, and for other member-only communications.
Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the Context Awareness and Personalization Working Group home page.
As explained in the Process Document (section 3.3), this group will seek to make decisions when there is consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.
- When deciding a substantive technical issue, the Chair may put a question before the group. The Chair must only do so during a group meeting, and at least two-thirds of participants in Good Standing must be in attendance. When the Chair conducts a formal vote to reach a decision on a substantive technical issue, eligible voters may vote on a proposal one of three ways: for a proposal, against a proposal, or abstain. For the proposal to pass there must be more votes for the proposal than against. In case of a tie, the Chair will decide the outcome of the proposal.
- This charter is written in accordance with Section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
About this Charter
This charter for the Context Awareness and Personalization Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
Please also see the previous charter for this group.