diff --git a/index.html b/index.html index 51be782..bd615f7 100644 --- a/index.html +++ b/index.html @@ -1,6 +1,6 @@ - + JSON-LD 1.0 @@ -261,6 +261,24 @@ background: #e9fbe9; } + + + @@ -268,27 +286,41 @@ + + +
-

Abstract

-

JSON is a useful data serialization and messaging format. - This specification defines JSON-LD, a JSON-based format to serialize Linked Data. - The syntax is designed to easily integrate into deployed systems that already use JSON, - and provides a smooth upgrade path from JSON to JSON-LD. - It is primarily intended to be a way to use Linked Data in Web-based programming environments, - to build interoperable Web services, and to store Linked Data in JSON-based storage engines. +

Resumo

+

JSON é um formato de mensagens e serialização de dados úteis. + Essa especificação define JSON-LD, um formato baseado em JSON para serializar Dados Linkados. + A sintaxe é projetada para integrar facilmente em sistemas implantados que já usam JSON, + e fornece um caminho de atualização suave do JSON para JSON-LD. + Destina-se principalmente para ser uma maneira de usar Dados Linkados em ambientes de programação baseada na Web, + para construir serviços Web interoperáveis e para armazenar Dados Linkados em mecanismos de armazenamento baseados em JSON.

-

Status of This Document

+

Situação Deste Documento

- This section describes the status of this document at the time of its publication. - Other documents may supersede this document. - A list of current W3C publications and the latest revision - of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. + Esta seção descreve a situação deste documento no momento da sua publicação. + Outros documentos podem substituir este documento. + A lista das atuais publicações da W3C e a última revisão + deste relatório técnico pode ser encontrado no índice de relatórios técnicos da W3C em http://www.w3.org/TR/.

-

This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, - and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material r cited from another document. - W3C's - role in making the Recommendation is to draw attention to the specification - and to promote its widespread deployment. This enhances the functionality and - interoperability of the Web.

+

Este documento foi revisado por membros do W3C, por desenvolvedores de software, e por outros grupos da W3C e partes interessadas, + e é endossado pelo Diretor como uma Recomendação da W3C. É um documento estável e pode ser usado como material de referência ou citado em outro documento. + Papel do W3C + em fazer a recomendação é para chamar a atenção para a especificação + e promover sua implantação generalizada. Isto melhora a funcionalidade e a + interoperabilidade da Web.

-

This specification has been developed by the JSON for Linking Data Community Group before it has been transferred to the RDF Working Group for review, improvement, - and publication along the Recommendation track. - The document contains small editorial changes arising from comments received during the Proposed Recommendation review; - see the - diff-marked version for details.

+ -

There are several independent interoperable implementations of this specification. - An - implementation report as of October 2013 is available.

+

Esta especificação foi desenvolvida pelo JSON for Linking Data Community Group antes de ser transferida para o RDF Working Group para revisão, melhoria + e publicação na trilha de Recomendação. + O documento contém pequenas alterações de redação, decorrentes de comentários recebidos durante a revisão da Proposta de Recomendação; + Veja a + versão com diferenças marcadas para mais detalhes.

+ +

Existem várias implementações interoperacionais independentes desta especificação. + Um + relatório de implementações em Outubro de 2013 está disponível.

- This document was published by the RDF Working Group as a Recommendation. If you wish to make comments regarding this document, - please send them to + Este documento foi publicado pelo RDF Working Group como uma Recomendação. Se você deseja fazer comentários sobre este documento, + por favor os envie para public-rdf-comments@w3.org ( - subscribe, - archives). - All comments are welcome.

+ inscrever-se, + arquivos). + Todos os comentários são bem vindos.

- This document was produced by a group operating under the + Este documento foi produzido por um grupo que opera sob a + + Política de Patentes da W3C de fevereiro de 2004. + + W3C mantém uma lista pública de divulgação de patentes feita em conexão + com as entregas do grupo; essa página também inclui instruções para a + divulgação de uma patente. - 5 February 2004 W3C Patent Policy. + - W3C maintains a public list of any patent disclosures made in connection - with the deliverables of the group; that page also includes instructions for - disclosing a patent. An individual who has actual knowledge of a patent which - the individual believes contains - Essential Claim(s) must disclose the information in accordance with section - 6 of the W3C Patent Policy. + Uma pessoa que tenha conhecimento de uma patente que + esta pessoa acredita conter + "Reivindicações essenciais" deve divulgar as informações de acordo com a + seção + 6 da Política de Patentes do W3C.

