- From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
- Date: 05 Sep 2001 09:52:27 +0100
- To: "Joseph M. Reagle Jr." <reagle@w3.org>
- Cc: merlin <merlin@baltimore.ie>, "Gregor Karlinger" <gregor.karlinger@iaik.at>, "Donald Eastlake" <lde008@dma.isg.mot.com>, w3c-ietf-xmldsig@w3.org, henry@w3.org
"Joseph M. Reagle Jr." <reagle@w3.org> writes:
> At 19:43 7/12/2001, Joseph M. Reagle Jr. wrote:
> > In speaking to Henry Thompson about this, he realized that the schema spec
> > doesn't provide this info as a normalized attribute value, only as a PSVI
> > normalized attribute value which XPath wouldn't see -- this is a bug meriting
> > an erratum most likely.
See other recent threads - it's not clear whether it's a bug or a feature.
> > I'm still thinking all this through, so it requires more
> > conversation. (Best yet, since XSV (schema validator) is written
> > in python, I'd like to see what kind of node set it returns and
> > what an XPath selection over it returns.)
>
>
> BTW: Short of playing with an implementation of a nodeset, XSV -r
> will return a reflection of the actual schema augmented
> Infoset. That reflection is a 2 meg file (for a simple 1 line XML
> document and 4 line schema document attached!) with the following,
> which *seems* to report a default value normalized and schema
> normalized (as it should) despite what Henry said(?):
>
>
> <normalizedValue>baz</normalizedValue>
> <psv:schemaNormalizedValue>baz</psv:schemaNormalizedValue>
This _was_ a bug in XSV, in the sense of not conforming to the
spec. as written. For some time now, you get
<normalizedValue xsi:nil='true'/>
. . .
<psv:schemaNormalizedValue>baz</psv:schemaNormalizedValue>
from XSV -r.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
Received on Wednesday, 5 September 2001 04:56:02 UTC