Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Transition from DTD to XML Schema specification

From: ht@---.--.--.-- (----- -. --------)
To: mdirector@----.---
Date: 6/5/2007 3:32:00 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Steidl (IPTC) writes:

> What are best practices for such a sliding transition from DTD to XML 
> Schema validated documents and are there workarounds to allow the import 
> of both non-namespaced and namespaced XML instances. Our document 
> specifications are used worldwide and there is no way of defining a "day 
> X" from that on DTD based instances are abondoned and only XML Schema 
> based instances are allowed.

Do some/all/most of your users include a DOCTYPE in their instances?

If so, just edit the DTD (centrally and, if they reference the DTD
locally, the local copies) to include an attribute declaration of the
form

 xmlns CDATA #FIXED "[your NS URI here]"

Then your instances will have the namespace they need for your
validator (providing it's not unhelpful wrt external subsets).  This
reduces your problem from editing all your instances to just editing
your DTD (and all its copies) -- should be much more managable. . .

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@i...
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFGZYHdkjnJixAXWBoRAufZAJ0RfrrOi075XuYSOcdmfbY2NHelVACdFmC4
2ZYEwcw7UW/eyqHT1SfksBE=
=VnIk
-----END PGP SIGNATURE-----


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent