Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: implementing redefinitions

From: ht@---.--.--.-- (----- -. --------)
To: "Michael Kay" <mike@--------.--->
Date: 8/17/2005 5:00:00 PM
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for this clear and succinct statement of the situation, which I
think the XML Schema WG should take into consideration as it tries to
clarify the whole schema composition story for XML Schema 1.1.

Michael Kay writes:

> In QT we have to consider a query or transformation as a whole. Documents
> are annotated with types, and we need to have confidence that when we see=
 a
> type annotation, we know what type it refers to. The processing model
> assumes that types can be identified by a QName. For this to work, we can=
't
> have two different types with the same QName within the scope of a query =
or
> transformation (in the XQuery case, this scope is an entire database...).
>
> This is something of a pain, because it means you can't use XSLT to
> transform from one version of a schema to another version of the same sch=
ema
> if it uses the same namespace. Clearly we need a versioning story, as you
> have often said yourself...
>
> But it also affects redefine. If I load two documents as inputs to a query
> or transformation, one validated using schema A, and the other using sche=
ma
> R which redefines schema A, then I've got two types with the same name, a=
nd
> everything (in particular, QT type checking) breaks.

What do you (Mike) think _should_ happen in this case?  Whose
responsibility is it to detect this condition, and what should they do
when they do?

ht
=2D -- 
 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@i...
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged sp=
am]
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDA1D0kjnJixAXWBoRAumMAJoCO4l59oDgxeljA7Mp322qsMl6rgCfVX+y
cmPSGv4wYfRyVwdXe6MYXG8=
=DpdN
=2D----END PGP SIGNATURE-----

From mike@s... Wed Aug 17 15:36:30 2005
Received: from lisa.w3.org ([128.30.52.41]


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent