[
Lists Home |
Date Index |
Thread Index
]
"Dare Obasanjo" <dareo@microsoft.com> writes:
> The sForS is not a valid schema and thus should fail to validate.
I think it's time to stop saying this. As Eddie noted, there is only
one remaining issue (the use of whiteSpace in the definitions for the
builtin primitives) and this is a contentious issue -- validators
which enforce all and only the normative requirements now pass the
sForS.
> As for validating processors to allow
>
> <xs:import namespace="http://www.w3.org/2001/XMLSchema"; />
>
> so users can specify items from the http://www.w3.org/2001/XMLSchema
> namespace in their instance documents is a work around to this
> deficiency that I am not sure any validating processor currently
> implements.
Works in XSV. But why do it? All the public components from the
sForS are already available by definition, without any import being
required.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2002, 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/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
|
