- From: Amelia A. Lewis <alewis@tibco.com>
- Date: Wed, 01 Oct 2003 09:32:31 -0400
- To: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Cc: Roberto.Chinnici@Sun.COM, jmarsh@microsoft.com, www-ws-desc@w3.org
On Wed, 01 Oct 2003 08:53:53 +0600 Sanjiva Weerawarana <sanjiva@watson.ibm.com> wrote: > NOTE: I changed the subject to reflect the on-going discussion. > > > I still support your original position, hence I disagree with making > > this pattern normative. How about the compromise of having the > > pattern Amy proposes in a non-normative appendix to the patterns > > spec? We define it properly, assign it a URI, use it to elucidate > > the patterns framework, make it available for anybody to use it (if > > they have a binding for it, that is), but it's *not* normative. > > I think this is ok .. and basically this is all we can do for any > patttern. It is however normative to the point that if someone > uses that pattern URI then the semantics MUST be exactly as specified. > Beyond that there's no real "normativeness" for pattern URIs. Some > patterns will of course get exercised in bindings we do (i.e., the > bindings will only be applicable to those patterns), but that's as > far as it goes. > > I suggest we take this approach for all patterns which are not > used directly in the spec. This seems like a reasonable compromise > between not supporting unused patterns and propertly documenting > and naming specific patterns which people find useful. Sounds good to me. I'll submit a couple of patterns that I think are of interest for pub/sub, one of which I think also has application for things like choreography. Probably not today, though, but this week. Amy! -- Amelia A. Lewis Architect, TIBCO/Extensibility, Inc. alewis@tibco.com
Received on Wednesday, 1 October 2003 09:38:15 UTC