Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Transition from DTD to XML Schema specification

From: "Michael Steidl (IPTC)" <mdirector@----.--->
To: xml-dev@-----.---.---
Date: 6/5/2007 2:49:00 PM
Hello Group:

More than 5 years ago my organisation, the IPTC (www.iptc.org), has 
created first XML document specifications based on DTDs for the purpose of 

exchanging news in a B2B environment. Now we want move the document 
definitions to XML Schemas (to be precise: the "new" XML Schema replicates 

the "old" DTD), and this drives us into a bad situation:

- for the XML Schema we define a default namespace.

- adopters of our document specification set up an XML database and load 
the XML Schema for structure validation.

- then they receive XML documents which are still based on the DTD and 
hence without a namespace.

- the XML DB rejects these XML instances as invalid - and actually this is 

 right.

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.

Thanks 

Michael
==================================================
Sent by:
Michael Steidl
Managing Director of the IPTC <mdirector@i...>
International Press Telecommunications Council
"Information Technology for News"
Visit us on the web at  http://www.iptc.org


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