Roll call - 12/18 = 66% Quorate - OK For new issues
Discussion of Exit Criteria added to Administrivia
What about new issues rasied today?
Too much to discuss already today - not added
No comments or objections
Resolution: Minutes of 2011-02-08 approved w/o
Action: id=2010-09-22-8 status=pending owner="EricJ" produce new proposal for ASSEMBLY-227
Action: id=2011-01-04-2 status=pending Edwards to write a new proposal for the resolution of Assembly-246 along the lines contained
Have heard nothing from OASIS Admin - will need to chase
There has been no discussion of exit criteria
Do we need to distinguish between 1.1 and 1.2?
Up to the TC, but we need to have the discussion
Not included in agena - no discussion
Open Issues 1.2
Review's his proposal
Probably need a directional statement at moment then prepare final proposal
Element (current name) is used in two places - will need new element for local
TC had previously agreed to change ##any
This (substitution group) needs to be corectly handled
Some (Java) products define event types and filters in terms of Java classes
...favors PeterN's implementation
Can't distinguish between extention parts that are optional/mandatory - no Global "MustUnderstand"
the "one of something" point that Eric makes does not apply to bindings, I note
I can have a <reference/> containing both a <binidng.ws/> and a <binding.jms/>
Don't this this applies as that's only the case for "one or more" not for "zero or more"
mike, i agree, that is why i'm in the Q
Only reason that we do not have a eventTypes.java yet is that the Java-TC is too swamped with 1.1 work and has not done anything
on 1.2 so far.
Detailed discussion on how this relates to bindings
Can we make a decision or more discussion?
Also XPath1, XPath2 is part of element name - should this be an attribute no part of name?
This made some things more difficult
We did discuss this in detail some time ago, but I can't recall when exactly
...decided(?) to include in name
Motion: Resolve ASSEMBLY-239 in direction of using Substitution groups (as per PeterN's) E-mail m=BryanA s=AshokM
Reference to PeterN's E-mail
Naming of element is separate from use of substitution groups
Only directional at present - we could consider details like names later
Propose ammendment to restrict direction to ONLY substitution group part of proposal
Amendment: Restrict direction of proposal for ASSEMBLY-239 to use of substitution groups only m=DannyV s=EricJ
this is directional, so the details e.g. names are open to discussion
Some discussion of what amendment means
+1 to Bryan
Basically just restrict consideration to parts of original E-mail that addresses substitution groups ONLY - nothing else
Don't want to have to reorganize document and require a super majority to change later
Call the question on the amendment
No objection to amendment?
Call the question on main motion
Time Expired - motion dies
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Date not specified, the date '2011-02-15' was assumed
final validation: Title not specified, default title 'Oasis SCA-Assembly Teleconference...' was assumed
final validation: Chair not specified, default chair was assumed
statistics: Schreiber found 73 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 3: s/1. Intro/agenda: 1. Intro/
edit-substitute: command on line 3 succeeded, changed line 1 from '1. Intro' to 'agenda: 1. Intro'
command-scribe: Line 2: Scribe 'Eric Wells' is recognized by use of the nick 'EricW'
command-scribe: Line 2: EricW's nick 'EricW' has been selected
edit-delete: Line 3 was deleted
citation-detection-scribed: Line 99: Check for possible unrecognized nick 'COB 9'
citation-detection-scribed: Line 101: Check for possible unrecognized nick 'Roll is at'
system: Transformer: SAXON 184.108.40.206
[End of Schreiber diagnostic output]