RE: [wsbpel] Issue 88 - Proposal to vote

["Peter Furniss" <peter.furniss@choreology.com>]

On (2) below - The issue list table "Resolved issues awaiting editing
into spec" is generated by selecting all issues with status resolved and
no "In spec" entry.  I add the In spec's by hand when the editors say
they have applied it - so this relates to checking into the repository,
not the generation of a working draft. For 88 this "In spec" is 30
October, so it won't be in the current 21st September draft (I assume my
the evidence was Paco's message
http://lists.oasis-open.org/archives/wsbpel-spec-edit/200510/msg00034.ht
ml ).

I could formalise this with an additional table distinguishing things
that in published drafts from things that are only checked in, if people
thought it worthwhile. 

Peter


> -----Original Message-----
> From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com] 
> Sent: 07 December 2005 14:20
> To: wsbpel@lists.oasis-open.org
> Subject: Re: [wsbpel] Issue 88 - Proposal to vote
> 
> 
> (1) The spec section 6.4 has the following language for the 
> description of the importType attribute:
> 
> The importType attribute identifies the type of document 
> being imported by providing the URI of the encoding language. 
> The value 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.
> 
> This text does not exclude import of artifacts with a type 
> other than WSDL or XSD, even if only WSDL and XSD are 
> explicitly mentioned. I would like to explicitly point out 
> that this is a desirable approach for BPEL processes using 
> extensions, which may then also import artifacts with an 
> extension namespace.
> 
> Consequently, the WS-BPEL XML schema must be changed from
>    <attribute name="importType" type="bpws:importedURI" 
> use="required"/> to
>    <attribute name="importType" type="bpws:anyURI" use="required"/>
> 
> (2) According to the issue 88 resolution ( 
> http://www.choreology.com/external/WS_BPEL_issues_list.html#Is
sue88), the import attributes namespace and location are optional.

The resolution of issue 88 is not yet reflected in the spec BUT issue 88
is missing on the list of "Resolved issues awaiting editing into spec" (
http://www.choreology.com/external/WS_BPEL_issues_list.html#edit_table).
I assume that this is an error on the Web page.

==>

Taking both (1) and (2) together, the XML schema definition of tImport
must look like this:

   <complexType name="tImport">
     <complexContent>
       <extension base="bpws:tExtensibleElements">
         <attribute name="namespace" type="anyURI"/>
         <attribute name="location" type="anyURI"/>
         <attribute name="importType" type="bpws:anyURI"
use="required"/>
       </extension>
     </complexContent>
   </complexType>

Kind Regards
DK


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php