is bob going to dial in from Aruba;-)
Are we going to hear the splashing of waves & the chink of glasses??
Agenda accepted as posted
Approval of Minutes
Revised minutes from 2011-03-29
Resolution: Minutes of 2011-03-29 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
Chairs not available for 2011-04-12
Resolution: Meeting of 2011-04-12 cancelled w/o
Notes meeting of 2011-04-26 has also been cancelled
Encourages TC to discuss on E-mail list
1.1 Open Issues
ASSEMBLY 261: (v1.1) Upgrade ASM12017, ASM12030, ASM14004 be mandatory statements
Reviews "service unavailable fault"
...reverses proposal for 12017
...without extensive review of impact on bindings (& subsequent revision) can't really be made mandatory
Java spec has a "service unavailable" exception, which could be used
But not available in other language specs, so not required
C/C++ spec is difficult to include specific faults for all clients
Observes a WSDL definition should be enough to completely specify
...not suggesting that this is done (for 1.1) but could be (for 1.2)
Changed proposals for 12017, 14004
Just need to remove last para of section 11.2
...This also removes 14003, which is incorrect
Section 11.1 & 14005 cover all situations anyway
Resolution for ASSEMBLY-260 (last meeting) also removes 14001 & 14002
...Section then just becomes explanitory (apart from 14005)
Would like Assembly spec to clearly specify fault even if language specs don't handle it
Could expand section 11 (later) but too much work to do a proper job for 1.1
Motion: Resolve ASSEMBLY-261 with updated proposal in JIRA (2nd for 12017, 14004) & remove last para of 11.2 14003 m=MartinC s=AnishK
12030 seems definitional rather than really normative
motion includes the original proposal for ASM12030
A SHOULD in 12030 makes no sense at all - upgrading to a MUST seemed more sensible
No further discussion - No objections
Resolution: ASSEMBLY-261 is resolved with updated proposals for 12017, 14004 and original proposal for 12030 w/o
+1 to merging TAs and TCs
Discussion regarding impact on TA's & TC's
Do TA's, TC's and spec reference each other appropriately?
Not in current CD of spec
the TC doc does reference the zip file in the related works section on the front page
Action: Clean up references to Test Cases in spec (1.1 and 1.2 changes non-normative) owner=Editors
Action: Raise issue for changes to TA & TC docs required by ASSEMBLY-260, etc owner=MikeE;
1.2 Open Issues
ASSEMBLY-239: (1.2): Business data filter element needs better name, definition
don't we need peter for this issue?
Reviews the two alternate proposals
To summarize - do we want a "." in the name and do we need to allow more than one filter type?
...e.g. would we be ever go to XPath2 and want to do this without making any other changes
Need directional guidance before making any progress
Please review for next meeting
Could Peter and/or Eric summarize to E-mail list
Many thanks for scribing Eric
Straggler Roll - DannyV JimM PeterN
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Date not specified, the date '2011-04-05' 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 75 input lines
edits: Schreiber found no text-edit commands
command-scribe: Line 3: Scribe 'Eric Wells' is recognized by use of the nick 'EricW'
command-scribe: Line 3: EricW's nick 'EricW' has been selected
citation-detection-scribed: Line 82: Check for possible unrecognized nick 'Alternate proposals'
citation-detection-scribed: Line 97: Check for possible unrecognized nick 'Roll is at'
citation-detection-scribed: Line 98: Check for possible unrecognized nick 'COB 9'
system: Transformer: SAXON 184.108.40.206
[End of Schreiber diagnostic output]