[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=62779#comment-62779 ] 

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

To be discussed: should the delegated indication be a separate property, as in the current proposal, or should it be just an extra (or sub-) RDF type:

<https://a.example.com/access/category1/iteration30> 
   a acc:DelegatedAccessContext ; 
   acc:accessContext <https://a.example.com/access/teams/teamA> . 

where:

acc:DelegatedAccessContext a rdfs:Class ;
   rdfs:isSubClassOf acc:AccessContext .

> 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)