OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] Issue - 199 - Proposal for Vote (Message Variable NamingScheme)



Hi Yuzo,

Writing the actual spec (delta) text  for Issue 199 that fits and 
applies to Issue 103 proposal text is actually on my TO-DO list for a 
while.

Yuzo ... let's delay the formal voting a bit ... and work together to 
come up with delta text to cover both Issue 199 and Issue 203. And, use 
the formal voting of Issue 199 and 203 to give our detailed text an 
official status.

For Issue 203, I would go for (C) closer to the pre-103 situation. [ 
which was (B) in your 103 email, which Paco likes in general. ]


Regards,
Alex Yiu


Yuzo Fujishima wrote:

> Hi,
>
> I think there are two things to be added to the specification.
>
> 1. Restriction on variable name.
> 2. Definition of the semantics of $variable.part.
>
> As for 1, I propose the following:
>
> In: "9.2. Variables" of the specification draft (27FEB2005)
> After: "The name of a variable should be unique within its own scope."
> Insert: "The name must not contain a comma (".")."
>
> As for 2, I think it should be an essential part of Issue 103
> resolution rather than that of 199. In my opinion, Issue 199 serves as 
> input to the writer(s) of the final resolution of 103 by picking "." 
> as the separator between a variable and a part.
>
> Yuzo Fujishima
> NEC Corporation
>
> Yaron Y. Goland wrote:
>
>> Proposals to vote should have something reasonably close to the 
>> actual language that is going to go into the spec. This proposal 
>> lacks that.
>>
>>
>>     Yaron
>>
>> Yuzo Fujishima wrote:
>>
>>> Hi,
>>>
>>> I move that we adopt the submitter's proposal to solve Issue 199.
>>>
>>> Yuzo Fujishima
>>> NEC Corporation
>>>
>>>
>>> Chris Keller wrote:
>>>  >
>>>  >
>>>  > +1
>>>  >
>>>  >  >
>>>  > * From: * Satish Thatte [mailto:satisht@microsoft.com]
>>>  > *Sent:* Wednesday, March 16, 2005 6:39 PM
>>>  > *To:* Alex Yiu; Yuzo Fujishima
>>>  > *Cc:* wsbpel@lists.oasis-open.org; Yaron Y. Goland
>>>  > *Subject:* RE: [wsbpel] Issue 199: Message Variable Naming Scheme
>>>  >
>>>  >  >
>>>  > I think “.” is perfect.
>>>  >
>>>  >  >
>>>  > * From: * Alex Yiu [mailto:alex.yiu@oracle.com]
>>>  > *Sent:* Wednesday, March 16, 2005 7:54 AM
>>>  > *To:* Yuzo Fujishima
>>>  > *Cc:* wsbpel@lists.oasis-open.org; Satish Thatte; Yaron Y. 
>>> Goland; Alex Yiu
>>>  > *Subject:* Re: [wsbpel] Issue 199: Message Variable Naming Scheme
>>>  >
>>>  >  >
>>>  >
>>>  > Hi Yuzo and others,
>>>  >
>>>  > Just want to supplement info that there is a well-defined 
>>> character sets
>>>  > that we can use within a NCNAME.
>>>  >
>>>  > http://www.w3.org/TR/REC-xml-names/#NT-NCName
>>>  >
>>>  > It looks like "." may be a good choice.
>>>  >
>>>  >
>>>  > Regards,
>>>  > Alex Yiu
>>>  >
>>>  >
>>>  >  >
>>>  >
>>>  >     * Issue 199: Message Variable Naming Scheme *
>>>  >
>>>  > * Status: * received
>>>  > *Date added:* 16 Mar 2005
>>>  > *Categories:* Data handling
>>>  > 
>>> <http://www.choreology.com/external/WS_BPEL_issues_list.html#category_data_handling> 
>>>
>>>  > *Date submitted:* 16 March 2005
>>>  > *Submitter:* Yuzo Fujishima <mailto:fujishima@bc.jp.nec.com>
>>>  > *Champion:* Yuzo Fujishima <fujishima@bc.jp.nec.com>
>>>  > <mailto:fujishima@bc.jp.nec.com>
>>>  > *Document:* Issue 103 resolution
>>>  > *Description:* Since Issue 103 has been resolved without defining
>>>  > concrete naming scheme for message variables, we need a new issue to
>>>  > discuss it.
>>>  >
>>>  > The BPEL issues list lists three candiates:
>>>  >
>>>  > A. $variable.part B. $variable_part C. $variable-part
>>>  >
>>>  > Submitter's proposal: I think candidate C is not viable because 
>>> "-" will
>>>  > be interpreted as the minus operator.
>>>  >
>>>  > Choose candiate A and make it illegal to have "." in variable names.
>>>  > *Changes:* 16 Mar 2005 - new issue
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this mail list, you must leave the OASIS TC that
>>> generates this mail.  You may a link to this group and all your TCs 
>>> in OASIS
>>> at:
>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  You may a link to this group and all your TCs 
>> in OASIS
>> at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]