[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue 7 - approved proposal.
Here is the updated text of the proposal we approved in yesterday's call: Introduce a single <bpel:import> element used to import XSD, WSDL definitions. Zero or more <bpel:import> elements may appear as first children of the <bpel:process> element. Three required attributes must be: - "namespace": target namespace being imported - "location": where to find the imported information - "importType": identifies the type of document being imported by providing the URI of the encoding language: either "http://www.w3.org/2001/XMLSchema" or "http://schemas.xmlsoap.org/wsdl/". For example: <bpel:import namespace="..." location="document-location" importType="XYZ-namespace-uri"/> A <bpel:import> import element will be interpreted as a hint for BPEL processors. In particular, processors are not required to retrieve the imported document from the specified location. Francisco Curbera/Watson/IB To: "Liu, Kevin" <kevin.liu@sap.com> M@IBMUS cc: "'wsbpel@lists.oasis-open.org'" <wsbpel@lists.oasis-open.org>, "'ygoland@bea.com'" <ygoland@bea.com> 10/01/2003 12:27 Subject: RE: [wsbpel] Issue 7 - possible resolution AM Kevin, Thanks for the catch! I intended to say "namespace", not "targetNamespace". Please consider my proposal modified accordingly. Paco "Liu, Kevin" <kevin.liu@sap.co To: "'ygoland@bea.com'" <ygoland@bea.com>, Francisco m> Curbera/Watson/IBM@IBMUS, "'wsbpel@lists.oasis-open.org'" <wsbpel@lists.oasis-open.org> 09/30/2003 10:33 cc: PM Subject: RE: [wsbpel] Issue 7 - possible resolution I like option 1 better with one modification. Following the XSD and WSDL import model, I would prefer that the "targetNamespace" attribute be re-named to "namespace" which identify the namespace of the file being imported. Best Regards, Kevin -----Original Message----- From: Yaron Goland [mailto:ygoland@bea.com] Sent: Tuesday, September 30, 2003 9:58 AM To: 'Francisco Curbera'; wsbpel@lists.oasis-open.org Subject: RE: [wsbpel] Issue 7 - possible resolution Keep in mind that even in option 1 it will be necessary for the processor to validate the file's contents. Just because someone says something is a WSDL file doesn't mean it is. Also, why do we need the targetNamespace declaration on the import statement? The files themselves define their namespaces. Yaron > -----Original Message----- > From: Francisco Curbera [mailto:curbera@us.ibm.com] > Sent: Tuesday, September 30, 2003 9:23 AM > To: wsbpel@lists.oasis-open.org > Subject: [wsbpel] Issue 7 - possible resolution > > > > > > > As agreed at the last f2f, my proposed resolution of issue 7 > is described > below (#1.) Based on that discussion, we can consider a > second flavors of > the proposal, described in #2. I suggest we adopt one of them > (#1 is my > preference) and close this issue. > > 1. Introduce a single <bpel:import> element used to import XSD, WSDL > definitions. Zero or more <bpel:import> elements may appear as first > children of the <bpel:process> element. Three required > attributes must be > included on each <bpel:import> element: > > - targetNamespace being imported > - location: where to find the imported information > - importType: identifies the type of document being imported > by providing > the URI of the encoding language: either > "http://www.w3.org/2001/XMLSchema > ", or "http://schemas.xmlsoap.org/wsdl/". > > <bpel:import targetNamespace="..." location="... document > location ..." > importType="XYZ-namespace-uri/> > > 2. The alternate version of the eliminates the importType attribute. > > What is the difference? In option 2, a BPEL processor finds > and import and > retrieves the target document without knowing what kind of > document that > is. The processor must open and inspect the document in order > to figure out > how to process it. On discovering the type of the root > element inside the > document, the processor will be able to dispatch a Schema or > WSDL processor > to consume the document (which will in turn read the document and now > actually process it.) In option 1, the BPEL processor has not > need to read > in the target document, it can just handle the job to the appropriate > (Schema or WSDL) processor. Otherwise proposals are > equivalent, of course. > > > > > 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/le > ave_workgroup.php. > > 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 . 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 . 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]