Hi Roger,
I do not know XProc well enough but NVDL allows you to define
declaratively how you want the document to be processed and that can
mean a variable number of validate actions depending on what the XML
document contains - I do not know if XProc allows this.
But they are different technologies, it is like saying why should I need
XSLT because I can do that also in XQuery and I will get also all the
other benefits of using XQuery.
When one talks about performance penalty one needs to compare the NVDL
processing with something else. Compared with a simple parsing then yes,
there is some more processing involved. Compared with an XProc pipeline
doing the same thing then the best thing will be to run a performance
test but for instance in case of oNVDL there is very little overhead
because the NVDL processing and all the validations are performed during
a single document parsing.
Best Regards,
George
-- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Costello, Roger L. wrote: > Hi Folks, > > 1. I just saw this on a web site: > > "I'm personally against NVDL, I think I would rather have XProc used to > deliver multiple schema languages because then I also have all the > benefits of XProc in my architecture." > > I don't know enough about XProc to respond. Can someone who is familiar > with XProc respond to this? > > 2. Another comment that I heard is: > > "The NVDL processor (dispatcher) adds an additional layer and thus > introduces a performance penalty. > > Does anyone have performance measurements that refutes (or > supports) this statement? > > Thanks. > > /Roger > -- DSDL comments To unsubscribe, please send a message with the command "unsubscribe" to dsdl-comment-request@dsdl.org (mailto:dsdl-comment-request@dsdl.org?Subject=unsubscribe)Received on Thu May 29 22:19:30 2008
This archive was generated by hypermail 2.1.8 : Thu May 29 2008 - 23:13:14 UTC