W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2001

RE: NameValue and NameValueList data types

From: Jorgen Thelin <Jorgen.Thelin@capeclear.com>
Date: Thu, 20 Dec 2001 16:07:07 -0000
To: "'Rich Salz'" <rsalz@zolera.com>
Cc: <xml-dist-app@w3.org>
Message-ID: <000001c18970$6088b900$2902a8c0@SERENA>


> -----Original Message-----
> From: Rich Salz [mailto:rsalz@zolera.com] 
> Sent: 20 December 2001 14:06
> To: Jorgen Thelin
> Cc: xml-dist-app@w3.org; 'Jacek Kopecky'; Peter Hendry
> Subject: Re: NameValue and NameValueList data types
> 
> 
> > The problem we (as an industry) have is that until we 
> standardize the 
> > representation of a name-value list, we will never achieve any true 
> > interoperability of such a fundamental programming language 
> construct 
> > as name-value pairs.  An "Apache standard" for this type 
> > representation is not going to provide this
> 
> The success of Apache as a de-facto standard argues strongly 
> otherwise.

For the Java representation maybe, but what about .NET, Perl, Python,
Smalltalk, etc, etc, etc?

At the end of the day, Apache is not, and I am sure would not want to
be, a standards making body.  The current Apache "standard" for this
name-value representation is driven by pragmatism to exercise this area,
but I don't think anyone would claim this is a real long term solution.
"Just tough it out and make the rest of the industry fall in line" will
not work.

I am not disparaging the efforts of the Apache community, just pointing
to the fact that without a single standard for the representation of
name-value pairs that *everyone* can agree to, we cannot get beyond the
problem of having at least two "Walled Camps" which I had thought this
industry had finally matured past.  :-(
Received on Thursday, 20 December 2001 11:07:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 22:28:13 UTC