[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
RE: [xml-dev] RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
- From: "Len Bullard" <cbullard@hiwaay.net>
- To: "'Costello, Roger L.'" <costello@mitre.org>, <xml-dev@lists.xml.org>
- Date: Mon, 31 Dec 2007 09:46:33 -0600
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:costello@mitre.org]
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.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]