Authorization Delegation

We had a long discussion yesterday in the teleconf on Delegation. Some things
that we thought would be useful would be to improve the wiki page for it by
http://www.w3.org/wiki/WebID/Delegation

  - adding use cases 
  - add pointer to the original mailing list discussion
     http://lists.w3.org/Archives/Public/public-webid/2012Jun/0012.html
    (and perhaps summarise the other options listed there)
  - improve the flow description 
    + show what the header sent would look like exactly
    + show what the returned message would look like
    + explain in detail the process the Guard would have to follow to decide what to do
    + (perhaps improve the diagram)
    + there is no mention even there of the Acting-on-behalf-of: header we discussed 
  - Mike Jones distinguished between 
    authorization delegation / identity delegation / capability delegation
    Here we are dealing with authorisation delegation - the secretary is authenticating as itself
  - emphasise the importance of the Acting-on-behalf-of: header to Andrei's use case where a resource
    may return different representations depending on who is asking. (question on RESTfulness of such
    a service)
  - also note on how some of this could be achieved without an Acting-on-behalf-of header by the server
    returning in its header a pointer to an access control ontology that might restrict in some way who
    can see that resource - leaving it to the agent to read that ACL and act on it. (the secretary would of
    course have to declare in its foaf that it is an understander-of-that-acl ontology )
    (part of other solutions space)

All this should be very clearly set out, so that we can later go to the HTTPbis working group
and present this, to get their feedback. The clearer it is the better and more useful the 
discussion should there should be.

Henry

Social Web Architect
http://bblfish.net/

Received on Wednesday, 4 July 2012 11:36:31 UTC