Minutes
Opening
Resolution: m:Malhotra s:Khanderao Minutes of 2007-12-18 approved w/o
Action items
2007-12-18-1 defered until issues discussion agendum
Usage of Adobe Connect
<Sanjay>
It's killing my Firefox browser (2.0.0.11 on Windows)
<Sanjay>
Duane, do we have some support (say Gold)?
bob:
What is the persistence of the chat?
<jeffm>
user limit exceeded - macos 10.4.11 firefox 2.0.0.11
<henning>
firefox crashes when try to connect, IE says the user limit has been exceeded :-(
<Sanjay>
same here. I am scared to click that link now.
<Dieter Koenig>
i use firefox 2.0.0.11 and get to the "user limit exceeded" screen
Nickull:
The data goes away when the last user logs off
<CanadaDuane>
That is my fault: I probably forgot to override the default number of attendees.
<CanadaDuane>
dnickull@adobe.com
After some discussion of pluses and minuses it was decided to try it out for some document related things but to use webconf
for chat for the meantime
Proposed agenda for the f2f January 22/23
<Mike Edwards>
1. SCA Assembly Specification - proposed changes in form and ordering
WD-02 of the Assembly specification contains a proposal for a reworked version of
the specification - not changing the normative content, but certainly changing the
layout and content. Need to agree on making this significnat change.
2. SCA Assembly Conformance statements and Test Suite
- need to establish a path for conformance: for example what is
mandatory and what is optional - for example, are there "groups" of optional
elements that must all be not supported or all supported?
- need to define the form and content of the test suite and
establish a working plan
3. The Dynamic behaviour of the SCA Domain
- need to work through the dynamic aspects of the SCA Domain and establish
whether new rules, new interfaces are required. It is clear from discussions that
the dynamic nature of the Domain is not adequately described in the current
specification.
4. Callbacks and Conversational Interfaces
- is the current functionality for callbacks and for conversational interfaces too
complex and too hard to understand? Can a simpler set of features be
described that will make it easier to understand and to use
- note that there may be relationship between this item and some existing
issues (ISSUE-33 in Assembly for example)
5. Specific Major Issues:
ISSUE-1 Is binding.sca always present?
ISSUE-4 Dynamic change of callbacks
ISSUE-24 textual sca:include not sufficient
ISSUE-27 Default URI construction rules aren't consistentwith compatible service evolution
ISSUE-31 Wiring from a reference with no binding to a service with a binding
ISSUE-33 Long-Running Request-Response Operations
Initial proposal was distributed by Edwards by email
Edwards reviews the agenda proposal
<CanadaDuane>
When is next face to face?
Members are stunned into silence by the brilliance of the proposed agenda
<CanadaDuane>
ROTFL!!! ;-)
Koenig:
would like to see some discussion related to BPEL under item Nr. 4
Edwards:
Asks members to provide agenda feedback so that it may be finalized timely
<TomRutt>
We should have an Issue triage session of about 1/2 hour to get a grip on difficulty of issues and to assign volunteers for
proposals
Specification Draft
Edwards:
Editor tram has posted a new version on the web site
Patil:
Changes have been documented in the change-log
... I beseech members to review this version prior to the face to face.
<Khanderao>
stage 1:
- composite section
- changed order of subsections from property, reference, service to service, reference, property
- progressive disclosure of schemas, each section only shows what is described
- attributes description now starts with name : type (cardinality)
- child element description as list, each item starting with name : type (cardinality)
- added section in appendix to contain complete pseudo schema of composite
stage 2:
- moved component section after implementation section
- moved interface section to after constraining type section
- component section
- added subheadings for Implementation, Service, Reference, Property
- progressive disclosure of schemas, each section only shows what is described
- attributes description now starts with name : type (cardinality)
- child element description as list, each item starting with name : type (cardinality)
stage 3:
- implementation section
- moved implementation instance related stuff from implementation section to component implementation section
- added subheadings for Service, Reference, Property, Implementation
- progressive disclosure of schemas, each section only shows what is described
- attributes description now starts with name : type (cardinality)
- child element description as list, each item starting with name : type (cardinality)
- attribute and element description still needs to be completed, all implementation statements on services, references,
and properties should go here
- added complete pseudo schema of componentType in appendix
stage 4:
- added sample section, no content yet
- added comment to introduction section that the following text needs to be added
"This specification is defined in terms of infoset and not XML 1.0, even though the spec uses XML 1.0/1.1
terminology. A mapping from XML to infoset (... link to infoset specification ...) is trivial and should
be used for non-XML serializations."
post immediately above demonstrates the changes that were made to the draft specification
Open Issues
Assembly-11
Martin notes that he was assigned an action item in absentia and time since the assignment has been holiday
Assembly-35 Confusing words in Section 5.3 relating to ConversationalIntent
Edwards:
Stepping out of chair, exposes the proposal
<Sanjay>
looks good to me
Action: Edwards to introduce an issue for intents and policy set attachments to interface elements
Resolution: m:Booz s:Patil proposal contained in jira at http://www.osoa.org/jira/browse/ASSEMBLY-35 accepted w/o
New Issue Assembly-31
Action: Chapman to modify state of Assembly-31 from new to open
AOB
Schreiber diagnostics output
[Delete this section before publishing the minutes]
statistics: Schreiber found 173 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 204: bob: s/Kanderao/Khanderao
command-scribe: Line 3: Bob Freund recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 13: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 15: Check for possible unrecognized nick '3. Action Items'
citation-detection-irc1: Line 17: Check for possible unrecognized nick '2007-12-18-1'
citation-detection-irc1: Line 25: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 29: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 34: Check for possible unrecognized nick 'ASSEMBLY-11'
citation-detection-irc1: Line 35: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 37: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 39: Check for possible unrecognized nick 'ASSEMBLY-35'
citation-detection-irc1: Line 40: Check for possible unrecognized nick 'http'
edit-substitute: command on line 204 succeeded, changed line 87 from 'Kanderao' to 'Khanderao'
citation-detection-irc1: Line 164: Check for possible unrecognized nick 'stage 2'
citation-detection-irc1: Line 174: Check for possible unrecognized nick 'stage 3'
citation-detection-irc1: Line 184: Check for possible unrecognized nick 'stage 4'
edit-delete: Line 204 was deleted
system: Transformer: SAXON 9.0.0.2
[End of Schreiber diagnostic output]