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

Re: Document oriented experience reports anyone?

nadia foster

Hi All

I totally forgot that I had already resolved this problem months ago (I had
to evaluate the software before ordering it, and procurement takes a long
time around here).  The only thing I don't know is how Documentum will
handle this (we won't be moving to Documentum 5 until July, and 4i doesn't
play nice with Schemas).


                      Bob Foster                                                                                                 
                      <bob@o...>         To:       Michael Champion <michaelc.champion@g...>                          
                                               cc:       "Nadia.Swaby@p..." <Nadia.Swaby@p...>, Rick Jelliffe                
                      2005-06-08 14:19          <ricko@a...>, XML Developers List <xml-dev@l...>              
                                               Subject:  Re:  Document oriented experience reports anyone?              

XMLBuddy, Oxygen and no doubt other editors support using DTDs for
entities but not for validation, as the XML spec allows a non-validating
parser to do. XMLBuddy uses an off-the-shelf parser (XercesJ). The only
issue is finding the right feature incantation that makes it work.

I believe the industry as a whole is gradually reacting to this common
use case. In another forum, Michael Glavassevich wrote: "The JAXP 1.3
Validation API [1][2] decouples the process of validation from parsing.
You will be able to perform schema validation without also having to
turn on the [DTD] validation feature."

It's certainly the path of least resistance to Just Do It as opposed to
inventing a replacement for DTD entities. If your favorite parser
doesn't support this use case, send them a bug report.

Bob Foster

Michael Champion wrote:
 > On 6/8/05, Nadia.Swaby@p... <Nadia.Swaby@p...> wrote:
 >>In summation, schema can be very useful in publishing, but the lack of
 >>entity support is a huge drawback.
 > Strictly speaking, one can use DTDs (to declare entities) in
 > conjunction with XSD to define everything else.  After all, DTD
 > operates on XML syntax and XSD is defined on the Infoset.  I suspect
 > that there are gotchas that make this difficult ... does anyone know
 > what they might be?
 >>I guess I should copy and paste this in word and send it to the W3C!
 > Yes!


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.