OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsn message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: WSN minutes of 11-08-2004


Quorum reached.
 
Sept 13th minutes... approved.
 
F2F minutes as a block... approved.
 
AIs...
 
NEW ACTION: DavidH, Preventing unwanted subscriptions use case.
 
Modification of the time of the conf call... NO
 
Potential issues...
    1. Use of the wsrp:Dialect attribute. What is the default? WSRF needs to clarify.
        SteveG: Make it mandatory or give interpretation for it not being present.
        Peter: Or just declare one in WSN there or not even have Dialect and go for contained elements.
        Igor: contaned elements limit extensibility as there is a need to standardize conteiner elements somewhere
 
NEW ACTION: Peter and Steve to write the clarification of wsrp:Dialect use. I.e. why this element is valuable and how is it applicable to the WSN uses.
 
NEW ACTION: Sanjay to create new issue on use of wsrp:Dialect. http://www.oasis-open.org/archives/wsn/200411/msg00009.html
 
    2. DavidH proposal on the value of distributors
        Peter: this may be addressed by the brokered N
        DavidH: no it is not broketed
        Peter: this is indirect notification which is the issue of the broker. It will be distributing.
        DavidH: bundling a set of params and policies for multiple subscriptions (??)
        DavidH: describes a queueing use case
        Fred: it seems like a patterns of use, which could be built what exists already
        DavidH: the specificaation needs to cover simple delivery case and layer on top
        Peter: is the proposal to decouple poll interfaces from notification producer
        DavidH: yes, and everything else decoupled from the simple notification interface. e.g. state management (??)
        ... What is the difference between this and brokers subscribing to brokers....
        DavidH: the concern is to keep basic notification minimal
        DavidH: not have specific, and open-ended delivery scenarios baked into the basic spec. Filtering stays, but things like Notify go away.
        DavidH: composeable delivery mechanisms i.e. some may also be shared by several subscriptions
        Proposed issue: factor delivery options into a separate object
 
Left undecided for discussion on future calls.
 
Other business.
    Peter: request from SteveG. Mark as resolved the changes that were made. Interested parties need to review this by Thu.
    Looking for a volunteer... DavidH will do this.
 
NEW ACTION: DavidH to verify if SteveG's changes resolved the issues.
 
    William: vonunteers for WS-Topics editors
    Igor volunteered. Group did not object.
 

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 

 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]