Minutes WS Choreography WG conference call 27 September
2005
See also: IRC log: http://www.w3.org/2005/09/27-ws-chor-irc
1. Attendees:
Monica, Gary, Nick, Abbie, Greg, Tony, Jeff, Steve, Martin, Charlton
Regrets: Yves
2. Scribe
Martin
3. Agenda:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Sep/att-0023/Agenda20050927-0.txt
no changes to agenda
4. Minutes
20th September 2005
http://lists.w3.org/Archives/Member/member-ws-chor/2005Sep/att-0073/minutes-20050920-0.txt
srt proposed to accept, MC 2nd. noobjections. minutes approved
5. Action Items
1. ACTION: for the group to review on the latest CDL editors draft
Done
2. ACTION: SRT will send urls to all docs to WG
Done
3. ACTION: Editors to make change for first proposal as per proposal in http://lists.w3.org/Archives/Public/public-ws-chor/2005Sep/0015.html
Done
4. ACTION: Editors to make change for Yves proposal as above
Done
5. ACTION: Nick to ask Martin on F2F and Oracle in London
Done - venue reserved in London for 12-14 Dec. Will confirm f2f details next call.
6. ACTION: SRT to check Brighton as venue
not done
6. CR discussion:
snapshot:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Sep/0022.html
Garys comments:
http://lists.w3.org/Archives/Member/member-ws-chor/2005Sep/0069.html
Status of the document section:
2nd para: " Comments can be sent until 31 October 2005 " - shouldn't
this
now be end of November? or December?
agreed 31st december 2005
NEW ACTION: Editors to update status section to change date to 31st Dec 05
Section 1.5:
2nd para: " may couple with other languages such those that add
further computable semantic definitions. " needs an 'as' before 'those'
Becomes 2nd para: " may couple with other languages such as those that add
further computable semantic definitions. "
agreed add the "as"
NEW ACTION: Editors to update 2nd para of 1.5 as agreed 27/9
Section 5.5:
11th para: " A choreography can also be coordinated. CCChoreography
coordination " - CCC
agreed fix typo
NEW ACTION: Editors to update 5.5 to as agreed 27/9
Section 6.2.3:
Last bullet before the example - "badPOAckType" should be "badPOAck"
The exchange "badPurchaseOrderAckException" specifies that an
exception type of "badPOAckType" could occur at both participants
BECOMES: "The exchange "badPurchaseOrderAckException" specifies that an
exception "badPOAck" could occur at both participants"
<nick> +1
<Gary> +1
agreed
NEW ACTION: Editors to update 6.2.3, as agreed 27/9
Section 6.7 Finalize:
The example has 'perform' activities with the 'choreographyInstance'
attribute, but should be 'choreographyInstanceId'.
change first two performs
agreed
NEW ACTION: Editors to update 6.7, to chang the first two perfoms as agreed 27/9
Jeff's comments:
http://lists.w3.org/Archives/Member/member-ws-chor/2005Sep/0074.html
section 2:
change the following bullets
.activities and ordering structures - Activities describe the actions performed within a choreography
.Ordering structures combine activities with other ordering structures in a nested structure to express the ordering rules of actions performed within a choreography
Agreed to combine the two bullet points
NEW ACTION: Editors to update section 2, activitiy and ordering bullet points, as agreed 27/9
section 5.5, 2nd para:
Change:
A choreography package MAY contain exactly one top-level
choreography, marked explicitly as the root choreography.
to:
A choreography package MUST contain zero or one top-level
choreography, marked explicitly as the root choreography.
agreed
NEW ACTION: Editors to update 2nd para of 1.5 as agreed 27/9
general comment: jeff doesnt like the use of the word usage instead of use;)
NEW ACTION: Editors: In 4.3 the first paragraph is in italic, change to normal font.
Section 4.3:
logical/abstract is meaningless and un-testable
from:
A participantType groups together those parts of the observable
behavior that MUST be implemented by the same logical entity or abstract
organization.
to:
A participantType groups together those parts of the observable
behavior that MUST be implemented by a participant.
agreed
NEW ACTION: Editors to change 4.3 as agreed 27/9
Monicas comments:
3.2 2nd para. lowercase the SHOULD
agreed
NEW ACTION: Editors lowercase the SHOULD in 3.2 as agreed 27/9.
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
NEW ACTION: add new issue to discuss mutual commitement in the Primer.
Section 4.4
These corrections don't direct relinquishing/not relinquishing
control:
"once" - MUST relinquish
"distinct"- MUST relinquish
"shared" - no requirement unless we say MUST NOT
We agreed the above at our meeting on 18 Aug, so editors missed this one:
http://www.w3.org/2002/ws/chor/5/08/18-minutes.html
NEW ACTION: Editors to update the snapshot to use the must/must not wording for
relinquishing control from 18th aug
NEW ACTION: Editors: In 4.4, insert bullets in front of once, distrinct, shared
Section 4.4
change:
The OPTIONAL attribute action within the passing element, defines
when a channel instance will be passed,
to:
The OPTIONAL attribute action within the passing element, defines
when a channel instance MUST be passed,
Agreed
NEW ACTION: Editors to update 4.4 as agreed 27/9.
SECTION 4.4 on Derived Usage
Change from:
The OPTIONAL attribute action within the passing element, defines when
a Channelchannel instance will be passed, either during a request
exchange, during a response exchange or both. The default value for this
attribute is set to"request".
Change to:
The OPTIONAL attribute action within the passing element, defines when
a channel instance MUST be passed, either during a request
exchange, during a response exchange or both. The default value for this
attribute is set to"request".
agreed
NEW ACTION: Editors to update 4.4 to add MUST to passing attribute, as agreed 27/9.
More Monica comments
http://lists.w3.org/Archives/Member/member-ws-chor/2005Sep/0076.html
Section 5.2
change:
The OPTIONAL attribute mutable, when set to "false", specifies that the
variable information cannot change once initialized.
to:
The OPTIONAL attribute mutable, when set to "false", specifies that the
variable information MUST NOT be changed once initialized.
agreed
NEW ACTION: Editors to update 5.2 to add MUST NOT to mutable attribute, as agreed 27/9.
Section 5.4
Change from:
The attribute tokenName identifies the name of the token
that the document fragment locator is associated with.
Change to:
The attribute tokenName identifies the name of the token of
which the document fragment locator is associated.
agreed
NEW ACTION: Editors to update 5.4 to remove "with" from end of sentence.
no more comments
Steve aks the group whether, with the above changes to the snapshot, we should move this specification to CR.
<nick> 1million +1
<charlton> +1 emphatically
<SRT> +1
<Gary> +1
<abbie> abbie +1
<gritzinger> +1
<MChapman> +1
<abbie> +1
<m2> +1
No objections to moving to CR recorded
Group agrees to move to CR
7 AOB
Next F2F: provisional booking in london. confirm details next week
bpel been informed of provisional dates
focus on primer in future meetings
Summary of New Actions.
ACTION: Editors to update status section to change date to 31st Dec 05
ACTION: Editors to update 2nd para of 1.5 as agreed 27/9
ACTION: Editors to update 5.5 to as agreed 27/9
ACTION: Editors to update 6.2.3, as agreed 27/9
ACTION: Editors to update 6.7, to chang the first two perfoms as agreed 27/9
ACTION: Editors to update section 2, activitiy and ordering bullet points, as agreed 27/9
ACTION: Editors to update 2nd para of 1.5 as agreed 27/9
ACTION: Editors: In 4.3 the first paragraph is in italic, change to normal font.
ACTION: Editors to change 4.3 as agreed 27/9
ACTION: Editors lowercase the SHOULD in 3.2 as agreed 27/9.
ACTION: add new issue to discuss mutual commitement in the Primer.
ACTION: Editors to update the snapshot to use the must/must not wording for
relinquishing control from 18th aug
ACTION: Editors: In 4.4, insert bullets in front of once, distrinct, shared
ACTION: Editors to update 4.4 as agreed 27/9.
ACTION: Editors to update 4.4 to add MUST to passing attribute, as agreed 27/9.
ACTION: Editors to update 5.2 to add MUST NOT to mutable attribute, as agreed 27/9.
ACTION: Editors to update 5.4 to remove "with" from end of sentence.