This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
2.4.8--2.4.10. Exception-Finalization. Cannot see why finalizer blocks etc. should not combine in them corresponding workunits --- the latter seem rather redundant in semantics (and examples). As far as I read, no repetition etc. seems possible in these blocks.
agreed on con call 15-feb-05: requires clarification from issue raiser (Kohei Honda). Action on Gary to followup
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0035.html Proposal from Gary Brown: Although I have asked Kohei for clarification on this, I actually think the text in the issue is pretty clear: http://www.w3.org/Bugs/Public/show_bug.cgi?id=1102. "Cannot see why finalizer blocks etc. should not combine in them corresponding workunits --- the latter seem rather redundant in semantics (and examples). As far as I read, no repetition etc. seems possible in these blocks." He is saying why is only a workunit permitted inside a finalizerBlock? I can see no valid reason for this restriction, so I propose that we change this to be an 'activity'. The only changes I can see are in section 2.4.5: 1) Syntax to change from <finalizerBlock name="ncname" > WorkUnit-Notation </finalizerBlock> to <finalizerBlock name="ncname" > Activity-Notation </finalizerBlock> 2) Last paragraph in that section - suggested change would be to remove the sentence that talks about the workunit. 3) Obviously the schema would need to be updated The examples in 2.4.10 could be updated, but they are still valid using workunits. Regards Gary
resolution agreed on 26th april 2005: http://www.w3.org/2002/ws/chor/5/04/26-minutes.html
In section 2.4.5 Choreographies changed WorkUnit-Notation to Activity-Notation in FinalizerBlock in the syntax. Changed last para from: The OPTIONAL finalizerBlock element defines a Finalizer Block for a Choreography. A Choreography MAY have more than one Finalizer Blocks. Each Finalizer Block specifies one Finalizer Work Unit using a WorkUnit-Notation. If a Choreography defines more than one Finalizer Blocks, then each MUST be differentiated by a distinct name as specified with the name attribute within the finalizerBlock element. To: The OPTIONAL finalizerBlock element defines a Finalizer Block for a Choreography. A Choreography MAY have more than one Finalizer Block. Each Finalizer Block specifies one Finalizer Activity using a Activity-Notation. If a Choreography defines more than one Finalizer Block, then each MUST be differentiated by a distinct name as specified with the name attribute within the finalizerBlock element. In 2.4.9 Choreography FinalizationChanged: The actions within the Finalizer Work Unit MAY use Variable information visible in the Visibility Horizon of the Choreography it belongs to as they were at the time the Choreography completed for the Variables belonging to this Choreography and as they stand at the current time for the Variables belonging to the enclosing Choreography. The actions of a Finalizer Work Unit MAY fault. To: The actions within the Finalizer Activity MAY use Variable information visible in the Visibility Horizon of the Choreography it belongs to as they were at the time the Choreography completed for the Variables belonging to this Choreography and as they stand at the current time for the Variables belonging to the enclosing Choreography. The actions of a Finalizer Activity MAY fault. In the schema changed: <complexType name="tFinalizer"> <complexContent> <extension base="cdl:tExtensibleElements"> <sequence> <element name="workunit" type="cdl:tWorkunit"/> </sequence> <attribute name="name" type="NCName" use="required"/> </extension> </complexContent> </complexType> to: <complexType name="tFinalizer"> <complexContent> <extension base="cdl:tExtensibleElements"> <sequence> <group ref="cdl:activity"/> </sequence> <attribute name="name" type="NCName" use="required"/> </extension> </complexContent> </complexType>
group notification of status change: http://lists.w3.org/Archives/Member/member- ws-chor/2005Jul/0004.html
no comments from group so closed confirmed: http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/0004.html