-

Table of Contents

+

Índice de conteúdo

@@ -689,9 +738,10 @@

3.

3.1 General Terminology

-

This document uses the following terms as defined in JSON [RFC4627]. - Refer to the JSON Grammar section in [RFC4627] - for formal definitions.

+

+ This document uses the following terms as defined in JSON [RFC4627]. + Refer to the JSON Grammar section in [RFC4627] for formal definitions. +

JSON object
@@ -700,29 +750,29 @@

string. A single colon comes after each key, separating the key from the value. A single comma separates a value from a following key. - In contrast to JSON, in JSON-LD the keys in an object must be unique. + In contrast to JSON, in JSON-LD the keys in an object must be unique. +
array
-
An array structure is represented as square brackets surrounding zero or - more values. Values are separated by commas. In JSON, an array is an ordered sequence of zero or more values. While JSON-LD uses the same array representation - as JSON, the collection is unordered by default. While order is - preserved in regular JSON arrays, it is not in regular JSON-LD arrays unless - specifically defined (see section 6.11 Sets and Lists).
+
+ An array structure is represented as square brackets surrounding zero or more values. + Values are separated by commas. + In JSON, an array is an ordered sequence of zero or more values. + While JSON-LD uses the same array representation as JSON, the collection is unordered by default. + While order is preserved in regular JSON arrays, it is not in regular JSON-LD arrays unless specifically defined + (see section 6.11 Sets and Lists). +
string
- A string is a sequence of zero or more Unicode characters, wrapped in double quotes, - using backslash escapes (if necessary).
-
number
-
A number is similar to that used in most programming languages, except that - the octal and hexadecimal formats are not used and leading zeros are not - allowed. + A string is a sequence of zero or more Unicode characters, wrapped in double quotes, using backslash escapes (if necessary).
+
number
+
A number is similar to that used in most programming languages, except that the octal and hexadecimal formats are not used and leading zeros are not allowed.
true and false
-
- Values that are used to express one of two possible boolean states.
+
Values that are used to express one of two possible boolean states.
null
-
The null value, - which is typically used to clear or forget data. For example, a key-value - pair in the +
+ The null value, which is typically used to clear or forget data. + For example, a key-value pair in the @context where the value is null explicitly decouples a term's association with an IRI. @@ -731,16 +781,17 @@

null in expanded form, - then the entire JSON object is ignored.

+ then the entire JSON object is ignored. +

3.2 Data Model Overview

-

This section is non-normative.

+

Esta seção é não-normativa.

-

Generally speaking, the data model used for JSON-LD is a labeled, directed - graph. +

+ Generally speaking, the data model used for JSON-LD is a labeled, directed graph. The graph contains nodes, which are connected by edges. @@ -760,9 +811,9 @@

7. Data Model.

-

Developers who are familiar with Linked Data technologies will recognize the - data model as the RDF Data Model. To dive deeper into how JSON-LD and RDF - are related, see section +

+ Developers who are familiar with Linked Data technologies will recognize the data model as the RDF Data Model. + To dive deeper into how JSON-LD and RDF are related, see section 9. Relationship to RDF.

@@ -770,71 +821,83 @@

3.3 Syntax Tokens and Keywords

-

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

+

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 identifiersin - a compact manner. The @context keyword is described in detail - in - section 5.1 The 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 identifiersin 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.
+
+ 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.
+
+ 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.
+
+ 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 +
+ Used to set the data type of a node or typed value. This keyword is described in - section 6.4 Typed Values.
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
The separator for JSON keys and values that use compact IRIs.
-

All keys, keywords, - and values in JSON-LD are case-sensitive.

+

All keys, keywords, and values in JSON-LD are case-sensitive.

@@ -842,11 +905,12 @@

4. Conformance

-

This specification describes the conformance criteria for JSON-LD documents. +

+ This specification describes the conformance criteria for JSON-LD documents. This criteria is relevant to authors and authoring tool implementers. - As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, - and notes in this specification are non-normative. - Everything else in this specification is normative.

+ As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. + Everything else in this specification is normative. +

