- From: George Cristian Bina <george@oxygenxml.com>
- Date: Sat, 23 Mar 2013 07:38:52 +0200
- To: David Cramer <david@thingbag.net>
- CC: XProc Dev <xproc-dev@w3.org>
Hi David, I stopped development on oNVDL because I moved that into Jing itself, so if you get Jing then you will have NVDL support there. Last year at XML Prague I presented an NVDL implementation in XSLT and orchestrated with an XProc script - the source for that was committed inside the oNVDL project. If you need any information on the NVDL support in Jing or if you encounter any issues with that I will be happy to help. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 3/23/13 5:52 AM, David Cramer wrote: > I'm asking for a friend, but I'm curious about it myself: > > Given a number of xml vocabularies each in its own namespace, there's an > envelope xml that he owns and then down in the tree he allows any > foreign namespace. The result is an envelope xml and somewhere in it, > one or more nodes each containing one of these foreign vocabularies. A > schema will be supplied for each foreign vocab but he doesn't own the > supplied schemas, We would like to validate the xml against all the > relevant schemas at once. > > The two approaches that came to mind are: > > 1. NVDL: Designed for just this situation, however, there's not much > activity around it. JNVDL is flagged as Alpha and was last released in > 2007. oNVDL is likewise from 2007. Does that mean it's done or is it dead? > > 2. XProc: Run the doc through a simple xslt that spits out each > inner-xml using xsl:result document. Then use p:for-each to iterate over > the result docs and c:validate-with-schema each one. A do-it-yourself NVDL. > > Note that I see there was a discussion of nvdl in XProc in 2008 and it's > a proposed extension for v.next: > http://lists.w3.org/Archives/Public/xproc-dev/2008Sep/0073.html > http://www.w3.org/XML/XProc/docs/langreq-v2.html#step-nvdl > > Are my concerns about NVDL valid? I'm tempted to recommend XProc at this > point in any case, just because you can do so much more with it. Even if > he doesn't need the all the power of xproc now, he will someday. If > pxp:nvdl comes along, someday, then so much the better. What would you > recommend? > > Thanks, > David >
Received on Saturday, 23 March 2013 05:39:18 UTC