Mike Maxwell wrote: > Hussein Shafie wrote: >> Mike Maxwell wrote: >>> >>> Would it be possible to create a simple example...? >> >> --> See attached files. > > Thanks, that got me going! Turned out the missing crucial piece for me > was the prefix for the namespace I was using for the extension has to > appear in the 'version' attribute of the root element. From your example: > > <article version="5.0-extension my" > ... > xmlns:my="http://www.acme.com/namespace/my"; > ... > > > > I assume this must be documented somewhere. That is, I realize that > 'version' is a required attr of the root DocBook element, but I didn't > realize that the namespace prefix had to be there, and I can't seem to > find the documentation or explanation. Can you point me at it? I'm > afraid I may have missed something else (and I'm also wondering what to > do if I add more than one extension to DB5, with separate namespaces). >
The two "my"s are totally unrelated. * xmlns:my="http://www.acme.com/namespace/my"; is needed because the document contains element <my:bold>some text here</my:bold> * About <article version="5.0-extension my"> [1] the "version" attribute on the root element of a Document is needed by DocBook 5 (this is checked by the schematron). [2] A value other than "5.0" is needed by XMLmind XML Editor to detect a document as being conforming to a customization of DocBook 5 rather than to plain Docbook 5. Any value is fine. Real world example: version="5.0-subset Scilab". What really counts is that the <detect> configuration element references the value you have chosen: <detect> <and> <rootElementNamespace>http://docbook.org/ns/docbook</rootElementNamespace> <rootElementAttribute localName="version" value="Scilab" substring="true" /> </and> </detect>
