object instance data to docbook, xml, pdf, etc?

Harry George harry.g.george at boeing.com
Fri Jul 11 15:35:34 CEST 2003


mertz at gnosis.cx (David Mertz, Ph.D.) writes:

> Harry George <harry.g.george at boeing.com> wrote previously:
> |We are outputting the instance data, sort of like Gnosis xml_objectify,
> |but to docbook DTD.
> 
> You *could* use XSLT to transform the gnosis.xml.pickle output into
> DocBook (I'm pretty sure you mean that, objectify goes in the other
> direction generic-XML -> python).
> 

<blush> Yes, that's what I meant.  BTW, thank you for those tools.


> However, I personally find XSLT extremely awkward.  

Interesting.  I've been pushing back against XSLT ever since it was
invented as a "no parentheses" rendition of DSSSL.  I've run into
other people who used XSLT until they run into a complex task, and
then realize it is a mess.  What's been missing so far is a Python
rendition of the common tasks, and a design pattern for growing
others.

> If someone doesn't
> give you the done-deal, you might find it useful to take
> gnosis.xml.pickle and fork it for your desired DocBook/XML output.  All
> the issues about traversing objects is handled, you should pretty much
> be able to just look for the XML tags that get written, and substitute
> those as needed.
> 

Yep, that's what I had in mind.

> Yours, David...
> 
> --
> Keeping medicines from the bloodstreams of the sick; food from the bellies
> of the hungry; books from the hands of the uneducated; technology from the
> underdeveloped; and putting advocates of freedom in prisons.  Intellectual
> property is to the 21st century what the slave trade was to the 16th.
> 

-- 
harry.g.george at boeing.com
6-6M31 Knowledge Management
Phone: (425) 294-8757




More information about the Python-list mailing list