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

Re: Re: Native XML Interfaces

• From: "Pete Cordell" <petexmldev@codalogic.com>
• To: "Andrew Welch" <andrew.j.welch@gmail.com>,"Timothy W. Cook" <timothywayne.cook@g...>
• Date: Tue, 4 Jun 2013 13:22:14 +0100

Original Message From: "Andrew Welch"
>
> For example the dev is faced with the challenge of extracting the
> <title> and product/@id values from some xml.
>
> They could:
>
> - use xquery/xpath
> - use xom/jdom
> - use sax/stax
>
> instead they use a tool to generate an xsd from the xml, then use a
> binding tool to generate some classes, then use those generated
> classes.

If you just have sample XML files as your data model, which change rapidly, 
isn't there a risk that everybody has a different idea of what the data 
model is?  At least with an XSD there is a definitive documented data 
structure.

Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com

• Follow-Ups:
  • Re: Re: Native XML Interfaces
    • From: Peter Flynn <peter@silmaril.ie>

• References:
  • Re: Re: Native XML Interfaces
    • From: Andrew Welch <andrew.j.welch@gmail.com>
  • Re: Re: Native XML Interfaces
    • From: "Timothy W. Cook" <timothywayne.cook@gmail.com>
  • Re: Re: Native XML Interfaces
    • From: Andrew Welch <andrew.j.welch@gmail.com>