[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: RE: Caution using XML Schema backward- or forward-compatib

• From: "bryan rasmussen" <rasmussen.bryan@g...>
• To: "Costello, Roger L." <costello@m...>
• Date: Sun, 30 Dec 2007 09:55:26 +0100

I'll put in that Schematron is useful for specifying more than just
co-constraints when one is talking about compatibility, it could be
used as technical documentation as to compatibility axis of various
elements.

Cheers,
Bryan Rasmussen
On Dec 30, 2007 3:30 AM, Thomas Lord <lord@e...> wrote:
> Costello, Roger L. wrote:
> > I think that for a client to be able to utilize a web service, the web
> > service must specify three things:
> >
> > (1) Syntax of the data that the web service makes available to clients;
> > use a grammar-based language such as XML Schemas, or RELAX NG, or DTD.
> >
> >
>
> Ok.
>
>
> > (2) Relationship constraints (e.g. co-constraints) on the data; use
> > Schematron.
> >
> >
>
> Seems a bit arbitrary.   Why "relationship constraints" of that
> particular form?
> What's your theory, here?   Your claim wasn't that Schematron can be useful
> but that "[in order] for a client to be able to utilize a web service
> [....]" which is
> a remarkably strong claim.
>
>
>
>
> > (3) Semantics of the data; use a data dictionary, or English prose, or
> > RDF/S, or OWL, some combination thereof.
> >
> >
>
> Again, what's your theory?   Some notation that usefully indicates semantics
> seems a good idea, I grant you.   Obviously, also, service has to be
> documented somewhere.
> How did you get from there to "English prose, RDF/S, or OWL, some
> combination thereof"?
>
>
> (2) and (3) suggest investments, presumably with some return.   They
> also suggest
> suggestions competitive with a lot of well developed theory in program
> typing and
> in modeling the semantics of programs.   So, why are the technologies
> and approaches
> you suggest the right choice here?
>
> -t
>
>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>

• Follow-Ups:
  • Re: RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Fraser Goffin" <goffinf@g...>

• References:
  • Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Costello, Roger L." <costello@m...>
  • RE: Caution using XML Schema backward- or forward-compatibilityas a versioning strategy for data exchange
    • From: "Cox, Bruce" <Bruce.Cox@U...>
  • Re: RE: Caution using XML Schema backward- or forward-compatibilityas a versioning strategy for data exchange
    • From: Thomas Lord <lord@e...>
  • RE: RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Costello, Roger L." <costello@m...>
  • Re: RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Fraser Goffin" <goffinf@g...>
  • Re: RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Stephen Green" <stephengreenubl@g...>
  • RE: RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Costello, Roger L." <costello@m...>
  • Re: RE: Caution using XML Schema backward- or forward-compatibilityas a versioning strategy for data exchange
    • From: Thomas Lord <lord@e...>