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

RE: NameValue and NameValueList data types

From: <noah_mendelsohn@us.ibm.com>
Date: Thu, 20 Dec 2001 12:03:00 -0500
To: jacek@systinet.com
Cc: Jorgen.Thelin@capeclear.com, Peter.Hendry@capeclear.com, xml-dist-app@w3.org
Message-ID: <OFC351C409.C4EB58A6-ON85256B28.005E2BC6@lotus.com>
XML Schema faced a similar challenge.  If we put too few types into the 
base core, then we don't provide a very firm foundation for universal 
interoperability.  Support for those built in types is mandatory in schema 
(and now in SOAP).  If we put too many types in the required base spec, 
then the spec gets larger and harder to maintain, and the cost of a 
minimal conforming implementation goes up. 

We in schemas decided to also go for a middle ground solution, in which we 
would prepare a type library specification (see work in progress schema 
document at [1]), which would provide a single point of reference for 
types that didn't quite make it into the core.  The advantage of such an 
approach over relying on scattered organizations like Apache is that it 
provides a focussed point of discussion for interop.  In other words, a 
SOAP implementation can then say:  way support core SOAP plus all types in 
the type library.

Whether NameValueList etc. belongs in the XML Schema type library, or in a 
separte SOAP type library is an interesting question.

[1] http://www.w3.org/2001/03/XMLSchema/TypeLibrary.xsd

------------------------------------------------------------------------
Noah Mendelsohn                                    Voice: 1-617-693-4036
Lotus Development Corp.                            Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------------
Received on Thursday, 20 December 2001 12:14:47 UTC

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