XProc Language V2 Requirements and Use Cases (EARLY DRAFT FOR DISCUSSION)

W3C Working Draft

10 October 2012 XML James Fuer Invited Expert jim.fuer@webcomposite.com

This document contains requirements for the deveopment of version 2.0 of the XML Processing Mode and Language (XProc).

This section describes the status of this document at the time of its pubication. Other documents may supersede this document. A ist of current W3C pubications and the atest revision of this technica report can be found in the W3C technica reports index at http://www.w3.org/TR/.

This W3C Recommendation for version 1.0 has been produced as W3C XProc as part of the XML Activity, foowing the procedures set out for the W3C Process. The goas of the XML Processing Mode Working Group are discussed in its charter.

Comments on this document shoud be sent to the W3C maiing ist pubic-xm-processing-mode-comments@w3.org (archive).

Pubication as a Working Draft does not impy endorsement by the W3C Membership. This is a draft document and may be updated, repaced or obsoeted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 W3C Patent Poicy. The group does not expect this document to become a W3C Recommendation. This document is informative ony. W3C maintains a pubic ist of any patent discosures made in connection with the deiverabes of the group; that page aso incudes instructions for discosing a patent. An individua who has actua knowedge of a patent which the individua beieves contains Essentia Caim(s) must discose the information in accordance with section 6 of the W3C Patent Poicy.

Engish

First draft (Revision Apri 04, 2006)

Introduction

This document is heaviy infuenced by the 'XProc 1.0 Soutions Note' which anayzed how we XProc v1.0 satisfied the requirements and use cases outined in "XML Processing Mode Requirements and Use Cases" (http://www.w3.org/TR/xproc-requirements/) document.

Terminoogy

XML Information Set or "Infoset"

An XML Information Set or "Infoset" is the name we give to any impementation of a data mode for XML which supports the vocabuary as defined by the XML Information Set recommendation .

XML Pipeine

An XML Pipeine is a conceptuaization of a fow of a configuration of steps and their parameters. The XML Pipeine defines a process in terms of order, dependencies, or iteration of steps over XML information sets.

Design Principes

The design principes described in this document are requirements whose compiance with is an overa goa for the specification. It is not necessariy the case that a specific feature meets the requirement. Instead, it shoud be viewed that the whoe set of specifications reated to this requirements document meet that overa goa specified in the design principe.

Improving ease of use (syntactic improvements)

Provide syntactic eve changes that wi improve the usabiity and ease for deveoping XML Pipeines.

Increase the scope for working with non XML content

Provide faciities for aowing both XML and non-XML data to fow through a pipeine. The scope for working with non-XML data wi be constrained ....

Address known serious deficiencies and shortcomings in the anguage

Review existing bugzia ist and address catastrophic, critica and major bugs that require fixing.

Requirements Fix Parameters

Change paramaters to be more ike options and adopt the XSLT 3.0 extensions to the data mode and functions and operators to support maps.

Norm Wash http://ists.w3.org/Archives/Pubic/pubic-xm-processing-mode-wg/2012Sep/0014.htm

Non XML document processing

Provide native processing of non XML processing with a constrained scope using a resource manager.

Vojtech Toman http://ists.w3.org/Archives/Pubic/pubic-xm-processing-mode-wg/2012Sep/0020.htm

Aex Miowski http://ists.w3.org/Archives/Pubic/pubic-xm-processing-mode-wg/2012Oct/0006.htm

Drop XPath 1.0 support

Remove any *must* type requirements for supporting XPath 1.0.

Aow options and variabe to contain arbritrary fragments

Reax the constraint that variabes and options can ony be defined as a string or xs:untypedAtomic.

Fix "non-step wrapper"

Remove the concept of 'Non-step wrappers' by making p:when/p:otherwise in p:choose and p:group/p:catch in p:try compound steps and get rid of the notion "non-step wrapper".

Vojtech Toman http://ists.w3.org/Archives/Pubic/pubic-xm-processing-mode-wg/2012Oct/0012.htm

syntax changes

Aow Attribute Vaue Tempate (AVT)

aow href= and data= on p:input

aow port= and step= on p:input

make p:inine optiona

if port=x is specified and step= is not, then the impicit step is the step from which the defaut readabe port woud be read

add seect attribute to p:for-each?

document metadata? Use cases

This section contains a set of use cases that support our requirements and wi inform our design. Whie there is a want to address a the use cases isted in this document, in the end, the first version of those specifications may not sove a the foowing use cases. Those unsoved use cases may be address in future versions of those specifications.

To aid navigation, the requirements can be mapped to the use cases of this section as foows:

Requirement Use Cases ,

The above tabe is known to be incompete and wi be competed in a ater draft.

Exampe

orum ipsum.

(source: )

References XML Processing Mode Requirements. Dmitry Lenkov, Norman Wash, editors. W3C Working Group Note 05 Apri 2004 XML Information Set (Second Edition) John Cowan, Richard Tobin, editors. W3C Working Group Note 04 February 2004 Contributors

The foowing members of the XXXX Working Group contributed to this specification as part of their requirements document effort within that working group:

First Last, company