ISSUES LIST ACTIONS FOR EDITORS EDITORS Issue 937 Editorial EDITORS Issue 943 Editorial EDITORS Issue 945 Editorial EDITORS Issue 561 No - but need to do the editorial work EDITORS Issue 563 Editorial EDITORS Issue 683 Editors EDITORS Issue 724 Editorial and on the list OTHER ACTIONS FOR EDITORS *** New Last call issues section *** Editors to insert in new section of last call issues: "Due to a lack of clarity in existing XML specifications, we are unable at this time to recommend an approach for accessing and modifying members of lists and arrays." *** QoS and Bindings *** ACTION: Editors to * add support to wsdl 1.1 in section 1.4 as "constrianed with ws-i basic profile for compatibility" * add to section 6 "based on these requirement cdl should be composable with btp, wst WS-CAF" * add "ws addressing (W3C Member Submission 10 August 2004)" to clarify member submission *** Issue 691 *** ACTION: Editors to apply http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0066.html to current draft *** Variables and scoping for a participant *** ACTION: Tony will redo test and represent for editors *** Raise/Throw *** ACTION: Editors to include amended proposal below: Proposal http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0057.html Ammendment: Add two new lines before "**The assign activity MAY also be used to cause an exception at a Role.**" and remove the "**". PROPOSAL ADOPTED WITH THE ABOVE AMMENDMENT *** Timeouts and exceptions *** ACTION: editors to implement Charlton's proposal below: http://lists.w3.org/Archives/Public/public-ws-chor/2004Oct/0042.html ACTION: editors to implement amended proposal, base being http://lists.w3.org/Archives/Public/www-archive/2004Nov/att-0025/Timeout_exception.pdf * May also need to change xsd:deadline to xsd:datetime. * May also need to allow XPath expressions that yield either date format as soln to variables * Peters ammendment: change where timeout proposal fromRoleRecordReference="ncname", toRoleRecordReference="ncname" to instead each reference a list of ncnames... proposal, contd - and have only one record raise the exception - remove "at most one record elements may be specified..." *** Variables *** ACTION: Editors to incorporate proposal on issue 691 (variables) http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0066.html *** Choreology proposal 1 *** Title: Coordinated Choreographies Proposal 1 - coordination attribute Base: http://lists.w3.org/Archives/Public/public-ws-chor/2004Oct/0065.html monica: submitted two editorial changes to proposal 1 - both accepted by bob [note: don't know what they are??] ACTION: Editors to apply Proposal 1 which was adopted ACTION: Editors to delete "2. globalizedTrigger()" paragraph and align 3. in proposal 1 *** Choreology proposal 3 *** Title: Coordinated Choreographies Proposal 3 - Multiple Finalizers Base: http://lists.w3.org/Archives/Public/public-ws-chor/2004Oct/0066.html Other than couple of editorials items and reference to a couple of things which refer to other issues: isolation and finalizers, 2.4.7. add for lifeline Amendment: Paragraph in proposal 3 "The finaliser workunits are enabled only after the Choreography..." I think this is the third from the end. - remove it ACTION: Editors to apply amended Proposal 3 which was adopted. *** Choreology proposal 4 *** Title: Corrected Coordinated Choreographies Proposal 4 - Finalize Activity Base: http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0003.html Amendment 1 from Peter: http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0072.html Amendment 2 from Peter: http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0073.html Amendment 3 from Steve: FULL TEXT to that ammendment should be "The Finalize activity is used to enable one or more finalizers in particular instances of immediately inner choreographies which have defined finalizers, and thus bring those choreographies to a defined conclusion" Amendment 4 from various: agreed to rename "choreographyInstance" to "choreographyInstanceId" agreed to rename "subChoreographyInstance" to "choreographyInstanceId" Type of attribute above is to be "XPath expression/xsd:String" ACTION: Change the second paragraph, should be "A Choreography SHOULD have at least one finalize element..." ACTION: Peter to consolidate the rules in proposal 4 ACTION: Editors to apply amended proposal 4 which was adopted. RESOLUTION: we have agreed in principle to these changes as captured in the action and associated details and ask Choreology to redraft in accordance with agreed changes. NOTE: Don't forget that the choreographyInstanceId on a perform is optional, i.e. a "?" is placed after it in the psuedo schema NOTE: Otherwise, it is required and the value MUST be different for each instance of the named Choreography which is performed. If the performed Choreography can only be performed once within the enclosing choreography, the subChoreographyInstanceId attribute is optional. Couldn't figure out if these are editing instructions or not. *** Extending Choreographies Proposal 6 *** Title: Coordinated Choreographies Proposal 6 - Extending Choreographies Base: http://lists.w3.org/Archives/Public/public-ws-chor/2004Oct/0068.html ACTION: editorial - add a note to the Last Call section regarding this proposal to the status section: indicating that we are working on this proposal, it is not finalized as of yet, and we do not believe it will have a major impact on the architecture *** Back to proposal 1 *** Title: Coordinated Choreographies Proposal 1 - coordination attribute Have not captured all edits to this one just yet .... ***Updated Life Line Completion Proposal*** Title: Choreography lifeline Proposal (was RE: Proposal: To remove the initiate flag on the Interation) Base proposal is http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0056.html * Replace "once" with "when" in paragraph four of the proposal above * In paragraph three change line six to: "The complete condition MUST be possible to match the condition in all roles participating in the choreography" * change last two sentences in paragraph 3 to the new text below: "When a choreography completes all uncompleted enclosed choreogrphies will automatically become complete" * note this text (presumably the bit above) is to replace the last two sentences in paragraph 3 * Change "enabled" to "installed' in peter's addition * Insert the finalize complete paragraph at the end of the life line section * Add to lifeline section: "Messages that were sent as part of a choreography that has since completed must be ignored." *** Isolation *** ACTION: Editors to update Section 2.4.5 isolation='true', ... default is false. See notes for more details. ACTION: Editors to reword the semantics of isolation=true. "Changes to ... the variable information MUST only be visible aftger the ... choreography has completed."