[OASIS Issue Tracker] (OSLCCORE-68) Extend access context to support notion of delegation

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63539#comment-63539 ] 

Nick Crossley commented on OSLCCORE-68:
---------------------------------------

Example updated to be more complete, to use more opaque URIs, and to mention delegation loops and limits.
There are no access control properties in access context resources, so there is no need for the non-normative note suggested in the previous comment.

> Extend access context to support notion of delegation
> -----------------------------------------------------
>
>                 Key: OSLCCORE-68
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-68
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Nick Crossley
>            Assignee: James Amsden
>
> There are examples of scenarios where the access context of a large number of resources is affected by an external change.  For example, in a task tracking system, you might need to update the access for a large number of tasks if the work is reassigned to a different release, or to a different team.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)