[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:comment-tabpanel&focusedCommentId=70105#comment-70105 ] 

Andrii Berezovskyi commented on OSLCCORE-79:
--------------------------------------------

The only place in the spec where I could find JSON-LD is [§13.2 Access Control|https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/trs/tracked-resource-set.html#accList]. And it does mandate a JSON-LD as the only RDF serialisation:
{quote}The response must be a JSON-LD format string
{quote}
and quite strongly recommends to stick to a predefined structure:
{quote}The response should use the simple @graph form with a default graph as shown in the example below. The response should use the @context value shown below (i.e., as a boilerplate header), and should not use other advanced JSON-LD features, since these can make the response more difficult to understand for human readers who only know JSON
{quote}

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