Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [XML Schema 1.1] Using doc() in xs:assert ... the referenced document needs a schema?

From: "Costello, Roger L." <costello@-----.--->
To: "'xmlschema-dev@--.---'" <-------------@--.--->
Date: 4/27/2009 8:04:00 AM
Hi Michael,

> Can you provide a little more information?  Where did you discover
> these requirements?  

I discovered these "requirement" upon using SAXON. Michael Kay has since in=
formed me that this is unique to SAXON, and is not in the specification.

> Making the 'available documents' property be the empty set helps
> ensure (a) better interoperability between validators, and (b) the
> context-independence of schema-validity assessment of an element
> or attribute against a declaration or type definition.  The
> context-independence of validation against a type is important to
> many users of XSD (although not, I suspect, to all).

I'm not clear on (b) but (a) certainly sounds like the decision to disallow=
 doc() for cross-document validation was done to make it easier to implemen=
t 1.1 schema validators. Validators are built once, but used many times. Di=
sallowing doc() seems to sacrifice XSD 1.1 usability in favor of ease of va=
lidator implementations.

/Roger =

From mike@s... Mon Apr 27 16:08:27 2009
Received: from bart.w3


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