[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue - 165 - clarification of the default NS URI for expression and query language
-----Original Message-----
From: Furniss, Peter
Sent: 24 September 2004 00:20
To: wsbpel@lists.oasis-open.org
Subject: [wsbpel] Issue - 165 - clarification of the default NS URI for expression and query languageThis issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")
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 - 165 - clarification of the default NS URI for expression and query language
Status: received
Date added: 23 Sep 2004
Categories: Syntax and validation, Related standards
Date submitted: 23 September 2004
Submitter: Alex Yiu
Description:Currently, http://www.w3.org/TR/1999/REC-xpath-19991116 is used as the default value of both expression language and query language, which represents XPath 1.0.
In order for us to make use of XPath 1.0 within BPEL, the BPEL spec needs to define additional semantics for the cross-language bindings. Those details are actually specific to BPEL language in a sense. Strictly speaking, it is not appropriate to "hijack" the W3C namespace for our own use.
(This was raised by Chris Keller in the course of issue 89 : Handling Unrecognized Query/Expression Languages discussion at the face-to-face today)
Submitter's proposal:Replace the following text in BPEL spec:
The default value for this attribute is XPath 1.0, represented by the URI of the XPath 1.0 specification: http://www.w3.org/TR/1999/REC-xpath-19991116.with:The default value for this attribute is: "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0", which represents the usage of XPath 1.0 within WS-BPEL 2.0. The URI of the corresponding XPath 1.0 specification is: http://www.w3.org/TR/1999/REC-xpath-19991116.See also:
I believe we still need try to get some official document from OASIS on how to use an OASIS-based URN.
- result of some internet searching on OASIS URN namespace convention by Alex
- RFC 3121, defining OASIS URN
Changes: 23 Sep 2004 - 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 - 165 - [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 - 165 - 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 mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]