A JSON-LD document complies with this specification if it follows the normative statements in appendix 8. JSON-LD Grammar. @@ -869,7 +933,7 @@

4.

5. Basic Concepts

-

This section is non-normative.

+

Esta seção é não-normativa.

JSON [RFC4627] is a lightweight, language-independent data interchange format. @@ -931,7 +995,7 @@

5.

5.1 The Context

-

This section is non-normative.

+

Esta seção é não-normativa.

When two people communicate with one another, the conversation takes place in a shared environment, typically called "the context of the conversation". @@ -958,19 +1022,19 @@

5.1
Example 3: Context for the sample document in the previous section
{
-          "@context":
+  "@context":
   {
-    "name": "http://schema.org/name", ← This means that 'name' is shorthand for 'http://schema.org/name'          
+    "name": "http://schema.org/name",  ← This means that 'name' is shorthand for 'http://schema.org/name' 
     "image": {
-      "@id": "http://schema.org/image", ← This means that 'image' is shorthand for 'http://schema.org/image'          
-      "@type": "@id" ← This means that a string value associated with 'image' should be interpreted as an identifier that is an IRI          
+      "@id": "http://schema.org/image",  ← This means that 'image' is shorthand for 'http://schema.org/image' 
+      "@type": "@id"  ← This means that a string value associated with 'image' should be interpreted as an identifier that is an IRI 
     },
     "homepage": {
-      "@id": "http://schema.org/url", ← This means that 'homepage' is shorthand for 'http://schema.org/url'          
-      "@type": "@id" ← This means that a string value associated with 'homepage' should be interpreted as an identifier that is an IRI          
+      "@id": "http://schema.org/url",  ← This means that 'homepage' is shorthand for 'http://schema.org/url' 
+      "@type": "@id"  ← This means that a string value associated with 'homepage' should be interpreted as an identifier that is an IRI 
     }
-  } }
-
+ } +}

As the context above shows, the value of a term definition can either be a simple string, mapping the 5.1

5.2 IRIs

-

This section is non-normative.

+

Esta seção é não-normativa.

IRIs (Internationalized Resource Identifiers [ @@ -1113,13 +1177,14 @@

5.2 IR
Example 9: Term expansion from context definition
- 
{ "
-          @context": { "
-          name": "http://schema.org/name"
-          }, "
-          name": "Manu Sporny", "status": "trollin'"
-          }
-
+ 
{
+  "@context":
+  {
+    "name": "http://schema.org/name"
+  },
+  "name": "Manu Sporny",
+  "status": "trollin'"
+}

JSON keys that do not expand to an 5.2 IR

5.3 Node Identifiers

-

This section is non-normative.

+

Esta seção é não-normativa.

To be able to externally reference nodes in a 5

5.4 Specifying the Type

-

This section is non-normative.

+

Esta seção é não-normativa.

The type of a particular node can be specified using the @type keyword. @@ -1287,7 +1352,7 @@

6.1 Base IRI

-

This section is non-normative.

+

Esta seção é não-normativa.

JSON-LD allows IRIs @@ -1302,10 +1367,13 @@

6.1
Example 15: Use a relative IRI as node identifier
- 
{ "@context": { "label": "http://www.w3.org/2000/01/rdf-schema#label" },
-          "@id": "", "label": "Just a simple document"
-          }
-
+ 
{
+  "@context": {
+    "label": "http://www.w3.org/2000/01/rdf-schema#label"
+  },
+  "@id": "",
+  "label": "Just a simple document"
+}

This document uses an empty @id, which resolves to the document @@ -1316,9 +1384,13 @@

6.1
Example 16: Setting the document base in a document
- 
{ "@context": {
-          "@base": "http://example.com/document.jsonld"          }, "@id": "", "label": "Just a simple document" }
-
+ 
{
+  "@context": {
+    "@base": "http://example.com/document.jsonld"
+  },
+  "@id": "",
+  "label": "Just a simple document"
+}

Setting @base to null will prevent @@ -1332,7 +1404,7 @@

6.1

6.2 Default Vocabulary

-

This section is non-normative.

+

Esta seção é não-normativa.

At times, all properties and types may come from the same vocabulary. JSON-LD's @vocab keyword allows an author to set a common prefix to be @@ -1363,17 +1435,23 @@

Example 18: Using the null keyword to ignore data
- 
{ "@context": { "@vocab": "http://schema.org/",
-          "databaseId": null }, "@id": "http://example.org/places#BrewEats",
-          "@type": "Restaurant", "name": "Brew Eats",
-          "databaseId": "23987520" }
-
+ 
{
+  "@context":
+  {
+     "@vocab": "http://schema.org/",
+     "databaseId": null
+  },
+    "@id": "http://example.org/places#BrewEats",
+    "@type": "Restaurant",
+    "name": "Brew Eats",
+    "databaseId": "23987520"
+}

6.3 Compact IRIs

-

This section is non-normative.

+

Esta seção é não-normativa.

A compact IRI is a way of expressing an IRI using a prefix and suffix separated by a colon (:). @@ -1442,7 +1520,7 @@

6.3 <

6.4 Typed Values

-

This section is non-normative.

+

Esta seção é não-normativa.

A value with an associated type, also known as a @@ -1470,16 +1548,19 @@

6.4 <
Example 21: Expanded term definition with type coercion
{
-          "@context":
+  "@context":
   {
     "modified":
     {
       "@id": "http://purl.org/dc/terms/modified",
       "@type": "http://www.w3.org/2001/XMLSchema#dateTime"
     }
-  }, ... "@id": "http://example.com/docs/1", "modified": "2010-05-29T14:17:39+02:00",
-          ... }
-
+ }, +... + "@id": "http://example.com/docs/1", + "modified": "2010-05-29T14:17:39+02:00", +... +}

