sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Draft minutes from 2009-10-27 are attached
- From: Bob Freund <bob.freund@hitachisoftware.com>
- To: sca-assembly@lists.oasis-open.org
- Date: Tue, 27 Oct 2009 12:08:28 -0400
Title: SCA-Assy - 2009-10-27
Hide Chat
Action Items
- Done:
- id=2009-10-20-1 status=done owner="SanjayP" Send E-mail describing alternative approach for ASSEMBLY-132
- id=2009-10-20-2 status=done owner="ScottV" Create JIRA component for Event Handling Issues
Resolutions
- 2009-10-27-1: Minutes of 2009-10-20 approved w/o
- 2009-10-27-2: m:Malhotra s:Booz Assembly-183 opened w/o
- 2009-10-27-3: m:Edwards s:Karmarkar Resolve Assembly-143 with the text immediately above w/o
Minutes
Opening
<gilbert.pilz>
tree killer!
Roll - 19 of 24 voting members present
Mike would like to do Assembly-183 first
no objections on the agenda amandment
Resolution: Minutes of 2009-10-20 approved w/o
Action Items
Action: id=2009-10-20-1 status=done owner="SanjayP" Send E-mail describing alternative approach for ASSEMBLY-132
Action: id=2009-10-20-2 status=done owner="ScottV" Create JIRA component for Event Handling Issues
Administrivia
Public review of both the Assembly Spec as well as the Test Cases have completed
Next F2F is proposed as December 1-3 at Tibco's location in the bay Area
<anish>
why can't you apply policies on binding.sca ?
Resolution: m:Malhotra s:Booz Assembly-183 opened w/o
Edwards dicusses his proposal at
<Scott>
now linked in Jira as well
<anish>
so, i don't quite see why we need the stmt in ASM90006
<anish>
the general rules of intent satisfaction say that intents that are specified are either satisfied by the binding or policy
set. These rules would still apply. Like they would for any other binding
<anish>
SHOULD with a MUST? It SHOULD satisfy an intent, if not it MUST raise an error. Why not just say it MUST satisfy an intent?
<anish>
IOW, the current wording says that it is never ok not to satisfy an intent as there would be an error
<Sanjay>
I think raising an error when an intent is not satisfied is required for any binding type. Why do we need a separate conformance
statement for binding.sca?
<Sanjay>
If the only special casing for binding.sca is that - policy sets are not used for binding.sca, shouldn't we just say that!
<Ashok>
Sanjay, then we shd change the 'should' to a 'must'
<Ashok>
If it's a should then a warning needs to be raised if anything
<Sanjay>
Ashok, even with a 'must' I think it is redundant to the general requirement of 'intents must be satisfied', right?
<Ashok>
yes, that's correct
<anish>
how about: An SCA binding implementor is encouraged to support all the intents specified by the SCA Policy specification in
their implementation.
<Mike Edwards>
Proposed text:
<Mike Edwards>
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. Qualities of service
for <binding.sca/> are expressed using intents.
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 has to support the binding.sca binding type. See section 13.2.
A service definition with no binding element specified uses the SCA binding (see ASM50005 in section 4.2 on Component Service).
<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 is one of the bindings specified by the
service provider, as long as the intents attached to the reference and the service are all honoured, as described in Section
4.3 on Component Reference.
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 <binding.sca/> element of a <component/> <reference/> specifies a URI via its @uri attribute, then this provides a wire
to a target service provided by another component.
The form of the URI which points to the service of a component that is in the same composite as the source component is as
follows:
<component-name>/<service-name>
<Scott>
works for me to first *shrink* the entire window, then drag the corner of this text box
Motion: m:Edwards s:Karmarkar Resolve Assembly-143 with the text immediately above
Resolution: m:Edwards s:Karmarkar Resolve Assembly-143 with the text immediately above w/o
AOB
<Mike Edwards>
Thanks Bob
[End of Minutes]
Formatted on 2009-10-27 at 12:06:25 GMT-4
Minutes formatted by Schreiber, a collection of XSLT
stylesheets by Bob Freund modeled after David Booth's scribe
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Title not specified, default title 'OASIS SCA-Assembly TC...' was assumed
final validation: Chair not specified, default chair was assumed
statistics: Schreiber found 51 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 9: s/mike/Mike
command-scribe: Line 1: Bob Freund is recognized
command-scribe: Line 1: Bob Freund's nick Bob has been selected
edit-substitute: command on line 9 succeeded, changed line 8 from 'mike' to 'Mike'
edit-delete: Line 9 was deleted
citation-detection-scribed: Line 67: Check for possible unrecognized nick 'Time'
command-autoroll/oasis: Line 79: Attempting to fetch roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=25350
command-autoroll/oasis: Line 79: Successfully fetched roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=25350
system: Transformer: SAXON 9.1.0.7
[End of Schreiber diagnostic output]
smime.p7s
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]