oxygen append child and nvdl
Post here issues about NVDL, not specifically linked to the oNVDL implementation.
oxygen append child and nvdl
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.
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.
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
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
George Cristian Bina
Return to “General NVDL Issues”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service