Minutes WS Choreography WG conference call 1 August 2006
Agenda: http://lists.w3.org/Archives/Public/public-ws-chor/2006Aug/att-0003/agenda0801-0.txt
Scribe: Martin.
Roll Call: Martin, Monica, Gary, Steve
Minutes previous meeting:
http://lists.w3.org/Archives/Member/member-ws-chor/2006Aug/att-0000/minutes-20060718-0.txt
minutes approved
Action:
1. ACTION: Provide examples in primer for issue 1503 of how to use lists/arrays - bounded and unbounded
NO PROGRESS.
2. ACTION: Add text in primer to explain interaction lifecycle, and that exchanges are only guaranteed if align=true.
NO PROGRESS.
3. ACTION: SRT Describe Connectedness/Strong Connectedness design patterns in CDL
NO PROGRESS.
4. ACTION: Martin to follow up with Nick about recursion
Email sent, no response.
CLOSED
5. ACTION: MC to chase CB on test examples
NO PROGRESS
6. ACTION: SRT to follow up with Cambs Univ impl.
NO PROGRESS.
7. ACTION: SRT to check next week on latter part of Sept for F2F dates.
decided week of 25th september, exact days tbd.
CLOSED
8. ACTION: SRT to Write up the summary of the problem (Participants/Roles).
sent: http://lists.w3.org/Archives/Public/public-ws-chor/2006Aug/0002.html
CLOSED
Primer status:
no change
Exit examples:
no progress.
Formal semantics:
paper (in Tex format) been sent and awaiting formatting to HTML
steve forwarding pdf version to list as well.
Implementation status
Imperial college will start to implement after summer holidays
Issue:
issue 3106: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3106
Gary: There are workarounds so proposal is to deffer this to next version of ws-choreography
Gary makes formal proposal
proposal agreed. Martin to make issue as deferred
Gary will raise a new issue related to channel passing example
NEW ACTION: Gary to raise a new issue related to channel passing example
NEW ACTION : Put issue 3105 on the Agenda for next week.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3105 for agenda next week
Issue 3107: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3107 Multipart variable with single part
Proposal: http://lists.w3.org/Archives/Public/public-ws-chor/2006Jul/0006.html
Monica, same way as BPEL does it.
Proposal accepted
Issue 3108: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3108 Activity names
Proposal: http://lists.w3.org/Archives/Public/public-ws-chor/2006Jul/0008.html
gary propses to add a mandatory name attribute to silentaction
monica, look at the broader context, not sure it should be mandatory
steve, in code generation need to indeintify where code gets inserted on a silentaction
monica, if there is no roletype we have to qualify if its the same silent action across board
in the absense of a roletype we should not assume the same "silent" behaviour is happening at each partner <scribe> i.e. the same code generation
<steve_> The mandatory attribute name for a silent action in no way implies that the behavior of a silent action situated at different roles will be the same. A silent action's behavior is undefined in all cases.
<m2> The mandatory attribute name for a silent action in no way implies that the behavior of a silent action situated at different roles will be the same. A silent action's behavior is undefined in all cases.
<m2> The mandatory attribute name for a silent action in no way implies that the behavior of a silent action situated at different roles will be the same. A silent action's behavior is undefined in all cases.
Martin proposes:
The name attribute is used to specify a name for each silent action
declared within a choreography. Regardless of the roletype, there is no implication that the behavior of the silent action will be the same. In all cases, a silent action's behavior is undefined.
Proposal accepted.
other activities that dont have names are: sequence
choice
parallel
perform
assign (although the copy elements do)
noAction
Agreed to leave these activities nameless as we can't think of solid usecases
Mark 3108 as resolved/fixed
Issue 3109: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3109 hasExchangeOccurred
Garry proposes to defer to the next verstion of choreo as there is a workaround.
Agreed to defer to version 2. mark as resolve/remind
Issue 3110: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3110 description element
Proposal: http://lists.w3.org/Archives/Public/public-ws-chor/2006Jul/0007.html
proposal to allow zero or more description element as opposed to currently an optional description.
monica, do we need to say that when multiple descripions are present there is no additional semantics in ordering etc
Add this mutiple documentation and some clarification to the primer
NEW ACTION: SRT keep primer up to date with CR issue resolutions/schema changes.
Proposal accepted. mark issue 3110 as resolved-fixed
Issue 3111: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3111 Recursive performs
Proposal: http://lists.w3.org/Archives/Public/public-ws-chor/2006Jul/0009.html
remove the paragrapgh that dissallows recursion.
proposal accepted. mark 3111 as resolved fixed
three new issues to be added to db
Participants without roles (now issue 3568)
GARY: http://lists.w3.org/Archives/Public/public-ws-chor/2006Jun/0008.html
MATTHEW RAWLINGS: http://lists.w3.org/Archives/Public/public-ws-chor/2006Jun/0001.html
STEVE ROSS-TALBOT: http://lists.w3.org/Archives/Public/public-ws-chor/2006Aug/0002.html
It is impossible to compare QNames (now issue 3569)
http://lists.w3.org/Archives/Public/public-ws-chor/2006May/0011.html
Name and optional query for TokenLocator (now issue 3570 and 3571)
http://lists.w3.org/Archives/Public/public-ws-chor/2006Aug/0000.html
discuss: Name and optional query for TokenLocator
issues 3570: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3570 and
Proposal in: http://lists.w3.org/Archives/Public/public-ws-chor/2006Aug/0000.html
Agreed to 2) of proposal to add optional name. Mark as resolved fixed.
issue 3571: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3571
Proposal 3) in http://lists.w3.org/Archives/Public/public-ws-chor/2006Aug/0000.html
make the query attribute optional
gary, making it optional means that people can define choreo without having to go to minute levels of details. could be usefull as an interchange format e.g. between bus analyst
martin, don't like the way this is being done, better to define profiles with explicit rules like abstract bpel
srt, hold off on this for the moment.
martin will log this as a separate issue and keep it open (done)
Issue 3568: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3568
Participants without roles:
srt observes that in order to fix this we have to revise every element that uses roletype and this may be a huge job.
Its also not clear what the implication is on the type system.
Such a change could send us back to last call
Gary lot of uses cases can use cdl as is, but some recent ones would benefit from the change
General agreement that we don't want to go back to LC
Leave open to give someone the opportunity to propose a minimum impact (i.e. no LC implication) proposal
<scribe> if no proposal is forthcoming we will defer this to the next version
AOB:
none,
meeting adjorned
Summary of Outstanding Actions:
1. ACTION: Provide examples in primer for issue 1503 of how to use lists/arrays - bounded and unbounded
2. ACTION: Add text in primer to explain interaction lifecycle, and that exchanges are only guaranteed if align=true.
3. ACTION: SRT Describe Connectedness/Strong Connectedness design patterns in CDL
4. ACTION: MC to chase CB on test examples
5. ACTION: SRT to follow up with Cambs Univ impl.
6. NEW ACTION: Gary to raise a new issue related to channel passing example
7. NEW ACTION : Put issue 3105 on the Agenda for next week.
8. NEW ACTION: SRT keep primer up to date with CR issue resolutions/schema changes.