Re: [sca-assembly] [ISSUE 143] There are no conformance statements insection 8.5 (CD03) - Proposal

[Mike Edwards <mike_edwards@uk.ibm.com>]

Ashok,

Funnily enough, you've picked on a sentence
that is unchanged from what is already in the spec - and one that
is not a normative statement.

I don't know of any "other means"
that applies to binding.sca - we don't say that policySets can apply to
binding.sca,
at least not normatively (and so portably).
 So the implication is that if binding.sca is to satisfy an intent,
then it must
satisfy it intrinsically (eg if "confidentiality"
is stated, then the binding.sca itself must be capable of providing the

necessary encryption without further
configuration).

What is not said is that binding.sca
*MUST* be capable of satisfying all of the intents defined by the Policy
spec.
This leaves it open for different vendors
to create binding.sca implementations that satisfy only a subset of the
intents (possibly an empty set!!).

You may like to open a separate issue
on this topic.  I suppose it should be an Assembly issue, but it is
right on the
boundary with the Policy spec....


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

From:	ashok malhotra <ashok.malhotra@oracle.com>
To:	Mike Edwards/UK/IBM@IBMGB
Cc:	OASIS Assembly <sca-assembly@lists.oasis-open.org>
Date:	22/09/2009 14:36
Subject:	Re: [sca-assembly] [ISSUE 143] There are no conformance statements in section 8.5 (CD03) - Proposal

---

Mike, you said:
 > The only requirement is that any specified qualities of service are
implemented for the SCA binding type.
Does this mean that the specific instance of the binding must support 
all the policies applied to it?
But all policies do not have to be satisfied by the binding.  Some
can 
be satisfied by other means.
All the best, Ashok


Mike Edwards wrote:
>
> Folks,
>
> Here is a proposal to resolve Issue 143 - the following text is a
> complete replacement for section 8.5:
>
> 8.5        *SCA Binding*
>
> The SCA binding element is defined by the following schema.
>
> <binding.sca />
>
> The SCA binding can be used for service interactions between 
> references and services contained within the SCA Domain. The way in
> which this binding type is implemented is not defined by the SCA 
> specification and it can be implemented in different ways by different
> SCA runtimes. The only requirement is that any specified qualities
of 
> service are implemented for the SCA binding type.  The SCA binding
> type is */not/* intended to be an interoperable binding type.  For
> interoperability, an interoperable binding type such as the Web 
> service binding is used.
>
> An SCA runtime MUST support the binding.sca binding type. [ASM90005]
>
> A service definition with no binding element specified MUST use the
> SCA binding. [ASM90006]
> <binding.sca/> only has to be specified explicitly in override
cases, 
> or when a set of bindings is specified on a service definition and
the 
> SCA binding needs to be one of them.
>
> If a reference does not have a binding subelement specified, then
the 
> binding used MUST be one of the bindings specified by the service
> provider, as long as the intents attached to the reference and the
> service are all honoured. [ASM90007]
>
> If the interface of the service or reference is local, then the local
> variant of the SCA binding will be used. If the interface of the 
> service or reference is remotable, then either the local or remote
> variant of the SCA binding will be used depending on whether source
> and target are co-located or not.
>
> If a reference specifies a URI via its @uri attribute, then this 
> provides the default wire to a service provided by another Domain
> level component. The form of the URI MUST be as follows:
>
> ·        <component-name>/<service-name>
 [ASM90008]
>
>
>
> 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/
>
>
>
>
>
>

---

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