This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2360 - Section 4.2 says: A relationshipType identifies the roleTypes and behaviors, where mutual commitments between two parties MUST be made for collaborations to be successful. However, you indicate in Section 3.1 that relationshipType MAY only be used in ...
Summary: Section 4.2 says: A relationshipType identifies the roleTypes and behaviors, ...
Status: ASSIGNED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Primer (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: Greg Ritzinger
URL: http://lists.w3.org/Archives/Member/m...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-18 19:31 UTC by Greg Ritzinger
Modified: 2005-12-12 11:38 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2005-10-18 19:31:35 UTC 
Section 4.2 

says: 
A relationshipType identifies the roleTypes and behaviors, where 
mutual 
commitments between two parties MUST be made for collaborations to be successful. 

 However, you indicate in Section 3.1 that relationshipType MAY only 
be used in a choreography package even though I don't see 
relationshipType 
as optional. How do you implement the requirement in Section 4.2? 

Steve notes: having relationships from a usage perspective alone, has been 
very useful. It has resulted in me making less mistakes in creating a large CDL 
with many channels and many relationships.
Comment 1 Martin Chapman 2005-12-12 11:38:51 UTC 
12 dec 05 f2f: explain the rationale and constaints introduced by using a 
relationship type
Comment 2 Greg Ritzinger 2008-06-05 13:24:54 UTC 
The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:

Section 4.2 says: A relationshipType identifies the roleTypes and behaviors, where mutual commitments between two parties MUST be made for collaborations to be successful.  However, you indicate in Section 3.1 that relationshipType MAY only be used in a choreography package even though I don't see relationshipType as optional. How do you implement the requirement in Section 4.2? Steve notes: having relationships from a usage perspective alone, has been very useful. It has resulted in me making less mistakes in creating a large CDL with many channels and many relationships. Make the primer talk about the mutual commitement