The modified key's value above is automatically type coerced to a @@ -1605,7 +1686,7 @@

6.4 <

6.5 Type Coercion

-

This section is non-normative.

+

Esta seção é não-normativa.

JSON-LD supports the coercion of values to particular data types. Type coercion allows someone deploying @@ -1723,16 +1804,28 @@

6.5
Example 25: Term definitions using compact and absolute IRIs
- 
{ "@context": { "foaf": "http://xmlns.com/foaf/0.1/", "
-          foaf:age": {
-          "@id": "http://xmlns.com/foaf/0.1/age",
-          "@type": "xsd:integer" }, "
-          http://xmlns.com/foaf/0.1/homepage": { "@type":
-          "@id" } }, "foaf:name": "John Smith", "
-          foaf:age": "41", "
-          http://xmlns.com/foaf/0.1/homepage": [ "http://personal.example.org/",
-          "http://work.example.com/jsmith/" ] }
-
+ 
{
+  "@context":
+  {
+    "foaf": "http://xmlns.com/foaf/0.1/",
+    "foaf:age":
+    {
+      "@id": "http://xmlns.com/foaf/0.1/age",
+      "@type": "xsd:integer"
+    },
+    "http://xmlns.com/foaf/0.1/homepage":
+    {
+      "@type": "@id"
+    }
+  },
+  "foaf:name": "John Smith",
+  "foaf:age": "41",
+  "http://xmlns.com/foaf/0.1/homepage":
+  [
+    "http://personal.example.org/",
+    "http://work.example.com/jsmith/"
+  ]
+}

In this case the @id definition in the term definition is optional. @@ -1766,7 +1859,7 @@

6.5

6.6 Embedding

-

This section is non-normative.

+

Esta seção é não-normativa.

Embedding is a JSON-LD feature that allows an author to use 6.6

6.7 Advanced Context Usage

-

This section is non-normative.

+

Esta seção é não-normativa.

Section 5.1 The Context introduced the basics of what makes JSON-LD work. This section expands on the basic principles of the @@ -1876,14 +1969,16 @@

Example 29: Combining external and local contexts
{
-          "@context": [
+  "@context": [
     "http://json-ld.org/contexts/person.jsonld",
     {
       "pic": "http://xmlns.com/foaf/0.1/depiction"
     }
-  ], "name": "Manu Sporny", "homepage": "http://manu.sporny.org/",
-          "pic": "http://twitter.com/account/profile_image/manusporny"          }
-
+ ], + "name": "Manu Sporny", + "homepage": "http://manu.sporny.org/", + "pic": "http://twitter.com/account/profile_image/manusporny" +}
@@ -1973,7 +2068,7 @@

6.9 String Internationalization

-

This section is non-normative.

+

Esta seção é não-normativa.

