W3C home > Mailing lists > Public > public-ws-chor-comments@w3.org > August 2005

RE: W3C WS-Choreo WG - Issue 973

From: Martin Chapman <martin.chapman@oracle.com>
Date: Wed, 3 Aug 2005 20:46:11 +0100
To: "'Bjoern Hoehrmann'" <derhoermi@gmx.net>
Cc: <public-ws-chor-comments@w3.org>
Message-ID: <00bb01c59864$01a29170$0901a8c0@ie.oracle.com>

Well I can define an extension called "foo" and in the description of
foo it could redefine the semantics of something in the cdl namespace.
For example "foo should be used instead of perform and its behaviour is
not to invoke the indicated choreography".  This would not be allowed as
it contradicts the specs definition of perform.

Does this help?


>-----Original Message-----
>From: public-ws-chor-comments-request@w3.org 
>[mailto:public-ws-chor-comments-request@w3.org] On Behalf Of 
>Bjoern Hoehrmann
>Sent: Wednesday, August 03, 2005 8:35 PM
>To: Martin Chapman
>Cc: public-ws-chor-comments@w3.org
>Subject: Re: W3C WS-Choreo WG - Issue 973
>* Martin Chapman wrote:
>>We discussed 973 on our con call last night: 
>>The group felt that putting an example in that showed an extension 
>>contradicting the specification was not appropraite (like a negative 
>>test). However, the group did agree to put such an example in the 
>>primer, which is currently being drafted.
>Again, my main concern is that
>  Extensions MUST NOT contradict the semantics of any
>  element or attribute from the WS-CDL namespace.
>I do not understand how an extension can "contradict the 
>semantics" of other elements or attributes. The best 
>interpretation I can come up with is that this means 
>processing by implementations that support the extension must 
>be equivalent to processing by implementations that do not 
>support the extension. That's not really different from 
>prohibing extensions.
>Björn Höhrmann · mailto:bjoern@hoehrmann.de · 
>http://bjoern.hoehrmann.de Weinh. Str. 22 · >Telefon: 
>+49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim 
>· PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 3 August 2005 19:45:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:46:25 UTC