RE: Read-Only Provider

["John, Anil" <Anil.John@jhuapl.edu>]

Gary & All,

Unfortunately I will not be able to be on the call on Monday as I am on travel at that time and Tom, who is my alternate, is currently on vacation. Gary has been working off-line on this with us to put this in a consumable form, so I am hoping that questions that come can be answered.  I would be glad to answer any questions by e-mail as they come up.

Regards,

- Anil
________________________________________
From: Gary Cole [gary.cole@oracle.com]
Sent: Saturday, April 23, 2011 12:10 PM
To: OASIS PSTC
Cc: John, Anil; Smith, Thomas C.
Subject: Read-Only Provider

Another use-case on the wiki is ready for review: http://wiki.oasis-open.org/provision/ReadOnlyProvider

The read-only provider use-case makes the case for considering a read-
only provider to be conformant.  Currently, SPMLv2 requires a provider
to support the core operations, including add, modify and delete.
Anil John raised this use-case, supported by Thomas Smith.

I will ask Richard Sand to schedule this use-case for review during
the next PSTC meeting on Monday, 4/25.  I realize that this is short
notice, but the write-up is only about 3 pages and the business-level
use-case is fairly straightforward.  If at the time of the meeting
participants feel that they need more time to prepare, we can delay
the review.

Gary

ps.  Please peruse the current list of potential use-cases on the
wiki: http://wiki.oasis-open.org/provision/PotentialUseCases
- So far, only ForgotMyPassword and ReadOnlyProvider have been written
up according to the template.
- I've discussed with Anil on the list some aspects of simple search
that might bear on a SimpleProfile.
- Dan Perry and Richard Sand plan to work on Synchronization
Capabilities.
- We need volunteers to write up additional use-cases: pick your
favorite!