oxygen append child and nvdl

Post here issues about NVDL, not specifically linked to the oNVDL implementation.
Posts: 41
Joined: Wed Aug 08, 2007 5:56 am

oxygen append child and nvdl

Post by queshaw » Thu Aug 09, 2007 12:52 am

I think there might be an inconvenient feature of the editor when using nvdl.

For example:


namespace a = "http://a"
start = doc
doc = element a:doc { sec }
sec = element a:sec { empty }


<?xml version="1.0" encoding="UTF-8"?>
<rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0">
<namespace ns="http://a">
<validate schema="xsltwrap.rnc" schemaType="application/x-rnc">
<namespace ns="http://www.w3.org/1999/XSL/Transform">
<validate schema="xslt20.rnc" schemaType="application/x-rnc"/>


<?xml version="1.0" encoding="UTF-8"?>
<doc xmlns="http://a">
<xsl:transform version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"/>

If I right click on doc in the outline, append child suggests the XSLT elements as well as the elements from xsltwrap.rnc. If I enter copy for example, it then indicates that copy doesn't belong in that context.

This is using oxygen 8.2.

Site Admin
Posts: 2102
Joined: Thu Jan 09, 2003 2:58 pm

Post by george » Thu Aug 09, 2007 2:12 pm


That is because we provide the content completion right now using a few heuristics that try to see what proposals different schemas offer in different contexts and as a result it may offer more than only the valid proposals.
I wrote an internal documentation about what we will need to be able to offer valid proposals exactly as described by the NVDL rules but that is not yet implemented - and it is not a trivial task either.

Best Regards,
George Cristian Bina

Post Reply