ISSUE 30: Incorrect description of <Operation/> child elements in Assembly

[Scott Vorthmann <scottv@tibco.com>]

http://www.osoa.org/jira/browse/ASSEMBLY-30

On Nov 27, 2007, at 6:10 AM, Mike Edwards wrote:

>
> RAISER: Mike Edwards
>
> TARGET: Assembly Specification
>
> DESCRIPTION:
>
> (Numbering based on sca-assembly-1.1-spec-WD-01.doc)
>
> The ability to apply intents and policies to individual operations  
> of an interface as used by a service or a reference
> is described in the Policy Framework specification.  This  
> capability is described incorrectly or
> inadequately in parts of the Assembly specification, as follows:
>
> Problem 1: Schema for the SCA Binding repeats the <operation/>  
> elements which are present in the
> base sca:binding type which it extends.  It also repeats the  
> attributes of the base type.
> This is incorrect, pure & simple.  Extension types should not  
> repeat elements or attributes in the base type.
>
> Problem 2:  <operation/> elements are defined as child elements of:
> - Service complex type (and derivatives like ComponentService)
> - Reference complex type (and derivatives)
> - Binding complex type
>
> These are correct - they are provided to permit  intents and  
> policySets to be applied to individual
> operations, if required.
>
> However, these elements are nowhere described in the body of the  
> Assembly specification, not even
> within the pseudo-schemas for the relevant elements.  The elements  
> should be added to the pseudo
> schemas and a reference to their description should be added to the  
> related sections of the Assembly
> specification.
>
>
> PROPOSAL:
>
> 1) Remove the <operation/> elements and the attribute declarations  
> from the binding.sca xsd,
> except for the <anyAttribute.../> extension element.
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <!-- (c) Copyright SCA Collaboration 2006, 2007 -->
>
> <schema xmlns="http://www.w3.org/2001/XMLSchema";
>
>     targetNamespace="http://www.osoa.org/xmlns/sca/1.0";
>
>     xmlns:sca="http://www.osoa.org/xmlns/sca/1.0";
>
>         elementFormDefault="qualified">
>
>
>     <include schemaLocation="sca-core.xsd"/>
>
>
>     <element name="binding.sca" type="sca:SCABinding"
>
>             substitutionGroup="sca:binding"/>
>
>     <complexType name="SCABinding">
>
>         <complexContent>
>
>             <extension base="sca:Binding">
>
>                 <anyAttribute namespace="##any"  
> processContents="lax"/>
>
>             </extension>
>
>         </complexContent>
>
>     </complexType>
>
> </schema>
>
> 2) Add to the following pseudo-schemas the following, after each  
> <service/>, <reference/> and <binding/>
> element:
>
> <operation name="xs:NCName" requires="list of xs:QName"?  
> policySets="list of xs:QName"?>*
>
> Pseudo-schemas starting on the following lines:
>
> 136
> 491
> 991
> 1339
> 1521
> 1931
> 2322
>
>
> 3) Add the following to each of the sections that describe  
> attributes and/or child elements of services, references
> and bindings:
>
> An xxxx element has zero or more operation child elements. These  
> elements are used to describe characteristics of individual
> operations within the interface of the service or reference.  For a  
> detailed decription of the operation element, see the
> Section 4.4 of the Policy Framework specification.
>
>
>
>
> Yours,  Mike.
>
> Strategist - Emerging Technologies, SCA & SDO.
> Co Chair OASIS SCA Assembly TC.
> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
> Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431
> Email:  mike_edwards@uk.ibm.com
>
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with  
> number 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire  
> PO6 3AU
>
>
>
>
>
>
>