From c1afb78146f5e1f3c3df516efed39958aaa48a09 Mon Sep 17 00:00:00 2001 From: Emerson Rocha Luiz Date: Fri, 21 Oct 2016 09:24:24 -0200 Subject: [PATCH] =?UTF-8?q?Traduzido=20subtitulo=20e=20links=20de=20topo;?= =?UTF-8?q?=20Identa=C3=A7=C3=A3o=20de=20exemplos=203,=209,=2015,=2018,=20?= =?UTF-8?q?21,=2025,=2031,=2033,=2034,=2035,=2040=20(#1)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- index.html | 245 ++++++++++++++++++++++++++++++++++------------------- 1 file changed, 156 insertions(+), 89 deletions(-) diff --git a/index.html b/index.html index abb2c5c..41e10b8 100644 --- a/index.html +++ b/index.html @@ -304,19 +304,19 @@

JSON-LD 1.0

Um formato baseado em JSON para serializar Dados Linkados

W3C Recommendation

+ id="w3c-recommendation-16-january-2014">Recomendação da W3C em
-
This version:
+
Esta versão:
http://www.w3.org/TR/2014/REC-json-ld-20140116/
-
Latest published version:
+
Última versão publicada:
http://www.w3.org/TR/json-ld/
-
Previous version:
+
Versão anterior:
http://www.w3.org/TR/2013/PR-json-ld-20131105/
-
Editors:
+
Editores:
Manu Sporny, Digital Bazaar
Gregg Kellogg, Kellogg Associates @@ -324,7 +324,7 @@

Um formato baseado em JSON para seria
Markus Lanthaler, Graz University of Technology
-
Authors:
+
Autores:
Manu Sporny, Digital Bazaar
Dave Longley, Digital Bazaar @@ -339,19 +339,19 @@

Um formato baseado em JSON para seria

- Please refer to the errata for this document, - which may include some normative corrections. + Por favor consulte a errata deste documento + que pode incluir algumas correções normativas.

- This document is also available in this non-normative format: - diff to previous version + Este documento também está disponível neste formato não-normativa: + diferenças quanto a versão anterior

- The English version of this specification is the only normative version. Non-normative - translations may also - be available. + A versão em inglês desta especificação é a versão única normativa. + Traduções não-normativas podem + estar disponíveis.

@@ -360,10 +360,12 @@

Um formato baseado em JSON para seria MIT, ERCIM, Keio, Beihang), - All Rights Reserved. - W3C liability, - trademark and - document use rules apply. + Todos os direitos reservados. + Aplicam-se as regras de + responsabilidade, + marca registrada e + uso do documento + da W3C.

@@ -992,19 +994,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.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 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 @@ -1350,9 +1356,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 @@ -1397,11 +1407,17 @@

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"
+}
@@ -1504,16 +1520,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 @@ -1757,16 +1776,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. @@ -1910,14 +1941,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" +}
@@ -2018,13 +2051,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 @@ -2057,15 +2091,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 @@ -2091,13 +2132,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 @@ -2113,11 +2162,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 @@ -2245,12 +2300,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