wsn message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Minutes of call 08/05/06
- From: Matthew I Roberts <matt.roberts@uk.ibm.com>
- To: wsn@lists.oasis-open.org
- Date: Mon, 8 May 2006 17:50:44 +0100
All,
Please find attached the minutes from
today's conference call.
Thanks,
Matt
Matt Roberts
IBM WebSphere Messaging Design and Development
Hursley Park, England. +44 1962 815444
matt.roberts@uk.ibm.com
MP 211 / DE3H22
WSN minutes
Approval of minutes of 24th April
- no objections.
Action Items
AI 4 Peter
has sent some changes to Sanjay by email (no response as yet)
AI 5, 6, 7 can all be closed as completed
AI
7 is covered in email ref #2 (http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200605/msg00005.html)
Status of base and brokered PRDs
BaseN
David and Peter have prepared the public
review draft documents. Peter did a bit more proof reading at the same
time and found some mismatches between the schemas and the pseudo-schemas
as described in ref #3 (http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200605/msg00003.html).
Many changes related to cardinality
of {any} in pseudo-schema.
The Approval process requires us to
issue a new committee draft to implement these changes rather than sneaking
them in under the covers. Peter will post CD 4, which will have a ballot,
and subject to approval by ballot will be submitted for public review as
PRD 4. This will then have a 15 day public review, and we will ignore PRD
3 (deltas will all be from PRD 2 to PRD 4).
The only possibly controversial change
is the minOccurs=0 change to GetMessages (for the pull point). The pseudo
schema and text say that it is optional, but the existing schema had minOccurs=1.
Changing to minOccurs=0 will match the pseudo schema and text.
BrokeredN
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200605/msg00004.html
Main change of note was removing the
CurrentTime and TerminationTime resource property definitions that were
missed as part of WSN3.30.
No objections were raised.
Issue 4.29
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200605/msg00005.html
Peter scored each of the options based
on how well it satisfied each of four characteristics described in the
email. Option 3 scored the best points and was subsequently judged to be
the best by Peter and William.
Option 2 was judged to be a bit on the
woolly side and bad for interoperability. The problem with Option 1 was
an over complicated topic set document, whilst Option 4 is unable to satisfy
the 'purity of XPath expression' characteristic.
The only disadvantage of Option 3 is
that if you have an extension topic then you cannot use the simple queue
name expression to get to it. So you would have to use Concrete, Full,
or XPath topic dialects in order to address it.
This was proposed (Peter, David) and
accepted by the group.
Having completed this issue we can now
create a committee draft candidate document for WS-Topics.
WSN-Policy
William is not on the call this week
so Matt suggested deferring discussion of his proposal until a later call
David agreed that now that the ice has
been broken he will look at the continuity item he was assigned.
WSN-Primer
Most 'recent' email about this described
4 potential issues for the primer.
Need to reconcile the whitepaper material
and how it applies/moves into the primer. David agreed to look into this.
<end>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]