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: Issue - 289 - xsd target namespace and abstract profile URI

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 - 289 - xsd target namespace and abstract profile URI

Status: received
Date added: 17 May 2006
Date submitted: 17 May 2006
Submitter: Alex Yiu
Description: (modified prior to submission, in light of comments from Diane Jordan and others)

Background: During San Jose F2F, we passed a target namespace resolution issue 284 : target namespace URI update to update the target namespace URI for Exec and Abstract Process (see resolution of issue 284 for particulars)

Three points arise:

[a] Peter Furniss, 8 May 2006 asked whether we should use a de-referenable URI. E.g. starting with "http://docs.oasis-open.org/wsbpel/...".

Alex Yiu, 11 May 2006 replied : I guess there are two kinds of NS URI.

One kind is not associated with an XML Schema. (e.g. expression language URI) I think we should stick with URN in those cases.

The other kind is associated with an XML Schema. (e.g. target NS for Exec and Abstract BPEL). In this case, I am open to change from URN style to URL style with a de-referenceable URI. (Starting with "http://docs.oasis-open.org/wsbpel/...")

(Example from another OASIS TC: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd)

If we want to pick this route, the URI will become something to following:

The namespace URI of executable process is updated from: "urn:oasis:names:tc:wsbpel:2.0:process:executable" to: "http://docs.oasis-open.org/wsbpel/2.0/process/executable/[...].xsd"

The namespace URI of partner link type declaration in WSDL is updated from: "urn:oasis:names:tc:wsbpel:2.0:partnerlink" to: "http://docs.oasis-open.org/wsbpel/2.0/process/partnerLink/[...].xsd"

The namespace URI of abstract process is updated to: "http://docs.oasis-open.org/wsbpel/2.0/process/abstract/[...].xsd"

[...] is not decided yet. We need to investigate whether there is a naming convention for XSD files in OASIS.

[b] For the abstract profile URIs:

For Observable Behavior, I would suggest to update to: "http://docs.oasis-open.org/wsbpel/2.0/process/abstract/profiles/observable-behavior/2006/MM/[...].xsd" For Template, I would suggest to update to: "http://docs.oasis-open.org/wsbpel/2.0/process/abstract/profiles/template/2006/MM/[...].xsd"

By having these changes, the URI for both profiles and abstract process itself look more consistent.

If we don't have XSD for profiles, then the "[...].xsd" would be dropped.

[c] replace "MM" in profile with the real number for Month. Let us shoot for "06"

The division between description and proposal on this issue is a little arbitrary - see also pre-announcement messages in Links. PRF
Submitter's proposal: I would suggest to formally pass the resolution for this topic once the XSD for both Exec and Abstract Process and both Abstract Process Profiles are finalized.
Changes: 17 May 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 - 289 - [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 - 289 - 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).

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