Lists Home |
Date Index |
"Marty Burns" <firstname.lastname@example.org> writes:
> I guess the only minor downsides I see to your redefine method is:
> 1) you would have to look to the schemaLocation attribute in the instance
> file to recognize that the redefinitions occurred.
Yes, or control the schema documents used more explicitly at
validation invocation time . . .
> 2) you would not be able to pick and choose which instances of the code list
> is overridden -- e.g. one instance uses <cl:code>foo</> and another uses
Well, to do that you don't redefine, you define your own restriction
in your own namespace, and use xsi:type, i.e.
> 3) This is more of a question -- is it possible to redefine several types
> from different namespaces in a single schema file so there would be a single
> incorporation of all changes referenced in the schemaLocation attribute of
> the instance file.
Not directly possible -- if you want exactly one driver schema doc, it
would have to xs:import one redefining schema doc per namespace, and
hope your validator uses the xs:import schemaLoc hints (which they all
do, as far as I know).
> Thanks again for highlighting a promising solution that might be able to
> meet all the UBL requirements.
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: email@example.com
[mail really from me _always_ has this .sig -- mail without it is forged spam]