Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] NVDL as a dispatching architecture

From: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@---------.--.-->
To: xml-dev@-----.---.---
Date: 5/9/2006 12:49:00 AM
Tatu> This approach is obviously less generic than NVDL, but
Tatu> seems reasonable for efficient validation within
Tatu> context of stax (pull) processing.

I am not sure if your approach is less generic.  At a first 
glance, NVDL looks complicated but I would not be surprised 
if your approach can be safely extended for handling NVDL.  

NVDL implementations have been built using SAX.  However, it 
is not easy tell, by reading the NVDL spec, whether NVDL is
implementable using SAX.  To the contrary, most people will 
suppose that it is not.  The same thing might apply to 
pull-based implementations.

Having said this, a single <namespace> element of NVDL
having more than one <validate> element might be a problem 
for pull-based NVDL implementations.  We have to allow a 
single start tag to be *pulled" by more than one validator.

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