[OASIS Issue Tracker] (OSLCCORE-79) Consider defining a more general approach than a fixed JSON-LD format

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

     [ https://issues.oasis-open.org/browse/OSLCCORE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Crossley updated OSLCCORE-79:
----------------------------------
    Proposal: 
Separate access control (including resource representations) 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.

> Consider defining a more general approach than a fixed JSON-LD format
> ---------------------------------------------------------------------
>
>                 Key: OSLCCORE-79
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-79
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: TRS
>            Reporter: Martin Sarabura
>            Assignee: James Amsden
>            Priority: Major
>
> For the TRS spec, can we use a more general approach?
> Jim says it is brittle...



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)