This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Back to bug 2360
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| martin.chapman | 2005-12-12 11:38:51 UTC | Status | NEW | ASSIGNED |
| Summary | 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 | 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 |
Back to bug 2360