The specification is here: http://www.nvdl.org/ DSDL includes NVDL: http://www.dsdl.org There is an NVDL tutorial here: http://jnvdl.sourceforge.net/ There are also notes and an introduction here: http://www.dpawson.co.uk/nvdl/ I think it helps to read an NRL tutorial also because many things seem t...

Patch file onvdl.diff below. You would run: patch -p1 <onvdl.diff in the directory into which src.zip was extracted. The diff contains CRLF line endings, which might get lost if you copy and paste from the web browser. onvdl.diff: diff -Naur src/com/oxygenxml/validate/isoschematron/SaxonSchemaReader...

This is really a patch suggestion rather than an issue. I am using saxon 8.x in a java application and didn't want to also have saxon 6.x on my classpath. So, I: 1. Replaced com.icl.saxon with net.sf.saxon throughout the source. 2. Modified com/oxygenxml/validate/isoschematron/SchemaReaderImpl.java ...

Oxygen complains that the attribute dummy-for-xmlns is not allowed on some element when I assign a prefix to the XSLT namespace in schematron, e.g.: test.nvdl: <rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"> <anyNamespace> <validate schema="test.sch" schemaType=&q...

Thank you. The XSLT looks like that will help answer questions I read your answer as confirming what I thought might be true. Effectively, while sections can be dispatched for validation based on namespace, independent of the position of elements relative to each other, sections that are created by ...

Thank you for the explanation. In your example, is it the start mode that determines which schema is being used for each section? For example, this instance would be rejected: <quote xmlns="http://a"/> because the start mode results in validation against a.rnc. If I had a document type in ...

After seeing how the context element works (hopefully), I tried using triggers again and it seems to work (allow validation of an element in the same namespace using a different schema): a.rnc: namespace a = "http://a" start = root root = element a:doc { section+ } section = element a:sect...

I think I understand what context is for, based on this from the NRL tutorial: http://www.thaiopensource.com/relaxng/nrl.html#Element-name_context So, in my example, if I remove the p element from b.rnc, make quote be the root element and use a different namespace, then it restricts quote to being a...

I think there might be an inconvenient feature of the editor when using nvdl. For example: xsltwrap.rnc: namespace a = "http://a" start = doc doc = element a:doc { sec } sec = element a:sec { empty } xsltwrap.nvdl: <?xml version="1.0" encoding="UTF-8"?> <rules xmlns=&qu...

As far as I can tell, the spec doesn't describe the context element. Does it qualify the next mode to use based on the name of an element within the section being validated? I thought this might work (allow p to be validated by b.rnc instead of a.rnc): a.rnc: namespace a = "http://a" start...

Do triggers allow you to validate elements in the same namespace using different schemas? If so, how do you specify which schema to use for the different sections?