RE: [wsbpel] Issue - 296 - Make propertyAlias query element qualified in examples

["Mark Ford" <mark.ford@active-endpoints.com>]

Here are both examples from Section 8.2.6:

<propertyAlias propertyName="p:price" 
               messageType="my:POMsg" part="poPart">
    <query>price</query> 
</propertyAlias>

<propertyAlias propertyName="p:goldCustomerPrice" 
      messageType="my:POMsg" part="poPart">
    <query>(/p:po/price * 0.9)</query> 
</propertyAlias>

We don't provide a definition for the message or its part but the data may
look like this:

<p:po>
  ...
  <price>100</price>
  ...
</p:po>

Of course, <price> could be qualified depending on the schema but in this
case I think it's best to leave it unqualified so as not to confuse the
reader with the price element and the price property.


-----Original Message-----
From: Thomas Schulze [mailto:ThomasSchulze@de.ibm.com] 
Sent: Tuesday, June 06, 2006 2:42 AM
To: wsbpel@lists.oasis-open.org
Subject: Re: [wsbpel] Issue - 296 - Make propertyAlias query element
qualified in examples

+1

We should also add a namespace prefix to the XPath query expression in your
second example?

<bpel:propertyAlias propertyName="p:price" messageType="my:POMsg"
part="poPart">
   <bpel:query>
      p:price        <--- here
   </bpel:query>
</bpel:propertyAlias>

Best regards/Mit freundlichen Grüßen,

       Thomas Schulze



                                                                           
             ws-bpel issues                                                
             list editor                                                   
             <peter.furniss@er                                          To 
             ebor.co.uk>               wsbpel@lists.oasis-open.org         
                                                                        cc 
             05.06.2006 22:33                                              
                                                                   Subject 
                                       [wsbpel] Issue - 296 - Make         
             Please respond to         propertyAlias query element         
             wsbpel@lists.oasi         qualified in examples               
                s-open.org                                                 
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




This issue has been added to the wsbpel issue list with a status of
"received". The status will be changed to "open" if a motion to open the
issue is proposed and that motion is approved by the TC. A motion could also
be proposed to close it without further consideration. Otherwise it will
remain as "received".


The issues list is posted as a Technical Committee document to the OASIS
WSBPEL TC pages on a regular basis. The current edition, as a TC document,
is the most recent version of the document entitled in the "Issues" folder
of the WSBPEL TC document list - the next posting as a TC document will
include this issue. The list editor's working copy, which will normally
include an issue when it is announced, is available at this constant URL.
Issue - 296 - Make propertyAlias query element qualified in examples


Status: received
Date added: 5 Jun 2006
Date submitted: 01 June 2006
Submitter: Mark Ford
Description: The current draft of the spec (rev 1.157) contains some
examples of propertyAlias elements along with a pseudo schema. In these
examples and pseudo schema the query child element is not namespace
qualified. It should be in the same namespace as the parent element
according to the current version of the schema. I realize that there may be
some changes an upcoming issue that will address Global Elements and the
namespace to use for propertyAlias, property and partnerLinkType elements
but it's worth updating these examples now since they might get missed
later.


I found this issue on the following lines: 1598, 1604, 1624, 2149, 2156 in
revision 1.157 of the spec.


Here's an example:

<bpel:propertyAlias propertyName="tns:taxpayerNumber"
        messageType="txmsg:taxpayerInfoMsg"
        part="identification">
   <query>
      txtyp:socialsecnumber
   </query>
</bpel:propertyAlias>



Also, the examples at lines 2149 and 2156 are missing the bpel prefix from
the propertyAlias elements.


Here's an example:

<propertyAlias propertyName="p:price"
               messageType="my:POMsg" part="poPart">
   <query>price</query>
</propertyAlias>




Submitter's proposal: My proposal is to add the missing bpel prefix to the
<propertyAlias> and <query> elements.
Changes: 5 Jun 2006 - new issue



To comment on this issue (including whether it should be accepted), please
follow-up to this announcement on the wsbpel@lists.oasis-open.org list
(replying to this message should automatically send your message to that
list), or ensure the subject line as you send it starts "Issue - 296 -
[anything]" or is a reply to such a message. If you want to formally propose
a resolution to an open issue, please start the subject line "Issue
- 296 - Proposed resolution", without any Re: or similar.


To add a new issue, see the issues procedures document (but the address for
new issue submission is the sender of this announcement).


--------------------------------------------------------------------- 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