Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

JSON-LD: JSON for Linked Data

JSON-LD is a set of W3C standards track specifications for representing Linked Data in JSON. It is fully compatible with the RDF data model, but allows developers to work with data entirely within JSON.

No, colleagues is a property defined in http://schema.org. We create a prefix 'schema', and use it to mint a Compact IRI (or CURIE) as schema:colleagues. This is in keeping with general use of prefixes in many RDF syntaxes. If we were to use Person:colleagues, then the IRI would expand to http://schema.org/Personcolleagues. It might be better if there was a trailing '/' or '#', but this is not the namespace schema.org uses.

JSON is widely used for RESTful APIs, but there is no standard convention on representation, or the meaning of properties and values.\n

JSON is widely used for RESTful APIs, but there is no standard convention on representation, or the meaning of properties and values.\n

JSON is widely used for RESTful APIs, but there is no standard convention on representation, or the meaning of properties and values.\n

JSON-LD brings a standard representation for expressing entity-value relationships using a few standard keywords and a consistent organizational structure for JSON Objects.\nObjects represent entities, with keys acting as properties.\n Properties always expand to full IRIs.\nArrays express a set of values associated with a property, unordered by default.\n Order expressed in @context or as an expanded value representation.\nValues are Object, string or native, with standard XSD representations for native types.\n Expanded form allows for more datatype and language variations.\n

The @type key gives an object with one or more types, described with an IRI.\nThe @context provides a way to express IRIs as simple terms, and allows values to be typed.\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

Subject reference identifies an object with @id in the same document, or references an external document (Linked Data).\n

\n

\n

\n

\n

DBPedia currently uses a slightly out-of-date representation JSON-LD. But, by changing &amp;#x201C;@id&amp;#x201D; to &amp;#x201C;@graph&amp;#x201D;, and providing a context to identify IRIs, it can be processed as JSON-LD.\n

RDFa to JSON-LD bookmarklet can turn RDFa directly into JSON-LD.\n

\n

Payswarm uses named graphs to be able to sign data. The signature in the default graph signs the content of the named graph, through a separate normalization step.\n

Expansion is a core JSON-LD algorithm, used to normalize input documents to aide in processing.\n

Compaction creates a more human-readable form, but is often used as the final step in framing.\n

Framing is like SPARQL for JSON-LD, allows documents to be restructured using @type and property definitions and object relationships.\n

Framing is like SPARQL for JSON-LD, allows documents to be restructured using @type and property definitions and object relationships.\n

Normal JSON can be made JSON-LD by adding an external context through an HTTP link relation.\n

JSON-LD macros can turn more ideomatic JSON into conforming JSON-LD with standardized transformation.\n

JSON-LD macros can turn more ideomatic JSON into conforming JSON-LD with standardized transformation.\n

JSON-LD macros can turn more ideomatic JSON into conforming JSON-LD with standardized transformation.\n

JSON-LD macros can turn more ideomatic JSON into conforming JSON-LD with standardized transformation.\n

\n

\n

Full transformation from and to the RDF data model as a normative part of the API.\n

Full transformation from and to the RDF data model as a normative part of the API.\n