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

 


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

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


Subject: Groups - SPML V2 Working group Call added



SPML V2 Working group Call has been added by Darran Rolls (Darran.Rolls@sun.com).

Date:  Tuesday, 10 August 2004
Time:  11:00am - 12:00pm Eastern Time

Event Description:
Bi-weekly working group call - RELATIONSHIPS

Dial In Number (866) 545-5223
International (865) 673-9887
Access Code: 5272389


Agenda:
1) Should relationship operations re-use/extend core verbs?
   Jeff Bohren has proposed the following:
   - spmlcontain:add (since add may require containment).
   - spmlref:add (desirable to minimize SPML calls).
   - use spml:modify to add/replace/remove connections.
   - use spml:modify to update complex connection info.
   - use search to query by reference relationship.

   pro: keeps protocol simple (adds fewer verbs).
   con: makes protocol confusing (overloading; bad pattern).
   pro: containment sometimes required as part of create.
   pro: references desirable as part of create (fewer calls).


2) Represent each complex connection as a PSO?
   pro: keeps protocol simple (adds fewer verbs).
   con: scalability burden on provider (ID namespace).
   con: scales worse than native resource (e.g., RACF).
   rebuttal: complex connections are rare.
             Since most connection types are simple,
             benefit of simplicity outweighs burden of scale.

3) Does target declare capabilities globally or per PSO type?
   Gary thought "globally"; Jeff Bohren says it could be either.
   Does this make sense for other capabilities
   (beyond containment and reference relationships)?

4) Modifications - need to flesh out more fully.

5) Search - need to specify syntax more fully.


Minutes:

View event details:
http://www.oasis-open.org/apps/org/workgroup/provision/event.php?event_id=5746

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web
browser.




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