[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue 7 - approved proposal.
Dear Paco and other Colleagues, Just a point of detail. Suppose an XML schema is being imported that has not target namespace (i.e. a no namespace schema). Should we have a special value for the namespace attribute in this case as it is required and so can not just be omitted? Best Regards Tony A M Fletcher Cohesions (TM) Business transaction management software for application coordination www.choreology.com Choreology Ltd., 68 Lombard Street, London EC3V 9LJ UK Tel: +44 (0) 870 7390076 Fax: +44 (0) 870 7390077 Mobile: +44 (0) 7801 948219 tony.fletcher@choreology.com (Home: amfletcher@iee.org) -----Original Message----- From: Francisco Curbera [mailto:curbera@us.ibm.com] Sent: 16 October 2003 07:49 To: 'wsbpel@lists.oasis-open.org' 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]