[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 88 - Import Errata
This issue has been added to the wsbpel issue list. 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 document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting 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.
Should we use the XML element name 'import'?
Import implies that the files that are being pointed to are included in the BPEL definition. But
strictly speaking that isn't the case since BPEL does not support in-line WSDL or XML Schema definitions.
Shouldn't the name be more descriptive, such as 'associate'?
How do we handle relative URIs in import's attributes?
What is the base URI against which the relative URIs are resolved? Should we refer to something like
XML Base (http://www.w3.org/TR/xmlbase/)? Should we specify that if xmlbase isn't used then the definition
of the base URI is engine specific?
What happens if an engine chooses not to honor the import?
The current text of the BPEL spec states that the BPEL engine is not required to import the files
it is pointed at. But if it fails to import the files then the BPEL definition will not be complete
and at some point an error is likely to happen if the imported files contained definitions necessary
for the BPEL. Shouldn't a static error be thrown if an engine decides not to honor an import?
What happens if two different files import the same definition?
Is there any sort of ordering? Does the first or last definition hold? Should this always
be a static error? What about collisions from implicit imports versus explicit imports? An
implicit import is an import that occurs through a mechanism not specified in the BPEL file
itself (e.g. how import worked before we introduced the import XML element). An explicit
import is an import specified via an import XML element.
Changes: 3 Dec 2003 - new issue
To comment on this issue, 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 - 88 - [anything]" or is a reply to such a message.
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]