Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Referencing attributes from the XMLSchema-instance namespace

From: Boris Kolpackov <boris@-------------.--->
To: Michael Kay <mike@--------.--->
Date: 3/2/2007 12:49:00 AM
Hi Michael,

Michael Kay <mike@s...> writes:

> > http://www.w3.org/TR/xmlschema-1/#Instance_Document_Constructions
>
> And that gives the answer?

Well, it says:

"All schema processors have appropriate attribute declarations
 for these attributes built in..."

And then in 3.2.7 it says what are the types of xsi:type, xsi:nil,
etc., as well as:

"There are four attribute declarations present in every schema by
 definition:"

So based on this and quotes you provided in your other email, it
seems like those four attributes are implicitly defined in the xsi
namespace (just like XML Schema built-in types, I guess), cannot be
redefined, and it appears to be legal to reference them in schema
definitions. Even though there could be some chicken and egg
anomalies like providing a default value for xsi:type that differs
=66rom the type name in which it is declared.


Thanks for the feedback.

-boris


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