[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Namespaces and DTDs - Why not use what we have?

Re:  Namespaces and DTDs - Why not use what we have?
From: "Anderson, John" <John@B...>

> It seems a shame to "break" XML to try and get namespaces into DTDs
> Wouldn't it make more sense to take this informal mechanism as a starting
> point and formalize it?

We should make it clear that the ISO Document Schema Definition Languages 
effort is not attempting in any way to change/break (or force a change) in XML. 

DSDL validates (information sets from parsed) XML documents (or information
sets from SGML documents or other sources which could have been parsed from
an XML document.)

DSDL validation occurs after namespace information has been added. 

So the question for DSDL is, given that many people like or use DTDs, how should
DTDs be interpreted and what conventions should be added to make
them convenient and powerful for validating (information sets from parsed)
XML documents? 

Rick Jelliffe



Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.