Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Requirements on validation: (1) combine schemas, (2) divide a document into pieces and validate each piece, (3) use different schema languages, (4) validators work together

From: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@---------.--.-->
To: xml-dev@-----.---.---
Date: 5/6/2008 5:52:00 AM
Noah,

> I don't think you've accurately characterised the XSD language.  

Roger quoted what I wrote.

> You can, 
> to a significant degree, to incremenal validation if your validator 
> supports it. 

Here we apparently disagree.  I think that W3C XML Schema fails to 
meet the goal.

>  First of all, you can get a degree of modularity by using 
> facilities like xs:include.

No, xs:include and xs:import merely provides modularization of schemas. 
Modularization is a good thing, but you still have to understand a lot 
about what you want to include or import

I would argue that include/import is simlar to procedure calls 
while NVDL and its precedessors are similar to software components.  

In the case of NVDL, authors of component schemas have to understand 
nothing about the overall picture.  In WXS and RELAX NG, authors have to
understand everything.

You might be interested in my recent note (see my another mail 
"Full validation of Atom feeds containing extensions").  I believe 
that W3C XML Schema cannot capture advanced examples shown in this note.  
RELAX NG probably can do that, but I do not want to maintain such 
complicated schemas.  NVDL and its predecessor NRL provide practical 
solutions.

Cheers,

-- 
MURATA Makoto (FAMILY Given) <EB2M-MRT@a...>


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