Minutes
Opening
Roll quorate with 20 of 31 voting members.
<Eric Wells>
I will scribe next week
Resolution: Minutes of 2008-06-03/04 approved w/o
Action Items
Action: id=2008-04-28-1 status=pending Editors to address the editorial comments contained in Combellack's comments at http://lists.oasis-open.org/archives/sca-assembly/200804/msg00089.html
Action: id=2008-06-03-1 status=done Karmarkar to produce a refined proposal for Issue 60 containing details and example during the
lunch break
Action: id=2008-06-03-2 status=done Update the minutes to change Issue XX to Issue 66
Action: id=2008-06-03-3 status=pending owner=Karmarkar&Nash Simon Nash to develop a more concrete proposal for Issue 37 along the
lines of the F2F discussion so that profitable discussion may continue this meeting.
Action: id=2008-06-03-4 status=pending Chapman to propose some non-normative clarification text to resolve Issue-26 due=2008-12-24
Action: id=2008-06-03-5 status=pending Editors to produce a plan to label normative statements or groups of statements in the spec
due=2008-06-10
Action: id=2008-06-03-6 status=pending owner=Edwards Test sub cttee produce test assertions and test artifacts and test harness
Action: id=2008-06-03-7 status=pending ref Assembly-16 Edwards to look into the question of aliases
Action: id=2008-06-03-8 status=pending ref Assembly-16 Nash to look into how binding uris may be handled
Action: id=2008-06-03-9 status=pending Mike Edwards to prepare a proposal for addressing Assembly-8 based on some of the discussions
at the F2F
Action: id=2008-06-03-10 status=pending Mike Edwards, raise an issue relating to deployment and redeployment and the granularity and
semantics of these processes
Action: id=2008-06-03-11 status=pending Mike Edwards - Question of handling changes of property values (including multi-values) -
should be part of the discussion of Issue 41
Action: id=2008-06-03-12 status=pending Anish Karmarkar to bring back the resolution of issue 52 back to the BPEL TC ("close no action")
Action: id=2008-06-03-13 status=pending Nash/Edwards prepare proposal text for Assembly-56
Action: id=2008-06-03-14 status=pending Editors construct a plan for the next CD
Action: id=2008-06-03-15 status=pending Chairs to ensure that JIRA is up to date with the closed issue status in CD-01
Action: id=2008-06-03-16 status=pending TC Members with East Coast USA facilities consider hosting next F2F in week of Sept 29, for
approximately 18-20 persons
New Issues
Aupperle describes his new issue
Resolution: m:Aupperle s:Moberg New issue 67 opened w/o
<Bryan Aupperle>
The component type is defined by a componentType element in the componentType file. The extension of a componentType files
is .componentType but its name and location depends on the type of the component implementation: the specifics are described
in the respective client and implementation model specification for the implementation type.
Motion: m:Aupperle s:Moberg Assembly-67 beresolved with "The component type is defined by a componentType element in the componentType
file. The extension of a componentType files is .componentType but its name and location depends on the type of the component
implementation: the specifics are described in the respective client and implementation model specification for the implementation
type."
Amendment: m:Chapman s:Aupperle s/The extension of a componentType files is .componentType /The extension of a componentType file MUST
be .componentType/ w/o
Motion: as amended Resolve Assembly-67 with "The component type is defined by a componentType element in the componentType file. The
extension of a componentType file MUST be .componentType and its name and location depends on the type of the component implementation:
the specifics are described in the respective client and implementation model specification for the implementation type."
Resolution: Resolve Assembly-67 with "The component type is defined by a componentType element in the componentType file. The extension
of a componentType file MUST be .componentType and its name and location depends on the type of the component implementation:
the specifics are described in the respective client and implementation model specification for the implementation type."
w/o
Aupperle describes his new issue
Resolution: m:Aupperle s:Karmarkar Assembly-68 opened w/o
Resolution: m:Aupperle s:Karmarkar Resolve Assembly-68 with the proposal contained in the JIRA w/o
Aupperle describes what he characterizes as a purely editorial issue
<anish>
since these are examples, we should list the artifacts from all the sister TCs
Resolution: m:Aupperle s:Nash New Issue Assembly-69 opened w/o
Motion: m:Nash Resolve Assembly-69 by listing all of the standardized interface and implementation types defined by the various SCA
TCs in the relevant places
Resolution: Resolve Assembly-69 by listing all of the standardized interface and implementation types defined by the various SCA TCs in
the relevant places w/o
Existing Issues
Aupperle discussed the issue
<Bryan Aupperle>
Technologies that use naming schemes other than QNames must use a different import element from the same substitution group
as the the SCA <import> element. The element used identifies the technology, and may use any value for the namespace that
is appropriate for that technology. For example, <import.java> can be used can be used to import java definitions, in which
case the namespace should be a fully qualified package name.
<Bryan Aupperle>
The above is from CD 01
Action: Aupperle to develop a re-worked proposal for the resolution of Assembly-53 based on the discussions of 2008-06-17
Schreiber diagnostics output
[Delete this section before publishing the minutes]
statistics: Schreiber found 144 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 211: bob: s/Aupperly/Aupperle/g
edits: Line 227: bob: s/ansih:/anish:/G
command-scribe: Line 7: Bob Freund recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 17: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 19: Check for possible unrecognized nick '3. Action Items'
citation-detection-irc1: Line 21: Check for possible unrecognized nick '2008-04-28-1'
citation-detection-irc1: Line 23: Check for possible unrecognized nick '2008-06-03-1'
citation-detection-irc1: Line 26: Check for possible unrecognized nick '2008-06-03-2'
citation-detection-irc1: Line 29: Check for possible unrecognized nick '2008-06-03-3'
citation-detection-irc1: Line 31: Check for possible unrecognized nick '2008-06-03-4'
citation-detection-irc1: Line 33: Check for possible unrecognized nick '2008-06-03-5'
citation-detection-irc1: Line 35: Check for possible unrecognized nick '2008-06-03-6'
citation-detection-irc1: Line 37: Check for possible unrecognized nick '2008-06-03-7'
citation-detection-irc1: Line 39: Check for possible unrecognized nick '2008-06-03-8'
citation-detection-irc1: Line 41: Check for possible unrecognized nick '2008-06-03-9'
citation-detection-irc1: Line 43: Check for possible unrecognized nick '2008-06-03-10'
citation-detection-irc1: Line 45: Check for possible unrecognized nick '2008-06-03-11'
citation-detection-irc1: Line 47: Check for possible unrecognized nick '2008-06-03-12'
citation-detection-irc1: Line 49: Check for possible unrecognized nick '2008-06-03-13'
citation-detection-irc1: Line 51: Check for possible unrecognized nick '2008-06-03-14'
citation-detection-irc1: Line 53: Check for possible unrecognized nick '2008-06-03-15'
citation-detection-irc1: Line 55: Check for possible unrecognized nick '2008-06-03-16'
citation-detection-irc1: Line 59: Check for possible unrecognized nick 'ISSUE 67'
citation-detection-irc1: Line 60: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 62: Check for possible unrecognized nick 'ISSUE 68'
citation-detection-irc1: Line 63: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 65: Check for possible unrecognized nick 'ISSUE 69'
citation-detection-irc1: Line 66: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 71: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 76: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 78: Check for possible unrecognized nick 'Discussion'
citation-detection-irc1: Line 79: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 83: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 88: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 93: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 98: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 103: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 109: Check for possible unrecognized nick 'http'
edit-substitute: command on line 211 succeeded, changed line 201 from 'Aupperly' to 'Aupperle'
edit-substitute: command on line 211 succeeded, changed line 205 from 'Aupperly' to 'Aupperle'
edit-substitute: command on line 227 succeeded, changed line 207 from 'ansih:' to 'anish:'
edit-substitute: command on line 211 succeeded, changed line 209 from 'Aupperly' to 'Aupperle'
edit-delete: Line 211 was deleted
edit-delete: Line 227 was deleted
system: Transformer: SAXON 8.9
[End of Schreiber diagnostic output]