Re: version and forward compatibility

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The following excerpt from the minutes of the f2f [1] bears on the
possible resolution of this topic:

  Comment 15

  If the href attribute of a p:import statement has a URI that begins
  http://www.w3.org/ns/xproc/ then it may declare atomic steps in the p:
  namespace. A processor that recognizes that URI may choose not to read
  it.

  It is a static error if a pipeline contains a step that isn't
  declared. Consequence: you cannot write a backwards-compatible
  pipeline that includes a new compound step.

  It is a dynamic error to attempt to evaluate a step for which you do
  not have an implementation.

  Ignore unknown options in the forwards-compatible case

  Changed signature counts as a static error (except for optional options)

  we won't make backwards-incompatible changes to steps without changing
  their names.

ht

[1] http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Nov/0031.html
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFHRbxykjnJixAXWBoRAoTkAJ48VQmvfVThbeU/nFsAkwujqL/8BQCfdrEI
amh0e2ntZ0LV6QyNak+mZvA=
=r19G
-----END PGP SIGNATURE-----

Received on Thursday, 22 November 2007 17:29:31 UTC