Eugene, et al:

You are right to lament the over use of fancy language 
andtheunnecessarystringingtogetherofwords in writing about technology.  We 
deserve plainer talk and please don't let up the fight for it.  However 
terms like 'parse' when used with markup languages and 'vertical markets' 
when used in business systems long preceded XML and are pretty much 
standard parts of the language.

My point about the writer's incorrect use of 'part' instead of 'parse' (and 
other basic inaccuracies) is that it gave the impression of not knowing 
what he was writing about.  He seems to have made a few telephone calls 
then parroted the words given to him by the interviewees, without getting 
more knowledgeable about the subject matter.  To me, that's little more 
than rumor-mongering.  As readers who invest our time and energy and 
sometimes money, we deserve better than that.  Best regards.

Alan Kotok
Director, Education and Information Resources
Data Interchange Standards Association
[EMAIL PROTECTED]
+1 703-518-4174
** DISA's E-Business and Internet Conference, 7-9 March 2001, in San Francisco.
http://www.disa.org/conference/annual_conf/index.htm **




At 01:53 PM 2/2/01 +0800, Eugene Teo wrote:

>Hi all,
>
>One of the complaints of EDI is cost. The way I see it, XML will not be less
>costlier. The amount of initiatives moving this XML is costing money, and
>they would like to make money from it.
>
>Next time you use XML, you'll pay (probably like pay-per-view tv style). To
>parse, you pay for the parser. And eh, my UK parser is not compatible with
>American standards, so I have to buy another parser. And how do I automate
>which parser to use? Buy another piece of software or write my own! To
>translate XML to your old EDI format, you pay again. In the end, we are back
>to step one.
>
>Why do you think the big guys are running after XML? Because they are going
>to make big bucks from it! Who's going to pay for it?
>
>-Eugene
>
>PS. Why XML must come up with so many bombastic terms like
>parse,
>vertical markets,
>interoperatabliticomplicatedwordsalljoinedtogethertomakeitlonganddifficult,
>etc etc???
>
>Whenever I look at XML sites, I develop a big headache because of these
>words. For example, Alan Kotok corrected Steve to use 'parse' instead of the
>common word 'part'. To me, its the same. Why? I just want to cut up a flat
>file into transactions, segments, and fields thats all. Is 'parse' a more
>superior and complicated process? No, I am a programmer and it is all the
>same to me. Give me anything and I'll part, parse or cut for you.
>There is nothing more annoying than people who come up with new terms to
>describe absolutely normal and common processes.
>
>
>
>
>
>------   XML/edi Group Discussion List   ------
>Homepage =  http://www.XMLedi-Group.org
>
>Unsubscribe =  send email to: [EMAIL PROTECTED]
>Leave the subject and body of the message blank
>
>Questions/requests:  [EMAIL PROTECTED]
>
>To receive only one message per day (digest format)
>send the following message to [EMAIL PROTECTED],
>(leave the subject line blank)
>
>digest xmledi-group your-email-address
>
>To join the XML/edi Group complete the form located at:
>http://www.xmledi-group.org/xmledigroup/mail1.htm
>---------------------------------------------------------------------
>Plan on attending the upcoming meeting during DISA's conference:
>http://www.disa.org/conference/annual_conf/index.htm




------   XML/edi Group Discussion List   ------
Homepage =  http://www.XMLedi-Group.org

Unsubscribe =  send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank

Questions/requests:  [EMAIL PROTECTED]

To receive only one message per day (digest format) 
send the following message to [EMAIL PROTECTED], 
(leave the subject line blank) 

digest xmledi-group your-email-address

To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
---------------------------------------------------------------------
Plan on attending the upcoming meeting during DISA's conference:
http://www.disa.org/conference/annual_conf/index.htm


Reply via email to