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

RE: constructive (was RE: Markup perspective not c


free download shallow hal
Hi Didier:

Polarities are not solved; they are managed, that is, 
resolved for a given context and reexamined if reinvoked. 
Tools that do specific tasks well are good for managing 
the polarities natural to the domain.

All most of us want is for XML 1.0, the Core, to stop 
at syntax. IMO, that way layering over it can be a matter 
of choosing among different combinations that can themselves 
over time and with proof of effective application, become 
system profiles.

The DOM is ok.  It manifests as a database (usually local) 
with a tree-sorta structure that is good for operations where 
one needs the whole tree in memory, and can stand the 
overhead.  Some say it is a pig, but that is the 
Shallow Hal attitude.  Big thighs are beautiful too 
given perspective.   If one needs speed and svelte, 
there is SAX and the choice of the high maintenance 
companion:  fast and to the point, but make sure one 
knows about state management and gets a pre-nuptial.

len


From: Didier PH Martin [mailto:martind@n...]

Hi Len

Simon said:
Stop at the parser.  Let communities with needs beyond the parser build 
their own toolsets, and _don't call it XML_.

Len said:
Call them XML applications and XML systems.

Didier replies:
Exactly. An XML document stand alone is:
a) a dead piece of information/knowledge if not
	a.1) use by a machine for some process
	a.2) used by a living organism to get some information/knowledge
b) a useful piece of information/knowledge if:
	b.1) used by a machine for some process
	b.2) used by a living organism to get some information/knowledge

I think that we should pursuit the goal to have programs processing XML
document to be as readable as possible (see all references in Software
psychology - for neophytes just do a google research with software
psychology in it and you'll probably end up with several documents form
Ben Schnederman). Obviously, XML document should be also as readable as
possible.

Len, from my observations I discovered that today the positions are
polarized around two poles:
a) an XML document as an open and readable document and the programs
used to process it as a black box and mostly messy and barely readable.
b) XML as a black box and mostly messy and barely readable and readable
programs (but not necessarily open).

The value of the whole chain can be corrupted by one of its links.

My point is to go beyond these two poles and try to make both the
programs and the XML documents readable. I won't say that as Mike called
it that the DOM is a space suit but more as a 19 century diving suit. It
was good at the time taking into account the maturity of XML and the
knowledge people got about it. Now, its time to move to space suits and
go beyond the DOM.




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.