At times, it is important to annotate a string with its language. In JSON-LD this is possible @@ -1984,13 +2079,14 @@

Example 31: Setting the default language of a JSON-LD document
{
-          "@context":
+  "@context":
   {
     ...
     "@language": "ja"
-  }, "name": "花澄", "occupation":
-          "科学者" }
-
+ }, + "name": "花澄", + "occupation": "科学者" +}

The example above would associate the ja language code with the @@ -2023,15 +2119,22 @@

Example 33: Expanded term definition with language
- 
{ "@context": { ... "ex": "http://example.com/vocab/", "@language": "ja",
-          "name": { "@id": "ex:name", "@language": null          }, "occupation": { "@id": "ex:occupation" }, "occupation_en": { "@id":
-          "ex:occupation", "@language": "en" }, "occupation_cs":
-          { "@id": "ex:occupation", "@language": "cs"          } },
-          "name": "Yagyū Muneyoshi",
+        
{
+  "@context": {
+    ...
+    "ex": "http://example.com/vocab/",
+    "@language": "ja",
+    "name": { "@id": "ex:name", "@language": null },
+    "occupation": { "@id": "ex:occupation" },
+    "occupation_en": { "@id": "ex:occupation", "@language": "en" },
+    "occupation_cs": { "@id": "ex:occupation", "@language": "cs" }
+  },
+  "name": "Yagyū Muneyoshi",
   "occupation": "忍者",
   "occupation_en": "Ninja",
-  "occupation_cs": "Nindža", ... }
-          

+  "occupation_cs": "Nindža",
+  ...
+}

The example above would associate 忍者 with the specified default language @@ -2057,13 +2160,21 @@

Example 34: Language map expressing a property in three languages
- 
{ "@context": { ... "occupation": { "@id": "ex:occupation", "@container": "@language"          } }, "name": "Yagyū Muneyoshi", "occupation":
-          {
+        
{
+  "@context":
+  {
+    ...
+    "occupation": { "@id": "ex:occupation", "@container": "@language" }
+  },
+  "name": "Yagyū Muneyoshi",
+  "occupation":
+  {
     "ja": "忍者",
     "en": "Ninja",
     "cs": "Nindža"
-  } ... }
-          

+  }
+  ...
+}

The example above expresses exactly the same information as the previous example @@ -2079,11 +2190,17 @@

Example 35: Overriding default language using an expanded value
- 
{ "@context": { ... "@language": "ja" }, "name": "花澄", "occupation":
-          { "@value": "Scientist", "@language": "en" }
-            
-            }
+ 
{
+  "@context": {
+    ...
+    "@language": "ja"
+  },
+  "name": "花澄",
+  "occupation": {
+    "@value": "Scientist",
+    "@language": "en"
+  }
+}

This makes it possible to specify a plain string by omitting the @@ -2112,7 +2229,7 @@

6.10 IRI Expansion within a Context

-

This section is non-normative.

+

Esta seção é não-normativa.

In general, normal IRI expansion rules apply anywhere an IRI is expected (see section 5.2 IRIs). Within a context definition, this can mean that terms defined within the context may also be used within that context as long as there are no circular dependencies. @@ -2211,12 +2328,24 @@

Example 40: Associating context definitions with absolute IRIs
- 
{ "@context": { "foaf": "http://xmlns.com/foaf/0.1/", "xsd": "http://www.w3.org/2001/XMLSchema#",
-          "name": "foaf:name", "foaf:age": { "@id": "foaf:age", "@type": "xsd:integer"
-          }, "
-          http://xmlns.com/foaf/0.1/homepage": { "@type":
-          "@id" } }, ... }
-
+ 
{
+  "@context":
+  {
+    "foaf": "http://xmlns.com/foaf/0.1/",
+    "xsd": "http://www.w3.org/2001/XMLSchema#",
+    "name": "foaf:name",
+    "foaf:age":
+    {
+      "@id": "foaf:age",
+      "@type": "xsd:integer"
+    },
+    "http://xmlns.com/foaf/0.1/homepage":
+    {
+      "@type": "@id"
+    }
+  },
+  ...
+}

In order for the absolute IRI to match above, the absolute IRI needs to be used in the

6.11 Sets and Lists

-

This section is non-normative.

+

Esta seção é não-normativa.

