[rus-wg] RUS Specification - users

[Steven Newhouse]

>  In the document you identify only two classes of user as having access to
> data stored within the RUS - I guess that you mean the ability to view and
> modify URs. Should you also note that there are classes of user that have
> only read access - the grid user running jobs should be able to view her
> URs, PIs can view the URs of a project, VO manager can view the URs of jobs
> from her VO etc (all requiring access policies etc)

The OGSI version of the RUS specification had slightly richer user 
model... but I feel the current model reflects better the operational 
reality. How many of these users/PIs will want to be generating 
XPath/XQuery statements to extract data from a web service? Probably 
very few.

How many of these users are much more likely to use a yet undefined web 
portal to view their data? Most of them. Access control rules within the 
portal can be used by the RUS administrator to define who is allowed 
access to what. An the implementation layer they can use their access to 
everything within RUS to return the relevant records required by 
authorised queries.

This would seem to capture a lot of the common use cases btu leave a 
very simple authorisation model for the service implementator...

Comments?

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