[OASIS Issue Tracker] Created: (ODATA-601) Investigate enhancements to interoperability and feature set of OData JSON through JSON-LD

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

Investigate enhancements to interoperability and feature set of OData JSON through JSON-LD
------------------------------------------------------------------------------------------

                 Key: ODATA-601
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-601
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData JSON Format
    Affects Versions: V4.0_OS
            Reporter: Stefan Drees
             Fix For: V4.1_WD01


Driven by current analysis of JSON-LD in the GeoJSON community, I kindly suggest we investigate how JSON-LD (A JSON-based Serialization for Linked Data) might be mixed into OData JSON to avoid interoperability problems when our annotation and referencing style meets the "@" key culture of JSON-LD.

Specification: URL=http://www.w3.org/TR/json-ld/ 
and Community URL=http://json-ld.org/

Writing while thinking about it: Maybe a vocabulary might enable aliasing of the keys for JSON-LD overlapped concepts?

Citing JSON-LD 3.3 "Syntax Tokens and Keywords" to go "in medias res":

"""
JSON-LD specifies a number of syntax tokens and keywords that are a core part of the language:

@context
Used to define the short-hand names that are used throughout a JSON-LD document. These short-hand names are called terms and help developers to express specific identifiers in a compact manner. The @context keyword is described in detail in section 5.1 The Context.
@id
Used to uniquely identify things that are being described in the document with IRIs or blank node identifiers. This keyword is described in section 5.3 Node Identifiers.
@value
Used to specify the data that is associated with a particular property in the graph. This keyword is described in section 6.9 String Internationalization and section 6.4 Typed Values.
@language
Used to specify the language for a particular string value or the default language of a JSON-LD document. This keyword is described in section 6.9 String Internationalization.
@type
Used to set the data type of a node or typed value. This keyword is described in section 6.4 Typed Values.
@container
Used to set the default container type for a term. This keyword is described in section 6.11 Sets and Lists.
@list
Used to express an ordered set of data. This keyword is described in section 6.11 Sets and Lists.
@set
Used to express an unordered set of data and to ensure that values are always represented as arrays. This keyword is described in section 6.11 Sets and Lists.
@reverse
Used to express reverse properties. This keyword is described in section 6.12 Reverse Properties.
@index
Used to specify that a container is used to index information and that processing should continue deeper into a JSON data structure. This keyword is described in section 6.16 Data Indexing.
@base
Used to set the base IRI against which relative IRIs are resolved. This keyword is described in section 6.1 Base IRI.
@vocab
Used to expand properties and values in @type with a common prefix IRI. This keyword is described in section 6.2 Default Vocabulary.
@graph
Used to express a graph. This keyword is described in section 6.13 Named Graphs.
:
The separator for JSON keys and values that use compact IRIs.
All keys, keywords, and values in JSON-LD are case-sensitive.
"""
citation source at URL=http://www.w3.org/TR/json-ld/#syntax-tokens-and-keywords

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira