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

Data vs. Process was Re: Vocabulary Combination ...


process data
W. E. Perry wrote:

>... The larger point is that after 5+ years of XML processing a
> significant number of practitioners have discovered (or reaffirmed what
they already
> knew) that XML applications are effectively monolithic from the syntactic
instance to
> the idiosyncratic output. That is the inescapable consequence of a
syntactic
> definition of XML--a hard fact which has been lost on, or ignored by,
ancillary
> specifications that insist on introducing specious abstractions between
the
> syntactically-conformant instance and some processing of it appropriate to
a desired
> specific outcome. To induce from the nature of  particular processing some
abstract
> data model which appropriately describes an XML input instance as handled
by that
> process may be a useful exercise in designing or refining the
implementation of that
> process, but it is at best otiose to the XML instance itself, or indeed to
other
> processing which might usefully manipulate that instance for other
purposes.

Your writing is illustrative of what might be described as a predeliction
among programmers for describing processes (that's what an algorithm
describes -- a process).

The problem with this analysis is that the world isn't _only_ about
processes and processing -- there exists a declarative approach which has a
fundamental fit with XML -- which fundamentally is, or describes, a data
format (not a process description).

The ontologic approach is such a declarative approach -- for example,
nowhere in the OWL specifications is *any* writing about a "processing
model". You may consider such ontologic descriptions as specious
abstractions, but the whole point of this excercize is that much can be done
*without specifying any processing*.

We have only data and descriptions of data. When I was first discovering
XML, I recall reading the statement that XML is appropriate when the useful
life of the data is expected to be longer than the useful life of the
software that processes it. It seems to me that descriptions of data can
similarly outlive the processes that derive from these descriptions.

Jonathan


PURCHASE STYLUS STUDIO ONLINE TODAY!

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.
Email
First Name
Last Name
Company
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.