XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Re: Native XML Interfaces

Wow!  Now THAT is an education problem.  Nail Hammer Soup.

We get similar but not the same. I see document production processes  
from spreadsheets created without noticing the DTDs they spec'd are  
incompatible (don't actually validate the structures they are  
projecting).  The quote is "That's just ASCII and who cares..."

len

Quoting "Timothy W. Cook" <timothywayne.cook@gmail.com>:

> On Mon, Jun 3, 2013 at 8:12 AM, Andrew Welch  
> <andrew.j.welch@gmail.com> wrote:
>>> But Andrew, maybe I include myself in that category of not being aware
>>> of the APIs that are available. Could you exand on that with a couple
>>> of examples?
>>
>> 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.
>
> Okay, thanks.  Maybe I won't include myself in that group then.  :-)
> That is REALLY going the long way around.
>
> --Tim
>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS