W3C

XProc 2.0: ChangeLog

W3C Editor's Draft

This Version:
http://www.w3.org/TR/2014/ED-xproc-changelog-20141211/
Latest Version:
http://www.w3.org/TR/xproc-changelog/
Editors:
Norman Walsh, MarkLogic Corporation
Alex Milowski, Invited expert
Henry S. Thompson, University of Edinburgh
Repository:
This specification on GitHub
Report an issue
Changes:
Diff against current “status quo” draft
Commits for this specification

This document is also available in these non-normative formats: XML, automatic change markup from the previous draft courtesy of DeltaXML.


Abstract

This document summarizes the significant changes in XProc 2.0.

Status of this Document

This document is an editor's draft that has no official standing.

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

Please report errors in this document by raising issues on the specification repository

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.


Table of Contents

1 Introduction

This document attempts to summarize the significant changes in XProc 2.0. Generally speaking, each significant pull request should include an update to this document which describes the changes made. Of particular importance are user-visible syntax changes and changes in semantics.

2 Changes

First attempt at removing XPath 1.0

Removes references to XPath 1.0. Removes the p:base-uri and p:resolve-uri functions. They existed only for interoperability with XPath 1.0 implementations. The standard XPath 2.0 functions can be used instead.