Next in thread → Next in month →

Re: [wsbpel-reqts] RE: New Issue - Incomplete XPath expressions in thespecification

From
Diane Jordan <>
Date
2004-02-17T15:51:59+00:00
ID
Thread
Re: [wsbpel-reqts] RE: New Issue - Incomplete XPath expressions in thespecification
Monica,

Assuming this is not a duplicate, I
agree that we should ask if a member would be willing to submit it.  

Kristofer, 

please review issue 46 and let us know
your take on whether its a duplicate.  

Also, please be aware that your membership
status depends on meeting attendance.  You need to attend 2 out of
every 3 meetings to become a member and maintain member status.  This
requirement applies when you are a prospective member (indeed, you will
not be eligible for membership until you've attended 2 out of 3 meetings).

Peter,

Thanks for bringing this up.  

 

Regards, Diane

IBM  Dynamic e-business Technologies



(919)254-7221 or 8-444-7221, Mobile: 919-624-5123

"Monica J. Martin"
<> 

02/17/2004 06:17 AM

To

"Furniss, Peter"
<>

cc

Kristofer Agren <>,
bpel rqmts <>

Subject

Re: [wsbpel-reqts] RE: New
Issue - Incomplete XPath expressions in the specification

Furniss, Peter wrote:

>Isn't this covered in issue 46 (see

>http://www.choreology.com/external/WS_BPEL_issues_list.html#Issue46),

>and referenced in issue 39 (both now resolved).

>

>Also, I see, if what the membership and attendance information Kavi

>shows me is correct, you are still only a Prospective Member and it's

>possible you ought to have been dropped back to Observer.  After
I put

>in your previous issue (now issue 90) there was some question as to

>whether prospective members could post issues.  In practice, that
might

>differ as to whether the issue is a straightforward correction (as
this

>would be, if it weren't for 46) or a judgement or style question (as

>this might be).  When do you hope to become a full member ?

>

>(copying the issues and requirements group for advice)

>  

>

mm1: I suggest we have a member post the issue for Kristofer if there is

any question. The issue still exists regardless.

>Peter

> 

>------------------------------------------

>Peter Furniss

>Chief Scientist, Choreology Ltd

>web: http://www.choreology.com

>email: 

>phone: +44 870 739 0066

>mobile: +44 7951 536168

>

>

>  

>

>>-----Original Message-----

>>From: Kristofer Agren [mailto:]

>>Sent: 16 February 2004 16:11

>>To: Furniss, Peter

>>Subject: New Issue - Incomplete XPath expressions in the specification

>>

>>

>>Document: BPEL Specification

>>Description:

>>

>>Many of the BPEL examples that are included in the

>>specification use XPath queries that do not contain namespace 

>>references. If the node(s) being selected are within a 

>>namespace, per the XPath 1.0 specification, the XPath query 

>>should reference the nodes by their expanded-name/fully 

>>qualified name. 

>>

>>For example, in the excerpt below, the "query" attribute

>>defines an XPath query without namespace references, although 

>>that from the WSDL definition it is clear that the 

>>complexType (ship:shipOrder) that defines the part is 

>>contained in a namespace.

>>

>><bpws:propertyAlias propertyName="tns:shipOrderID"

>>                
messageType="sns:shippingRequestMsg"

>>                
part="shipOrder"

>>                
query="/shipOrder/ShipOrderRequestHeader/shipOrderID"/>

>>

>>The correct XPath query should be (assuming that the "ship"

>>prefix is defined and accurate):

>>

>>query="/shipOrder/ship:ShipOrderRequestHeader/ship:shipOrderID"

>>

>>I propose that all XPath queries in the BPEL specification

>>are updated to include namespace prefixes wherever applicable.

>>    

>>

To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel-reqts/members/leave_workgroup.php.
Next in thread → Next in month →