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: New Issue - BPEL Import Schema Disagrees with spec text


Problem


The latest schema for BPEL (2005.12.22) has:
	<complexType name="tImport">
		<complexContent>
			<extension base="bpws:tExtensibleElements">
				<attribute name="namespace" type="anyURI" use="required"/>
				<attribute name="location" type="anyURI" use="required"/>
				<attribute name="importType" type="anyURI" use="required"/>
			</extension>
		</complexContent>
	</complexType>
which makes all three attributes of the bpws:import element mandatory. However, the spec text states:


Each <import> element contains a mandatory and two optional attributes.

·        “namespace”. The namespace attribute specifies an absolute URI that identifies the imported definitions. This attribute is optional. An import element without  a namespace attribute indicates that external definitions are in use which are not namespace qualified.

·        “location”. The location attribute contains a URI indicating the location of a document that contains relevant definitions in the namespace specified. The location URI may be a relative URI, following the usual rules for resolution of the URI base (XML Base and RFC 2396). The location attribute is optional. An import element without a location attribute indicates that external definitions are used by the process but makes no statement about where those definitions may be found. The document located at the location URI MUST identify the definitions it contains with a URI matching the URI indicated by the namespace attribute. The location attribute is a hint and that the BPEL Processor is not required to retrieve the document being imported from the specified location.

·        “importType”. The importType attribute identifies the type of document being imported by providing an absolute URI that identifies the encoding language used in the document. The value of the importType attribute MUST be set to "http://www.w3.org/2001/XMLSchema"; when importing XML Schema 1.0 documents, and to "http://schemas.xmlsoap.org/wsdl/"; when importing WSDL 1.1 documents. Note: other importType URI values MAY be used here.



The spec clearly states that the "namespace" and "location" attributes are optional, following closely the pattern for <import> set by XML Schema itself.

The schema and the spec text clearly disagree. Which is right?

Proposed Solution

The specification text correctly reflects the intent of the TC. The schema should be modified thusly:

	<complexType name="tImport">
		<complexContent>
			<extension base="bpws:tExtensibleElements">
				<attribute name="namespace" type="anyURI" use="optional"/>
				<attribute name="location" type="anyURI" use="optional"/>
				<attribute name="importType" type="anyURI" use="required"/>
			</extension>
		</complexContent>
	</complexType>
where the changes are shown in blue, changing use="required" to use="optional" for the "namespace" and "location" attributes.


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