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

Clarification for Issue 1109 please

From: Tony Fletcher <tony_fletcher@btopenworld.com>
Date: Sat, 19 Mar 2005 18:00:17 -0000
To: <public-ws-chor@w3.org>
Message-ID: <000001c52cad$8587a1b0$6501a8c0@corp.choreology.com>
Dear Colleagues,
 
I would like to request your assistance with respect to editing into the CDL
specification agreements made with respect to Issue 1109 (refer to
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1109)
 
I read the bug and the fact that editorial resolution is proposed to imply
that getVariable can only be used to get the value of a variable at the role
from which it is called.  However, the getVariable function is specified to
have an optional role parameter
<emph>xsd:any getVariable(xsd:string varName, xsd:string part, xsd:string
documentPath, xsd:QName  roleName?) </emph>

Returns the information of the Variable with name <emph>varName</emph> as a
node set containing a single node. The second parameter, <emph>part</emph>,
specifies the message part of a WSDL1.1 document. For a WSDL 2.0 document it
MUST be empty. When the third parameter <emph>documentPath</emph> is empty,
then this function retrieves the entire document from the Variable
information. When it is non-empty, then this function retrieves from the
Variable information, the fragment of the document at the provided absolute
location path. The fourth parameter is OPTIONAL. When the fourth parameter
is used, the Variable information MUST be available at the Role specified by
<emph>roleName</emph>. If this parameter is not used then the Role is
inferred from the context that this function is used.

 

What is the point of the roleName parameter if getVariable can only be used
to a get the value of a variable at the role from which it is called?
 
It seems to me that we should agree
either to remove this parameter and state that getVariable can only be used
to a get the value of a variable at the role from which it is called. In
this case we should go through the specification and make sure all text and
uses of getVariable are consistent with this
or we should leave the definition alone - and probably the text alone as
well - i.e. no change - and accept that it is not defined how the value is
obtained or shared if the roleName points to a different role from the one
which has called the function.
 
Best Regards     Tony
A M Fletcher
 
Cohesions  (TM)
 
Business transaction management software for application coordination
www.choreology.com <http://www.choreology.com/> 
 
Choreology Ltd., 68 Lombard Street, London EC3V 9LJ     UK
Tel: +44 (0) 1473 729537   Mobile: +44 (0) 7801 948219
tony.fletcher@choreology.com     (Home: amfletcher@iee.org)
 
Received on Saturday, 19 March 2005 18:00:50 GMT

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