A JSON-LD author can express multiple values in a compact way by using arrays. Since @@ -2403,7 +2532,7 @@

6.1

6.12 Reverse Properties

-

This section is non-normative.

+

Esta seção é não-normativa.

JSON-LD serializes directed graphs. That means that every property points from a node to another node or value. @@ -2454,7 +2583,7 @@

6.13 Named Graphs

-

This section is non-normative.

+

Esta seção é não-normativa.

At times, it is necessary to make statements about a graph itself, rather than just a single @@ -2610,7 +2739,7 @@

6.13

6.14 Identifying Blank Nodes

-

This section is non-normative.

+

Esta seção é não-normativa.

At times, it becomes necessary to be able to express information without being able to uniquely identify the node with an IRI. @@ -2652,7 +2781,7 @@

6.15 Aliasing Keywords

-

This section is non-normative.

+

Esta seção é não-normativa.

Each of the JSON-LD keywords, except for @context, may be aliased to application-specific @@ -2683,7 +2812,7 @@

6.16 Data Indexing

-

This section is non-normative.

+

Esta seção é não-normativa.

Databases are typically used to make access to data more efficient. Developers often extend this sort of functionality into their application data to deliver @@ -2800,7 +2929,7 @@

6.16

6.17 Expanded Document Form

-

This section is non-normative.

+

Esta seção é não-normativa.

The JSON-LD Processing Algorithms and API specification [JSON-LD-API] defines a method for expanding a JSON-LD document. Expansion is @@ -2841,7 +2970,7 @@

6.18 Compacted Document Form

-

This section is non-normative.

+

Esta seção é não-normativa.

The JSON-LD Processing Algorithms and API specification [JSON-LD-API] defines a method for compacting a JSON-LD document. Compaction is @@ -2907,7 +3036,7 @@

6.19 Flattened Document Form

-

This section is non-normative.

+

Esta seção é não-normativa.

The JSON-LD Processing Algorithms and API specification [JSON-LD-API] defines a method for flattening a JSON-LD document. Flattening collects @@ -2962,7 +3091,7 @@

6.20 Embedding JSON-LD in HTML Documents

-

This section is non-normative.

+

Esta seção é não-normativa.

HTML script tags can be used to embed blocks of data in documents. This way, JSON-LD content can be easily embedded in HTML by placing it in a script @@ -3618,7 +3747,7 @@

9.1 Serializing/Deserializing RDF

-

This section is non-normative.

+

Esta seção é não-normativa.

The process of serializing RDF as JSON-LD and deserializing JSON-LD to RDF depends on executing the algorithms defined in @@ -3698,7 +3827,7 @@

A. Relationship to Other Linked Data Formats

-

This section is non-normative.

+

Esta seção é não-normativa.

The JSON-LD examples below demonstrate how JSON-LD can be used to express semantic data marked up in other linked data formats such as Turtle, RDFa, Microformats, @@ -3707,14 +3836,14 @@

A.1 Turtle

-

This section is non-normative.

+

Esta seção é não-normativa.

The following are examples of transforming RDF expressed in Turtle [TURTLE] into JSON-LD.

Prefix definitions

-

This section is non-normative.

+

Esta seção é não-normativa.

The JSON-LD context has direct equivalents for the Turtle @prefix declaration:

@@ -3828,7 +3957,7 @@

Lists

A.2 RDFa

-

This section is non-normative.

+

Esta seção é não-normativa.

The following example describes three people with their respective names and homepages in RDFa [RDFA-CORE].

@@ -3879,7 +4008,7 @@

A.2 RD

A.3 Microformats

-

This section is non-normative.

+

Esta seção é não-normativa.

The following example uses a simple Microformats hCard example to express how Microformats [MICROFORMATS] @@ -3917,7 +4046,7 @@

A.3 <

A.4 Microdata

-

This section is non-normative.

+

Esta seção é não-normativa.

The HTML Microdata [MICRODATA] example below expresses book information as a Microdata Work item.

@@ -4078,7 +4207,7 @@

application/ld+json

C. Acknowledgements

-

This section is non-normative.

+

Esta seção é não-normativa.

The authors would like to extend a deep appreciation and the most sincere thanks to Mark Birbeck, who contributed foundational concepts to JSON-LD via his work @@ -4193,4 +4322,4 @@