[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: Namespace and DocBook XML
Ok, maybee I wasn't quite clear. Let us aasume that the element "myelement" may contain #PCDATA and/or DocBook markup. I know, I can't inherit the DocBook DTD, and I have no intension of copying the wholeDocBook DTD into my DTD. What I basicly wan't to to is: Define myelement to contain #PCDATA. And then basically ignore the content of that element. I was thinking, that mybee I could use namespaces to solve it, something like <?xml version="1.0"> <db:myroot xmlns:db="http://mynamespace"> <db:myelement> <itemizedlist> <listitem><para>item 1</para></listitem> <listitem><para>item 2</para></listitem> </itemizedlist> <para>Some text</para> </db:myelement> </db:myroot> But, I havn't yet figured exactly how to do it, if it is possible at all ? Jens On Thu, 8 Nov 2001, Elliotte Rusty Harold wrote: > >2. I have developed tiny XML language, that is basicly a heiracical > >database. The content model of all the lower level elements are stricty > >DocBook XML (i.e para, itemizedlist, etc.) > > > >In another DocBook document, I have embedded PIs, that refer to > >nodes in my database. Applying a special XSLT stylesheet, have the effect > >of merging my DocBook document with the database, and thus procducing a > >new DocBook documet. > > > >I am able to validate both the original document and the resulting > >document as beeing DocBook compliant. > > > >My question is : how do I validate my database (is it at all possible > >with DTDs) ? > > Write a DTD for your database document, add a DOCTYPE declaration > pointing to that DTD, and validate it as you would a Docbook or any > other document. > > >How should my DTD look like ? > > > > This depends on what your document looks like.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC