oxygen append child and nvdl

[queshaw]

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="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0">
<namespace ns="http://a">
<validate schema="xsltwrap.rnc" schemaType="application/x-rnc">
<mode>
<namespace ns="http://www.w3.org/1999/XSL/Transform">
<validate schema="xslt20.rnc" schemaType="application/x-rnc"/>
</namespace>
</mode>
</validate>
</namespace>
</rules>

test.xml:

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

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.

[george]

Hi,

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