W3C home > Mailing lists > Public > public-ws-chor@w3.org > September 2005

Re: Error in example fragment in 6.2.3

From: Gary Brown <gary@pi4tech.com>
Date: Fri, 2 Sep 2005 09:15:29 +0100
Message-ID: <001101c5af96$7cf4a450$0200a8c0@GPB1>
To: "Nickolas Kavantzas" <nickolas.kavantzas@oracle.com>
Cc: "'WS-Choreography List'" <public-ws-chor@w3.org>
Hi Nick

I am happy with the current restriction that we can only have one variable with a particular name in a var declns section.

If different properties are required of a variable within different roles, then this could easily be resolved by using different variable names. So at the moment I think the best course of action is to just update the example.

Regards
Gary
  ----- Original Message ----- 
  From: Nickolas Kavantzas 
  To: Gary Brown 
  Cc: 'WS-Choreography List' 
  Sent: Friday, September 02, 2005 12:53 AM
  Subject: Re: Error in example fragment in 6.2.3


  Hi Gary,

  you are definitely correct about the example being incorrect with the
  section 5.2 rule (" The attribute name is used to specify a distinct name for each variable declared within the variableDefinitions element. ").

  But IHMO the problem is with the rule itself, since we cannot have two vars, with the same 
  name, defined at 2 roles but one having silent=true and the other not, which may be desired
  in some use-cases.


  Also,  in the last paragraph in section 5.2:

  'In those cases where the variable is shared amongst a subset of roles within a choreography, those roles need to be listed within the definition of the variable as the roleTypes using the attribute roleTypes.',  

  the word subset seems incorrect. I think 'set' is better than 'subset'.


  Best regards,

  --
  Nick
    ----- Original Message ----- 
    From: Gary Brown 
    To: 'WS-Choreography List' 
    Sent: Thursday, September 01, 2005 3:43 AM
    Subject: Error in example fragment in 6.2.3


    Hi

    The example in 6.2.3 Interaction Syntax has two variable declarations of the same name, which is no longer permitted:

      <variable name="badPurchaseOrderAck"   
                informationType="tns:badPOAckType" roleTypes="tns:Consumer"/>
      <variable name="badPurchaseOrderAck"   
                informationType="tns:badPOAckType" roleTypes="tns:Retailer"
                silent="true" />
As it says in section 5.2:" The attribute name is used to specify a distinct name for each variable declared within the variableDefinitions element. " RegardsGary------=extPart_000_
Received on Friday, 2 September 2005 08:15:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:01:41 GMT