[rus-wg] RUS Specification - users

[John Ainsworth]

I think there are three possible ways to proceed.
1. Remove Section 3 from the document. This leaves it up to each 
implementation to define how many different roles they have and what 
each role is permitted to do. As far as I can see this would have no 
impact on the service interface definition, though we may have to tidy 
up the text of section 5 a bit. I favour this approach.
2. Add a third class of user. This user is permitted to perform queries 
(read operations) on the RUS, and the resources for which they have 
permission are configured in the same way as the Resource Manager user 
class. An operator may configure zero or more users in this class.
3. As an option, permit any user to perform a query on the RUS, 
returning only the records where the GlobalUserId corresponds to the 
identity which they present when invoking the operation.

I don't find the text in 5.5.1 confusing - its talking about Resource 
Managers.

best regards
John

On 8 Apr 2005, at 07:14, Steven Newhouse wrote:

>> Some of the text seems to do this e.g. In the
>> RUS::extractRecords (Section 5.5.1).
>
> That particular bit of text does seem confusing - its reference to 
> users & roles. As authorisation is covered elsewhere in the document 
> I'd suggest removing it from here.
>
> Thoughts?
>
> Steven
> -- 
> ----------------------------------------------------------------
> Dr Steven Newhouse                        Tel:+44 (0)2380 598789
> Deputy Director, Open Middleware Infrastructure Institute (OMII)
> Suite 6005, Faraday Building (B21), Highfield Campus,
> Southampton University, Highfield, Southampton, SO17 1BJ,  UK
>
>
>