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

 


Help: OASIS Mailing Lists Help | MarkMail Help

docstandards-interop-tech message

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


Subject: FYI: dbdita demo available


Hi, Interoperability Enthusiasts:

FYI, there's a new docbook2dita plugin on the DITA Open Toolkit site:


Besides complementing the existing dita2docbook transform by providing a docbook2dita transform, this plugin provides four interoperability demos:

Caveat: These demos are only at the proof of concept level.

To install:

1. Install the Java, Ant, and the DITA Open Toolkit 1.3 as described in http://dita-ot.sourceforge.net/

2. Install the DocBook toolkit (tested only at the 1.69.1 level) and DocBook DTDs (tested only at the 4.4 level).

I suspect that more recent versions of the toolkit and 4.x versions of the DTD to work but I haven't had a chance to test. The demos go with DTDs as a lowest common denominator between DocBook and DITA instead of trying to mesh RelaxNG with XML Schema.

3. Install the docbook2dita plugin in the demo directory of the DITA Open Toolkit (creating a new dbdita subdirectory).
Edit the demo/dbdita/dbdita.properties file to identify the location of the DocBook toolkit and DocBook DTDs (doubling backslashes if you are using Windows).

4. From the base directory of the DITA Open Toolkit, execute: ant -f demo/dbdita/install-plugin.xml

To exercise the demos after installation:

1. From the base directory of the DITA Open Toolkit, execute: ant -f demo/dbdita/run-ant.xml

By the way, the DocBook-to-DITA transform is a bit experimental in that it tries to separate the input and output logic. When an output element is generated, the output logic requests content that's appropriate for that context. For instance, the output logic for <ul> requests <li> content. It's up to the input logic to determine how best to meet the content request from the current input context. As a result, the transform tends to be declarative and flexible but does run slower. The mapping between the vocabularies in the DocBook-to-DITA transform is far from complete, but it's a start.

The plugin provides more detailed explanations of the demos and the transform.

Perhaps these demos suggest some ODF equivalents?


Hoping that's interesting,


Erik Hennum
ehennum@us.ibm.com


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