Issue 9 - SCA-BPEL XML Namespaces

Issue entered:
http://www.osoa.org/jira/browse/BPEL-9

Regards,
Alex Yiu

Dieter Koenig1 wrote:
> TARGET: SCA Client and Implementation Model Specification for WS-BPEL -
> note that the SCA Assembly Model is also affected.
>
>
> DESCRIPTION: All SCA assembly model elements have a common namespace
> (currently "http://www.osoa.org/xmlns/sca/1.0" - which will change to an
> OASIS namespace - to be clarified with the SCA-Assembly TC and OASIS).
>
> This issue is about two SCA-BPEL areas that sould be separated from the
> common namespace.
>
> 1. For the SCA extensions (sca:property, sca:multiReference, etc.) in a
> WS-BPEL process, there is no point in having these extensions in a common
> schema with the SCA assembly model (processes and assemblies are disjoint
> artifacts).
>
> 2. The XML schema element "serviceReferenceList" introduced in the SCA-BPEL
> specification is neither an SCA assembly model nor a BPEL process model
> element and should be separated as well.
>
>
> PROPOSAL: Use separate XML namespaces for SCA and SCA-BPEL, e.g. something
> like this:
>
> SCA Assembly Model (to be verified) ==>
> http://docs.oasis-open.org/sca/1.1/assembly
> WS-BPEL 2.0 extensions for SCA      ==>
> http://docs.oasis-open.org/sca/1.1/bpel/process
> Data element "serviceReferenceList" ==>
> http://docs.oasis-open.org/sca/1.1/bpel/types
>
> The SCA-BPEL TC may resolve this issue by separating these namespaces now,
> i.e. by using different prefixes, and aligning the namespace declarations
> with the SCA-Assembly TC and OASIS later.
>
>
> Kind Regards
> DK
>
>