Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: implementing redefinitions

From: Kasimier Buchcik <kbuchcik@---------.-->
To: "Henry S. Thompson" <ht@---.--.--.-->
Date: 8/19/2005 1:17:00 PM
Hi,

On Wed, 2005-08-17 at 16:00 +0100, Henry S. Thompson wrote:
> -----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.

[...]

Is there an effort scheduled to clarify redefinitions for XML Schema
1.0 as well?

I'm currently unsure if the fact that nobody clarified the test
results yet (which you can find at the beginning of this thread),
means that the people who actually can comment this issue
are still on holiday or at meetings, or if this means that they will
not comment it, for whatever reasons. Please let me know if and how
this issue was noticed by the WG. I don't intend to apply any
pressure, but need to know if it is reasonable to suspend the
implementation of redefinitions on my side, in order to try to
find out what a schema processor _should_ do here.

What to do if the WG will not clarify the problems I see with
redefinitions? Are implementations then free to implement it
in a way they think is suitable? Does this mean that we
have another official area of implementation-dependant behaviour
here?

Regards,

Kasimier





From ht@i... Fri Aug 19 10:52:20 2005
Received: from lisa.w3.org ([128.30.5


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