The mission of the XSL Working Group, part of the Extensible Markup Language (XML) Activity, is to define a practical style and transformation language capable of supporting the transformation and presentation of, and interaction with, structured information (e.g., XML documents) for use on servers and clients. The language is designed to build transformations in support of browsing, printing, interactive editing, and transcoding of one XML vocabulary into another XML vocabulary. To enhance accessibility, XSL is able to present information both visually and non-visually. XSL is not intended to replace CSS, but will provide functionality beyond that defined by CSS, for example, element re-ordering.
End date | 31 January 2009 |
---|---|
Confidentiality | Proceedings are Member-only |
Initial Chairs | Sharon Adler |
Initial Team Contacts (FTE %: 70) |
Michael Sperberg-McQueen, Liam Quin |
Usual Meeting Schedule | Telcons: Weekly Ftf: 5-6 per year |
XSL consists of three main components, a transformation language known as XSLT, an expression language for addressing parts of XML documents, known as XPath, and a vocabulary of formatting objects with their associated formatting properties, known as XSL-FO.
This charter defines the next phase in the continuing development of XSL. Both XSLT Version 1.0 and XPath Version 1.0 were published as W3C Recommendations in November 1999. XSL Formatting Objects became a W3C Recommendation in October 2001.
XSLT 2.0, XPath 2.0, and other related specifications were published as Candidate Recommendations on 3 November 2005. XSL 1.1 was published as a Candidate Recommendation on 20 February 2006.
Under this charter, the XSL Working Group will
XSLT 2.0 is a language for transforming XML documents into other XML documents; it is intended to be used in conjunction with XPath 2.0. A transformation expressed in XSLT describes rules for transforming one or more source trees into one or more result trees. A transformation is specified through a set of template rules. The structure of result trees can be completely different from the structure of the source trees. In constructing a result tree, nodes from the source trees can be filtered and reordered, and arbitrary structure and content may be added. This mechanism allows a stylesheet to be applicable to a wide variety of source trees that have similar tree structures.
An important requirement for XSLT 2.0 and XPath 2.0 is to provide schema-awareness, so that simple datatypes and complex types defined using XML Schema may be visible to processors. It is also important for XSLT transformations to take place without requiring schema-awareness and validation.
A series of working drafts of both XPath 2.0 and XSLT 2.0 have been published, beginning in December 2001. For XSLT, major differences from the 1.0 versions are summarized in Appendix K of the XSLT 2.0 specification. For XPath 2.0, Appendix H provides a summary of the main areas of incompatibility between XPath 2.0 and XPath 1.0.
The XSL Working Group moved the XSL 1.0 specification of formatting objects to Recommendation on 15 October 2001.
For the period of this new charter, the XSL Working Group will continue to maintain the XSL Recommendation, progress XSL 1.1 to Recommendation, and develop a version 2.0 of XSL formatting objects.
The Working Group expects to demonstrate at least 2 interoperable implementations of all required and optional features before requesting to advance to Proposed Recommendation.
Jointly with the XML Query Working Group, a set of W3C Recommendations for:
A set of W3C Recommendations for:
Jointly with the XML Query Working Group, if needed to support features in XPath 2.1, the Working Group will investigate the work on:
Note: The XSL and XML Query Working Group have compiled a list of Candidate requirements for XQuery 1.1 and XPath 2.1. This is not meant to be an exhaustive list of such features, and should be published in document form before any work in the area can proceed.
The following documents will become Working Group Notes:
The Working Group also maintains the following specifications:
Specification | FPWD | LC | CR | PR | Rec |
---|---|---|---|---|---|
Note: The group will document significant changes from this initial schedule on the group home page. | |||||
XQuery 1.0 and XPath 2.0 Data Model | N/A | N/A | N/A | September 2006 | November 2006 |
XQuery 1.0 and XPath 2.0 Functions and Operators | N/A | N/A | N/A | September 2006 | November 2006 |
XQuery 1.0 and XPath 2.0 Formal Semantics | N/A | N/A | N/A | September 2006 | November 2006 |
XSLT 2.0 and XQuery 1.0 Serialization | N/A | N/A | N/A | September 2006 | November 2006 |
XML Path Language (XPath) 2.0 | N/A | N/A | N/A | September 2006 | November 2006 |
XSL Transformations (XSLT) Version 2.0 | N/A | N/A | N/A | September 2006 | November 2006 |
Extensible Stylesheet Language (XSL) Version 1.1 | N/A | N/A | N/A | September 2006 | November 2006 |
XML Query 1.0 and XPath 2.0 Full-Text | N/A | September 2006 | January 2007 | May 2007 | September 2007 |
Extensible Stylesheet Language (XSL) Version 2.0 | June 2007 | ? | ? | ? | ? |
The Working Group expects to produce interoperability test suite for their specifications, intended to assess the accuracy of the Candidate Recommendations, and to promote interoperability.
When approved by the XML Coordination Group, liaison with other W3C Working Groups can be accomplished through joint task forces. It is expected that this be required for liaison with at least the XML Schema, XML Query, and Internationalization Working Groups.
The XSL Working Group will also work with other W3C Working Groups to determine the appropriate media type registration for XSL.
The XSL Working Group is responsible for maintaining active communication with national and international standards bodies and industry consortia whose scope of work intersects its own. This specifically includes, but is not limited to, OASIS and IETF.
To be successful, the XSL Working Group is expected to have 8 or more active participants for its duration. Effective participation to XSL Working Group is expected to consume one work day per week for each participant; two days per week for editors. The XSL 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.
This group primarily conducts its work on the Member-only mailing list w3c-xsl-wg@w3.org (archive). Joint communication with the members of the XQuery Working Group communicate via mailing list w3c-xsl-query (archive).In addition, there is a separate mailing list, w3c-xsl-fo-sg (archive), for discussion on XSL formatting objects; all lists are Member-confidential.
Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the XSL Working Group home page.
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.
This charter for the XSL Working Group has been created according to section 6.2 of the Process Document. Except as specified in this charter, the Working Group follows the Common Procedures for XML Working Groups. In the event of a conflict between this document, the common procedures, 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.
Copyright© 2006 W3C ® (MIT , ERCIM , Keio), All Rights Reserved.
$Date: 2006/09/26 20:24:47 $