OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Bad Business (was Re: advocating XML)

Close.   A competent manager listens to the 
customer, reads the RFPs and counts requests 
for functionality.  They understand the 
mix of products they are providing and 
the means by which they meet requirements.  
Counting requests, when they go above some 
threshhold, they plan to implement new 
functionality.  They are knowledgeable about 
the changes in the technology they provide 
and have anticipated the convergence of 
changes.  They don't dismiss technologies 
out of hand; they understand how each 
technology affects the other.  The idea 
that was the "failure" last year becomes 
the "success" a year later when the environment 
in which it is implemented changes (cheap 
fast processors implementing cache memory 
+ cheap disk drives and cheap RAM = XML). 
It's a long ride from the lab to the street.

Then they look around their staff and decide 
who gets to be the first penguin in the water.  
They do that about a year before they need 
the functionality so they can if they have 
to make a few mistakes off Broadway.

CSV works fine for lots of transactions that 
have smooth edges.   To justify markup, look 
at the pipeline and the lifecycle.


Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h

-----Original Message-----
From: David Megginson [mailto:david@megginson.com]

This is a strange thread -- I'll admit to not having read every
posting, but why *should* anyone want to go out and advocate XML where
it might not be needed?

If comma-delimited does everything someone wants, then it makes sense
to stick with it.  If the person later wants to do stuff that
comma-delimited makes too hard (nested/recursive structures, optional
and repeatable fields, partly self-describing format, structural
validation, markup mixed into a text stream, etc.) then, and only
then, does it make sense to come and talk with us, the XML community.

There's no point anticipating those problems -- a competent manager
should wait until they actually come up.  Paying the high cost of a
transition to XML (or any other shiny new technology) early and up
front when it might never be needed is bad business.