Re: [Issue 82] NEW ISSUE: Relax <component/> schema to allow <implementation/> anywhere

[David Booz <booz@us.ibm.com>]

The hard wired sequence you've shown below is where we started years ago. That structure was deemed inflexible, and the choice was added. I still agree with the notion that a flexible structure would be beneficial.

Since opening this latest issue, several schema experiments have been attempted to arrive at a solution, but none of them has been successful (UPA failures). I'm no longer certain if this issue is solvable given schema rules AND where we have placed the extensibility points. I was hoping you'd have a brainstorm.


Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

Anish Karmarkar ---09/23/2008 01:33:07 AM---I've always wondered why we have that choice. Apologies, if this was discussed before and I have fo

From:	Anish Karmarkar <Anish.Karmarkar@oracle.com>
To:	David Booz/Poughkeepsie/IBM@IBMUS
Cc:	sca-assembly@lists.oasis-open.org
Date:	09/23/2008 01:33 AM
Subject:	Re: [Issue 82] NEW ISSUE: Relax <component/> schema to allow <implementation/> anywhere

---

I've always wondered why we have that choice. Apologies, if this was 
discussed before and I have forgotten the reason.
What's wrong with saying:
<sequence>
   <implementation />
   <service minOccurs="0" maxOccurs="unbounded"/>
   <reference minOccurs="0" maxOccurs="unbounded"/>
   <property minOccurs="0" maxOccurs="unbounded"/>
   <any minOccurs="0" maxOccurs="unbounded"/>
</sequence>

Doesn't that make the UPA problem more manageable?
OR what is the advantage of allowing service/ref/prop to occur in any order?

-Anish
--

David Booz wrote:
> TARGET: Any version of the Assembly spec
> 
> DESCRIPTION:
> The schema for <component/> and others requires <implementation/> to be 
> the first child. This seems overly restrictive and should be relaxed.
> 
> PROPOSAL:
> Move the <implementation/> element inside the <choice/> containing 
> <service/>, <reference/> and <property/>.
> 
> 
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:booz@us.ibm.com
>