RE: [xml-dev] RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange

From
Len Bullard <>
To
"'Costello, Roger L.'" <>,
Date
2007-12-31T15:46:33Z
ID
<000001c84bc4$53202d30$f104b4d8@c4u6h3>
Thread
RE: [xml-dev] RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
Umm..  cool but you just restated pretty much the nut of the discussions for
the design of XML originally.  Was there a point to that other than to beg
the use of semantic web tech for web services?

A lot of applications don't need it.

May I assume that the entire focus of this is not versioning for data
exchange, but versioning for applications implemented AS web services where
the definition of web services has X Y and Z components?

len


From: Costello, Roger L. [mailto:] 

A web service may also make artifacts available to clients to assist
them with "understanding what they get":

(a) A document (or documents) to help clients understand the data they
retrieve

There are many technologies to achieve this, including prose (i.e.
create a web page that client developers can read), data dictionary,
RDF/S, OWL.