OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: DOCBOOK-APPS: Programmatically accessing configuration info inaDocBook instance

Have you considered customizing the dtd to add the widget configuration
markup you need? The DTD has been designed with customization in mind:
http://docbook.org/tdg/en/html/ch05.html. Where to allow the widget
markup depends on how you want the documents structured. Perhaps inside
a refentry <http://docbook.org/tdg/en/html/refentry.html>?  


-----Original Message-----
From: Richard Campbell [mailto:richard.campbell@oarcorp.com]
Sent: Thursday, August 01, 2002 4:37 PM
To: docbook-apps@lists.oasis-open.org
Subject: DOCBOOK-APPS: Programmatically accessing configuration info in
aDocBook instance

Can anyone suggest a way to accomplish the following?

As an integrator of computer controlled widgets I require my widget
to supply the technical manual for their widget as as DocBook XML file.
I install a widget on my reconfigurable hardware platform I place the
document in a repository so that the operator can browse the manual. In
addition, the document, acting as a configuration file on steroids will
include some widget configuration information that my software
can access to know how to control the widget.  The application will use
libxml2, Gdome, or  gmetadom to parse the xml document and build an
in-memory Document Object Model.

My question is where or what construct in the DocBook would be
to store this sort of configuration information so that it can be
programatically. Index, table, ?

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC