[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-82) Propose method for access context discovery
[ https://issues.oasis-open.org/browse/OSLCCORE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Crossley updated OSLCCORE-82: ---------------------------------- Proposal: Separate access control (including discovery of access control) from TRS. Note that access control was not part of TRS 2.0, but was only described in the never-standardized ILDP document. That leaves this issue open, but with less urgency (and more freedom) to resolve it. > Propose method for access context discovery > ------------------------------------------- > > Key: OSLCCORE-82 > URL: https://issues.oasis-open.org/browse/OSLCCORE-82 > Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC > Issue Type: Improvement > Components: TRS > Reporter: Martin Sarabura > Assignee: Axel Reichwein > Priority: Major > Labels: TRS > > Currently I believe we don't specify how to discover access contexts in our Tracked Resource Specification. We need to fill this gap. -- This message was sent by Atlassian JIRA (v7.7.2#77003)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]