Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


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

From: "Michael Kay" <mike@--------.--->
To: <mdirector@----.--->,<xml-dev@-----.---.--->
Date: 6/5/2007 3:00:00 PM
I would have said there were two approaches:

(a) continue to work without namespaces. You haven't actually said why you
want to introduce a namespace, and you can use XML Schema without one.

(b) introduce a couple of simple XSLT stylesheets to do the conversion from
the non-namespace form to the namespace form and perhaps vice versa. Run the
transformation on the input before you apply schema validation.

Michael Kay
http://www.saxonica.com/

> -----Original Message-----
> From: Michael Steidl (IPTC) [mailto:mdirector@i...] 
> Sent: 05 June 2007 15:50
> To: xml-dev@l...
> Subject: [xml-dev] Transition from DTD to XML Schema specification
> 
> 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
> 
> 
> 
> 
> 
> ______________________________________________________________
> _________
> 
> XML-DEV is a publicly archived, unmoderated list hosted by 
> OASIS to support XML implementation and development. To 
> minimize spam in the archives, you must subscribe before posting.
> 
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l... List archive: 
> http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>


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