Python & XML & DTD (warning: noob attack!)

**Peter Hansen** · Jul 18 '05, 07:59 AM

Re: Python & XML & DTD (warning: noob attack!)

Igor Fedorow wrote:[color=blue]
>
> I have an XML file with an internal DTD which looks roughly like this:
> [snip]
> I want to parse this file into my application, modify the data (this includes
> maybe creating and/or deleting nodes), and write it back into the file --
> including the DTD. (It doesn't necessarily need validation, though.)
>
> I tried xml.dom.ext.Pre ttyPrint, but it produces only
> [snip]
> actually lacking the document type definition.
>
> Any help is appreciated![/color]

Unfortunately I don't know of any way you could generate the DTD again,
and I've never seen a package which supports what you ask for (not that
it isn't possible, mind you).

On the other hand, are you sure you need the DTD? We use XML in
dozens of ways and absolutely have never benefited from attempts
to use DTDs, and don't appear to suffer from the lack thereof.

Also, aren't DTDs sort of considered either obsolete or at least
vastly inferior to the newer approaches such as XML Schema, or both?

So my recommendation is to ditch the DTD and see if any problems
arise as a result.

-Peter

**Igor Fedorow** · Jul 18 '05, 08:00 AM

Re: Python & XML & DTD (warning: noob attack!)

On Thu, 29 Jan 2004 15:44:25 +0100, Peter Hansen wrote:
[color=blue]
> Igor Fedorow wrote:[color=green]
>>
>> I have an XML file with an internal DTD which looks roughly like this:
>> [snip]
>> I want to parse this file into my application, modify the data (this
>> includes maybe creating and/or deleting nodes), and write it back into the
>> file -- including the DTD. (It doesn't necessarily need validation,
>> though.)
>>
>> I tried xml.dom.ext.Pre ttyPrint, but it produces only [snip] actually
>> lacking the document type definition.
>>
>> Any help is appreciated![/color]
>
> Unfortunately I don't know of any way you could generate the DTD again, and
> I've never seen a package which supports what you ask for (not that it isn't
> possible, mind you).
>
> On the other hand, are you sure you need the DTD? We use XML in dozens of
> ways and absolutely have never benefited from attempts to use DTDs, and
> don't appear to suffer from the lack thereof.
>
> Also, aren't DTDs sort of considered either obsolete or at least vastly
> inferior to the newer approaches such as XML Schema, or both?
>
> So my recommendation is to ditch the DTD and see if any problems arise as a
> result.
>
> -Peter[/color]

Actually, I don't really *need* it, but I would simply like to have it -- which
obviously isn't possible...

Anyway, thank you for your help!

Cheers =)
*igor*

**Kevin Ballard** · Jul 18 '05, 08:00 AM

Re: Python & XML & DTD (warning: noob attack!)

On 2004-01-29 07:04:44 -0500, Igor Fedorow <igor.NOSPAM@ob da.net> said:
[color=blue]
> I tried xml.dom.ext.Pre ttyPrint, but it produces only
>
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE root>
> <root>
> ...
> </root>
>
> actually lacking the document type definition.[/color]

Why not simply use that, then replace the <!DOCTYPE root> with the DTD? I'm
sure you can parse it out from the original file.

--
"Remember, no matter where you go, there you are."
-Buckaroo Banzai
Kevin Ballard

http://kevin.sb.org

**Andrew Clover** · Jul 18 '05, 08:01 AM

Re: Python & XML & DTD (warning: noob attack!)

Peter Hansen <peter@engcorp. com> wrote:
[color=blue]
> Unfortunately I don't know of any way you could generate the DTD again[/color]

It is possible to preserve the internal subset in DOM Level 3. You can
read it from the property DocumentType.in ternalSubset, and it will be
included in documents serialised by an LSSerializer.

It is not, however, possible to write to the internalSubset, and you can't
create a new DocumentType object with a non-empty internalSubset, for some
reason. So the only standard way to copy an internalSubset would be to make
the new document by parsing something with the same value, eg.:

dtd= oldDocument.doc type.internalSu bset
parser= oldDocument.imp lementation.cre ateLSParser(1, None)
input= oldDocument.imp lementation.cre ateLSInput()
input.stringDat a= '<!DOCTYPE x [%s]><x/>' % dtd
newDocument= parser.parse(in put)
[color=blue]
> I've never seen a package which supports what you ask for[/color]

Plug time: the only package I know of to support DOM Level 3 is my own:

doxdesk.com: software: pxdom

http://www.doxdesk.com/software/py/pxdom.html

Currently this is based on the November 2003 CR spec; there have been a
number of fixes and changes to L3 functionality since, but I'm waiting for
W3C to publish the next draft (presumably Proposed Recommendation) before
releasing 1.0.
[color=blue]
> Also, aren't DTDs sort of considered either obsolete or at least
> vastly inferior to the newer approaches such as XML Schema, or both?[/color]

Certainly they have their drawbacks: they're namespace-ignorant, not
flexible enough for some purposes, and they're a legacy bag on the side of
XML rather than something built on top of it in XML syntax.

Still, they're well-understood and widely supported, and simpler to learn
than Schema at least.

--
Andrew Clover
mailto:and@doxd esk.com

doxdesk.com: home

http://www.doxdesk.com/

Python & XML & DTD (warning: noob attack!)

Python & XML & DTD (warning: noob attack!)

Comment

Comment

Comment

Comment