Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] A single, all-encompassing data validation language - good or bad for the marketplace?

From: "Anthony B. Coates (XML-Dev)" <abcoatesecure-xmldev@-----.--.-->
To: xml-dev@-----.---.---
Date: 8/9/2007 12:07:00 PM
I was only looking at the external application/user perspective.  The  
number of separate steps that users need to manually configure in their  
own code tends to have a strong impact on usability; more configuration  
steps means a greater barrier to entry.  The number of steps that the  
processing itself applies internally and transparently to the user is not  
in itself significant (although the time/memory of requirements may  
sometimes be significant).

Cheers, Tony.

On Thu, 09 Aug 2007 12:51:30 +0100, Michael Kay <mike@s...> wrote:

>> Perhaps the expression "single step" was misleading, as what
>> I meant was that the validation of the input against a W3C
>> XML Schema can be done during the XSLT/XQuery processing
>> using a Schema-aware processor, so that you reduce the number
>> of individual steps in the validation process by one.
>
> If you ask Saxon-SA to validate an input document to a transformation,  
> then
> you get a push pipeline that feeds events from the XML parser through the
> schema validator to the Saxon tree builder. Apart from the crucial fact  
> that
> the type information generated by the validator is retained by the tree
> builder, this is very similar to what you would get if you put together  
> your
> own SAX-based pipeline in JAXP or XProc, which you can do of course  
> without
> a schema-aware XSLT processor.
>
> So it all depends what you mean by "steps" - separate steps from the
> application perspective, or separate steps within the internal pipeline?
>
> Internally, Saxon's input pipeline is typically much more complicated, it
> can involve steps that strip whitespace, that combine adjacent text  
> nodes,
> that expand XInclude, that locate the subtree rooted at a particular ID
> value, that maintain the namespace context, etc. And the "step" in this
> pipeline that does schema validation is itself a push pipeline whose
> internal complexity is a wonder to behold...
>
> Michael Kay
>



-- 
Anthony B. Coates
Senior Partner
Miley Watts LLP
Experts In Data
UK: +44 (20) 8816 7700, US: +1 (239) 344 7700
Mobile/Cell: +44 (79) 0543 9026
Data standards participant: genericode, ISO 20022 (ISO 15022 XML),  
UN/CEFACT, MDDL, FpML, UBL.
http://www.mileywatts.com/


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