Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: implementing redefinitions

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

Michael Kay" writes:

> I'm struggling with this a bit in Saxon. I think the rule I have to adopt=
 is
> that once a schema component has been used for validating documents that
> exist in the current "environment" (that is, whose PSVIs I can reach),
> redefinition of that schema component is banned.

On an episode-by-episode basis, this makes sense to me, and I think is
covered at least in many cases by the "no new namespaces once we
start" provision.

But across multiple episodes, I don't think the spec. licenses this --
each episode should be treated completely independently.

So, the obvious question -- how can their be more than one document in
the "current 'environment'"?

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)

iD8DBQFDAzUBkjnJixAXWBoRApgqAJ9uYPvEJ1r3IPGnOZYKWN9SfNPQ4ACfS0VO
owVVK4JzsG0SDgjvMbI9giI=
=rkX+
=2D----END PGP SIGNATURE-----

From mike@s... Wed Aug 17 13:48:25 2005
Received: from lisa.w3.org ([


transparent
Print
Mail
Digg
delicious
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