RE: [ws-caf] bug 135 - participating services list

[Mark Little <Mark.Little@arjuna.com>]

At this stage in WS-Context I have to agree. I don't see the harm in leaving 
in an optional element. We can add some appropriate text to the spec. to 
ensure that the field is documented, and perhaps enhance the primer.

Mark.

>===== Original Message From "Newcomer, Eric" <Eric.Newcomer@iona.com> =====
>Peter,
>
>No, I disagree.  It can be easily defined, that is, as a reference point for 
other services to find the list of other participating services.  It is an 
optional element in any case and therefore does not represent a problem in the 
spec.
>
>Eric
>
>-----Original Message-----
>From: Furniss, Peter [mailto:Peter.Furniss@choreology.com]
>Sent: Tuesday, June 29, 2004 12:56 PM
>To: ws-caf@lists.oasis-open.org
>Subject: [ws-caf] bug 135 - participating services list
>
>
>I would like to formally propose, as a resolution of bug 135, that the 
participating-services-list element be removed from the WS-Context document 
and schema.
>
>http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=135
>
>As I think the discussion on this has shown, appreciable additional 
specification is required to make it work, and that specification would want 
to constrain the general flexibility of ws-context. It should therefore be 
considered as a candidate for a "referencing specification", and not part of 
the base ws-context.
>
>
>Peter
>
>------------------------------------------
>Peter Furniss
>Chief Scientist, Choreology Ltd
>web: http://www.choreology.com <http://www.choreology.com/>
>email: peter.furniss@choreology.com
>phone: +44 870 739 0066
>mobile: +44 7951 536168