W3C | XML

XSLT Working Group Charter

The mission of the XSLT Working Group, part of the Extensible Markup Language (XML) Activity, is to define and maintain 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.

Join the XSLT Working Group.

End date 31 January 2013
Confidentiality Proceedings are Member-only
Initial Chairs Sharon Adler
Initial Team Contacts
(FTE %: 40)
Liam Quin, Carine Bournez
Usual Meeting Schedule Telcons: Weekly
Ftf: 2 per year plus TPAC

Scope

XSL consists of two main components: a transformation language known as XSLT, and an expression language for addressing parts of XML documents, known as XPath. As of this charter period (starting in January, 2011), the XSL Working Group has been split into two parts: The XSLT Working Group has responsibility for XPath, XSLT and the supporting documents, and the new XML Layout and Print Working Group will continue the work of developing XSL-FO 2.0, and maintenance on XSL-FO 1.1.

XPath shares a data model, serialization rules, formal semantics, full-text retrieval facilities, and a library of functions and operators with the XQuery defined by the XML Query Working Group, and a type system based on that of W3C XML Schema.

Under this charter, the XSLT Working Group will

XSLT and XPath

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 3.0 and XPath 3.0 is to provide better capabilities for streaming transformations.

A ‘streaming transformation’ is one which:

  1. can run in an amount of memory independent of document size;
  2. can begin delivering results before all of the input to the transformation is available;
  3. can perform the transformation in a single pass over the input document.

Success Criteria

The Working Group expects to demonstrate at least two interoperable implementations of all required and optional features before requesting to advance any of its specifications to Proposed Recommendation.

Deliverables

The XSLT Working Group will deliver W3C Recommendations for:

The Working Group will also deliver, as needed, errata documents and/or corrected editions for specifications it has published previously.

The following documents may become Working Group Notes:

As needed to support desired new features in XPath 3.0 and XSLT 3.0, the XSLT Working Group will work jointly with the XML Query Working Group on:

Jointly maintained requirements and use cases may become Working Group Notes.

Additionally, the XSLT Working Group will deliver jointly with the XML Query Working Group errata documents and/or corrected editions for the following W3C Recommendations:

Milestones

The XQuery Charter gives details on the schedule for the shared documents.

Milestones
Specification FPWD LC CR PR Rec
Note: The group will document significant changes from this initial schedule on the group home page.
XSL Transformations (XSLT) Version 3.0 N/A November 2011 March 2012 September 2012 November 2012
Extensible Stylesheet Language (XSLT) Version 2.0 (second edition) N/A N/A N/A June 2011 August 2011

Other Deliverables

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.

Timeline View Summary

Dependencies

W3C Groups

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.

External Groups

The XSLT 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.

Participation

To be successful, the XSLT Working Group is expected to have 8 or more active participants for its duration. Effective participation to XSLT Working Group is expected to consume one work day per week for each participant; two days per week for editors. The XSLT 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.

Communication

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).

Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the XSLT Working Group home page.

Patent Policy

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 XSLT Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

This revision of the charter (2011) renames some documents from 1.1/2.1 to 3.0, and adjusts milestones as needed, but there are no new Recommendation Track deliverables.

Please also see the previous charter for this group.


Sharon Adler, Chair
Liam Quin, Team Contact

$Date: 2011/07/18 17:46:30 $