- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Thu, 04 Oct 2007 17:29:03 +0100
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: public-xml-processing-model-comments@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I read the intent of add-xml-base to force the overt xml:base
indications to be in line with the over [base URI] properties. So I
would propose to redraft 7.1.2 as follows:
1) Replace 'added' with 'added or corrected' in the first para;
2) Add a sentence after the two option typing sentences:
The value of the all option and the value of the relative option
MUST NOT both be true.
3) Replace the substance as follows:
The p:add-xml-base step modifies its input as follows:
* For the document element: force the element to have an xml:base
attribute with its [base URI] property's value as its value.
* For other elements:
If the all option has the value 'true', force the element to have
an xml:base attribute with the element's [base URI] value as its
value.
If element's [base URI] is different from the its parent's [base
URI], force the element to have an xml:base attribute with the
the following value:
If the value of the relative option is 'true', a string which
when resolved against the parent's [base URI] will give the
element's [base URI], otherwise the element's [base URI].
Othewise if there is an xml:base attribute present, remove it.
On this basis, the name might better be changed to something like
p:manifest-base-uris
ht
- --
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)
iD8DBQFHBRTPkjnJixAXWBoRAhjEAJ475Yh2lktQ9qK7Fkv24B4W2WA4VQCeP4DV
MMR8ZQr8gY2zaFI6FND3ky0=
=tx61
-----END PGP SIGNATURE-----
Received on Thursday, 4 October 2007 16:29:18 UTC