-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
4325 lines (3839 loc) · 260 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="pt" dir="ltr" typeof="bibo:Document w3p:REC" about="" property="dcterms:language"
content="pt">
<head>
<title>JSON-LD 1.0</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<style type="text/css">
.highlight {
font-weight: bold;
color: #0a3;
}
.comment {
color: #999;
}
table,
thead,
tr,
td {
padding: 5px;
border-width: 1px;
border-spacing: 0px;
border-style: solid;
border-collapse: collapse;
}
</style>
<style>
/* --- INLINES --- */
em.rfc2119 {
text-transform: lowercase;
font-variant: small-caps;
font-style: normal;
color: #900;
}
h1 acronym,
h2 acronym,
h3 acronym,
h4 acronym,
h5 acronym,
h6 acronym,
a acronym,
h1 abbr,
h2 abbr,
h3 abbr,
h4 abbr,
h5 abbr,
h6 abbr,
a abbr {
border: none;
}
dfn {
font-weight: bold;
}
a.internalDFN {
color: inherit;
border-bottom: 1px solid #99c;
text-decoration: none;
}
a.externalDFN {
color: inherit;
border-bottom: 1px dotted #ccc;
text-decoration: none;
}
a.bibref {
text-decoration: none;
}
cite .bibref {
font-style: normal;
}
code {
color: #ff4500;
}
/* --- TOC --- */
.toc a,
.tof a {
text-decoration: none;
}
a .secno,
a .figno {
color: #000;
}
ul.tof,
ol.tof {
list-style: none outside none;
}
.caption {
margin-top: 0.5em;
font-style: italic;
}
/* --- TABLE --- */
table.simple {
border-spacing: 0;
border-collapse: collapse;
border-bottom: 3px solid #005a9c;
}
.simple th {
background: #005a9c;
color: #fff;
padding: 3px 5px;
text-align: left;
}
.simple th[scope="row"] {
background: inherit;
color: inherit;
border-top: 1px solid #ddd;
}
.simple td {
padding: 3px 10px;
border-top: 1px solid #ddd;
}
.simple tr:nth-child(even) {
background: #f0f6ff;
}
/* --- DL --- */
.section dd>p:first-child {
margin-top: 0;
}
.section dd>p:last-child {
margin-bottom: 0;
}
.section dd {
margin-bottom: 1em;
}
.section dl.attrs dd,
.section dl.eldef dd {
margin-bottom: 0;
}
</style>
<style>
/* --- EXAMPLES --- */
div.example-title {
min-width: 7.5em;
color: #b9ab2d;
}
div.example-title span {
text-transform: uppercase;
}
aside.example,
div.example,
div.illegal-example {
padding: 0.5em;
margin: 1em 0;
position: relative;
clear: both;
}
div.illegal-example {
color: red
}
div.illegal-example p {
color: black
}
aside.example,
div.example {
padding: .5em;
border-left-width: .5em;
border-left-style: solid;
border-color: #e0cb52;
background: #fcfaee;
}
aside.example div.example {
border-left-width: .1em;
border-color: #999;
background: #fff;
}
aside.example div.example div.example-title {
color: #999;
}
</style>
<style>
/* --- ISSUES/NOTES --- */
div.issue-title,
div.note-title {
padding-right: 1em;
min-width: 7.5em;
color: #b9ab2d;
}
div.issue-title {
color: #e05252;
}
div.note-title {
color: #2b2;
}
div.issue-title span,
div.note-title span {
text-transform: uppercase;
}
div.note,
div.issue {
margin-top: 1em;
margin-bottom: 1em;
}
.note>p:first-child,
.issue>p:first-child {
margin-top: 0
}
.issue,
.note {
padding: .5em;
border-left-width: .5em;
border-left-style: solid;
}
div.issue,
div.note {
padding: 1em 1.2em 0.5em;
margin: 1em 0;
position: relative;
clear: both;
}
span.note,
span.issue {
padding: .1em .5em .15em;
}
.issue {
border-color: #e05252;
background: #fbe9e9;
}
.note {
border-color: #52e052;
background: #e9fbe9;
}
</style>
<style>
/* Translation node */
.alert-rc, .alert-wd {
background-color: #fafaae;
border-radius: 10px;
padding: 10px;
margin: 1em auto;
border: 2px black dashed;
}
.alert-wd {
border: 5px red dashed;
}
.alert-rc > .alert-rc-tt, .alert-wd > .alert-wd-tt {
font-size: 2em;
}
</style>
<link rel="stylesheet" href="style.css">
<!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
<!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
</head>
<body class="h-entry" role="document" id="respecDocument">
<div class="head" role="contentinfo" id="respecHeader">
<div class="alert-wd">
<p class="alert-wd-tt">Rascunho de trabalho de tradução</p>
Documento em processo de tradução pela <a href="http://www.webiwg.org/">WebIWG</a>. Original em
<a href="https://www.w3.org/TR/json-ld/">A JSON-based Serialization for Linked Data</a>
</p>
<p>
Veja a <a href="https://github.com/webiwg/w3c-tr-json-ld/issues">discussão desta tradução no Github</a>.
</p>
<p>
Veja <a href="http://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fjson-ld%2F&doc2=http%3A%2F%2Fjson-ld.pt.webiwg.org%2F">diferença entre o original e esta tradução</a>,
possivelmente útil para revisão.
</p>
</div>
<p>
<a href="http://www.w3.org/"><img width="72" height="48" src="w3c_home.png" alt="W3C"></a>
</p>
<h1 class="title p-name" id="title" property="dcterms:title">JSON-LD 1.0</h1>
<h2 property="bibo:subtitle" id="subtitle">Um formato baseado em JSON para serializar Dados Linkados</h2>
<h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-01-15T23:00:00.000Z"
id="w3c-recommendation-16-january-2014">Recomendação da <abbr title="World Wide Web Consortium">W3C</abbr> em <time class="dt-published"
datetime="2014-01-16">16 de janeiro de 2014</time></h2>
<dl>
<dt>Esta versão:</dt>
<dd><a class="u-url" href="http://www.w3.org/TR/2014/REC-json-ld-20140116/">http://www.w3.org/TR/2014/REC-json-ld-20140116/</a></dd>
<dt>Última versão publicada:</dt>
<dd><a href="http://www.w3.org/TR/json-ld/">http://www.w3.org/TR/json-ld/</a></dd>
<dt>Versão anterior:</dt>
<dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2013/PR-json-ld-20131105/">http://www.w3.org/TR/2013/PR-json-ld-20131105/</a></dd>
<dt>Editores:</dt>
<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
</dd>
<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
</dd>
<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.tugraz.at/">Graz University of Technology</a></span>
</dd>
<dt>Autores:</dt>
<dd class="p-author h-card vcard" rel="dcterms:contributor"><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://digitalbazaar.com/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
</dd>
<dd class="p-author h-card vcard" rel="dcterms:contributor"><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">Dave Longley</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
</dd>
<dd class="p-author h-card vcard" rel="dcterms:contributor"><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
</dd>
<dd class="p-author h-card vcard" rel="dcterms:contributor"><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.tugraz.at/">Graz University of Technology</a></span>
</dd>
<dd class="p-author h-card vcard" rel="dcterms:contributor"><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Niklas Lindström" href="http://neverspace.net/">Niklas Lindström</a></span>
</dd>
</dl>
<p>
Por favor consulte a <a href="http://www.w3.org/2014/json-ld-errata"><strong>errata</strong></a> deste documento
que pode incluir algumas correções normativas.
</p>
<p>
Este documento também está disponível neste formato não-normativa:
<a rel="alternate" href="https://www.w3.org/TR/json-ld/diff-20131105.html">diferenças quanto a versão anterior</a>
</p>
<p>
A versão em inglês desta especificação é a versão única normativa.
<a href="http://www.w3.org/Consortium/Translation/">Traduções</a> não-normativas podem
estar disponíveis.
</p>
<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010-2014
<a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (
<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>),
Todos os direitos reservados.
Aplicam-se as regras de
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">responsabilidade</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">marca registrada</a> e
<a href="http://www.w3.org/Consortium/Legal/copyright-documents"> uso do documento</a>
da <abbr title="World Wide Web Consortium">W3C</abbr>.
</p>
<hr>
</div>
<!--
N.T. Vou assumir "Linked Data" como "Dados Linkados". Isso requer mais pesquisa (fititnt, 2016-10-21 08:22)
N.T. É importante que traduções de "Linked Data" usem primeira letra maiúscula (fititnt, 2016-10-21 08:26)
-->
<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter">
<h2 aria-level="1" role="heading" id="h2_abstract">Resumo</h2>
<p>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.
</p>
</section>
<section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter">
<h2 aria-level="1" role="heading" id="h2_sotd">Situação Deste Documento</h2>
<p>
<em>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 <abbr title="World Wide Web Consortium">W3C</abbr> e a última revisão
deste relatório técnico pode ser encontrado no <a href="http://www.w3.org/TR/">índice de relatórios técnicos da <abbr title="World Wide Web Consortium">W3C</abbr> </a> em http://www.w3.org/TR/.</em>
</p>
<p>Este documento foi revisado por membros do <abbr title="World Wide Web Consortium">W3C</abbr>, por desenvolvedores de software, e por outros grupos da <abbr title="World Wide Web Consortium">W3C</abbr> e partes interessadas,
e é endossado pelo Diretor como uma Recomendação da <abbr title="World Wide Web Consortium">W3C</abbr>. É um documento estável e pode ser usado como material de referência ou citado em outro documento.
Papel do <abbr title="World Wide Web Consortium">W3C</abbr>
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.</p>
<!--
N.T.: Não tenho certeza da tradução "the Recommendation track" ser "na trilha de Recomendação".
E não consigo encontrar referências na internet sobre isso neste momento (fititnt, 2016-10-22 02:57)
-->
<p>Esta especificação foi desenvolvida pelo <em lang="en">JSON for Linking Data Community Group</em> antes de ser transferida para o <em lang="en">RDF Working Group</em> 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
<a href="https://www.w3.org/TR/json-ld/diff-20131105.html">versão com diferenças marcadas</a> para mais detalhes.</p>
<p>Existem várias implementações interoperacionais independentes desta especificação.
Um
<a href="https://dvcs.w3.org/hg/json-ld/raw-file/default/test-suite/reports/cr-20131022.html">relatório de implementações</a> em Outubro de 2013 está disponível.</p>
<p>
Este documento foi publicado pelo <a href="http://www.w3.org/2011/rdf-wg/" lang="en">RDF Working Group</a> como uma Recomendação. Se você deseja fazer comentários sobre este documento,
por favor os envie para
<a href="mailto:[email protected]">[email protected]</a> (
<a href="mailto:[email protected]?subject=subscribe">inscrever-se</a>,
<a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">arquivos</a>).
Todos os comentários são bem vindos.</p>
<p>
Este documento foi produzido por um grupo que opera sob a
<a id="sotd_patent" about="" rel="w3p:patentRules" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">Política de Patentes da <abbr title="World Wide Web Consortium">W3C</abbr> de fevereiro de 2004</a>.
<abbr title="World Wide Web Consortium">W3C</abbr> mantém uma <a href="http://www.w3.org/2004/01/pp-impl/46168/status"
rel="disclosure">lista pública de divulgação de patentes</a> feita em conexão
com as entregas do grupo; essa página também inclui instruções para a
divulgação de uma patente.
<!--
N.T.: Estou usando como referência para esse paráfrafo, a mesma tradução que fiz em
http://i18n-html-tech-lang.pt.webiwg.org/, porém parece que a palavra "Patente"
não é citada na outra fonte. O paragrafo de ambos devem ser especialmente
revisados.
-->
Uma pessoa que tenha conhecimento de uma patente que
esta pessoa acredita conter
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">"Reivindicações essenciais"</a> deve divulgar as informações de acordo com a
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">seção
6 da Política de Patentes do <abbr title="World Wide Web Consortium">W3C</abbr></a>.
</p>
</section>
<section id="toc">
<h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Índice de conteúdo</h2>
<ul class="toc" role="directory" id="respecContents">
<li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introdução</a>
<ul class="toc">
<li class="tocline"><a href="#how-to-read-this-document" class="tocxref"><span class="secno">1.1 </span>Como Ler este Documento</a></li>
</ul>
</li>
<li class="tocline"><a href="#design-goals-and-rationale" class="tocxref"><span class="secno">2. </span>Design Goals and Rationale</a></li>
<li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">3. </span>Terminology</a>
<ul class="toc">
<li class="tocline"><a href="#general-terminology" class="tocxref"><span class="secno">3.1 </span>General Terminology</a></li>
<li class="tocline"><a href="#data-model-overview" class="tocxref"><span class="secno">3.2 </span>Data Model Overview</a></li>
<li class="tocline"><a href="#syntax-tokens-and-keywords" class="tocxref"><span class="secno">3.3 </span>Syntax Tokens and Keywords</a></li>
</ul>
</li>
<li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">4. </span>Conformance</a></li>
<li class="tocline"><a href="#basic-concepts" class="tocxref"><span class="secno">5. </span>Basic Concepts</a>
<ul class="toc">
<li class="tocline"><a href="#the-context" class="tocxref"><span class="secno">5.1 </span>The Context</a></li>
<li class="tocline"><a href="#iris" class="tocxref"><span class="secno">5.2 </span>IRIs</a></li>
<li class="tocline"><a href="#node-identifiers" class="tocxref"><span class="secno">5.3 </span>Node Identifiers</a></li>
<li class="tocline"><a href="#specifying-the-type" class="tocxref"><span class="secno">5.4 </span>Specifying the Type</a></li>
</ul>
</li>
<li class="tocline"><a href="#advanced-concepts" class="tocxref"><span class="secno">6. </span>Advanced Concepts</a>
<ul class="toc">
<li class="tocline"><a href="#base-iri" class="tocxref"><span class="secno">6.1 </span>Base <abbr title="Internationalized Resource Identifier">IRI</abbr></a></li>
<li class="tocline"><a href="#default-vocabulary" class="tocxref"><span class="secno">6.2 </span>Default Vocabulary</a></li>
<li class="tocline"><a href="#compact-iris" class="tocxref"><span class="secno">6.3 </span>Compact IRIs</a></li>
<li class="tocline"><a href="#typed-values" class="tocxref"><span class="secno">6.4 </span>Typed Values</a></li>
<li class="tocline"><a href="#type-coercion" class="tocxref"><span class="secno">6.5 </span>Type Coercion</a></li>
<li class="tocline"><a href="#embedding" class="tocxref"><span class="secno">6.6 </span>Embedding</a></li>
<li class="tocline">
<a href="#advanced-context-usage" class="tocxref"><span class="secno">6.7 </span>Advanced Context Usage</a>
</li>
<li class="tocline">
<a href="#interpreting-json-as-json-ld" class="tocxref"><span class="secno">6.8 </span>Interpreting JSON as JSON-LD</a>
</li>
<li class="tocline">
<a href="#string-internationalization" class="tocxref"><span class="secno">6.9 </span>String Internationalization</a>
</li>
<li class="tocline">
<a href="#iri-expansion-within-a-context" class="tocxref"><span class="secno">6.10 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion within a Context</a>
</li>
<li class="tocline"><a href="#sets-and-lists" class="tocxref"><span class="secno">6.11 </span>Sets and Lists</a></li>
<li class="tocline">
<a href="#reverse-properties" class="tocxref"><span class="secno">6.12 </span>Reverse Properties</a>
</li>
<li class="tocline"><a href="#named-graphs" class="tocxref"><span class="secno">6.13 </span>Named Graphs</a></li>
<li class="tocline">
<a href="#identifying-blank-nodes" class="tocxref"><span class="secno">6.14 </span>Identifying Blank Nodes</a>
</li>
<li class="tocline">
<a href="#aliasing-keywords" class="tocxref"><span class="secno">6.15 </span>Aliasing Keywords</a>
</li>
<li class="tocline">
<a href="#data-indexing" class="tocxref"><span class="secno">6.16 </span>Data Indexing</a>
</li>
<li class="tocline">
<a href="#expanded-document-form" class="tocxref"><span class="secno">6.17 </span>Expanded Document Form</a>
</li>
<li class="tocline">
<a href="#compacted-document-form" class="tocxref"><span class="secno">6.18 </span>Compacted Document Form</a>
</li>
<li class="tocline">
<a href="#flattened-document-form" class="tocxref"><span class="secno">6.19 </span>Flattened Document Form</a>
</li>
<li class="tocline"><a href="#embedding-json-ld-in-html-documents" class="tocxref"><span class="secno">6.20 </span>Embedding JSON-LD in HTML Documents</a></li>
</ul>
</li>
<li class="tocline"><a href="#data-model" class="tocxref"><span class="secno">7. </span>Data Model</a></li>
<li class="tocline">
<a href="#json-ld-grammar" class="tocxref"><span class="secno">8. </span>JSON-LD Grammar</a>
<ul class="toc">
<li class="tocline"><a href="#terms" class="tocxref"><span class="secno">8.1 </span>Terms</a></li>
<li class="tocline">
<a href="#node-objects" class="tocxref"><span class="secno">8.2 </span>Node Objects</a>
</li>
<li class="tocline">
<a href="#value-objects" class="tocxref"><span class="secno">8.3 </span>Value Objects</a>
</li>
<li class="tocline">
<a href="#lists-and-sets" class="tocxref"><span class="secno">8.4 </span>Lists and Sets</a>
</li>
<li class="tocline">
<a href="#language-maps" class="tocxref"><span class="secno">8.5 </span>Language Maps</a>
</li>
<li class="tocline">
<a href="#index-maps" class="tocxref"><span class="secno">8.6 </span>Index Maps</a>
</li>
<li class="tocline">
<a href="#context-definitions" class="tocxref"><span class="secno">8.7 </span>Context Definitions</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#relationship-to-rdf" class="tocxref"><span class="secno">9. </span>Relationship to RDF</a>
<ul class="toc">
<li class="tocline"><a href="#serializing-deserializing-rdf" class="tocxref"><span class="secno">9.1 </span>Serializing/Deserializing RDF</a></li>
</ul>
</li>
<li class="tocline">
<a href="#relationship-to-other-linked-data-formats" class="tocxref"><span class="secno">A. </span>Relationship to Other Linked Data Formats</a>
<ul class="toc">
<li class="tocline">
<a href="#turtle" class="tocxref"><span class="secno">A.1 </span>Turtle</a>
</li>
<li class="tocline">
<a href="#rdfa" class="tocxref"><span class="secno">A.2 </span>RDFa</a>
</li>
<li class="tocline">
<a href="#microformats" class="tocxref"><span class="secno">A.3 </span>Microformats</a>
</li>
<li class="tocline">
<a href="#microdata" class="tocxref"><span class="secno">A.4 </span>Microdata</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#iana-considerations" class="tocxref"><span class="secno">B. </span>IANA Considerations</a>
</li>
<li class="tocline">
<a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a>
</li>
<li class="tocline">
<a href="#references" class="tocxref"><span class="secno">D. </span>References</a>
<ul class="toc">
<li class="tocline">
<a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a>
</li>
<li class="tocline">
<a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a>
</li>
</ul>
</li>
</ul>
</section>
<section class="informative" id="introduction">
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_introduction"><span class="secno">1. </span>Introdução</h2>
<p><em>Esta seção é não-normativa.</em></p>
<p>Dados Linkados [<cite><a class="bibref" href="#bib-LINKED-DATA">LINKED-DATA</a></cite>]
é um modo de criar uma rede de dados baseado em padrões interpretáveis por máquinas
em diferentes documentos e sites da Web. Permite que um aplicativo inicie
em um pedaço de Dados Linkados e siga os links para outros pedaços de Dados
Linkados que estão hospedados em diferentes sites pela Web.</p>
<p>JSON-LD é uma sintaxe leve para serializar Dados Linkados em JSON [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>].
Seu design permite JSON existente ser interpretado como Dados Linkados com mínimas
alterações. JSON-LD é destinado 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 mecanismo de armazenamento baseado em JSON. Como JSON-LD é 100% compatível
com JSON, a maior parte dos interpretadores JSON e bibliotecas disponiveis hoje podem
ser reusadas. Além de todos os recursos que JSON fornece, JSON-LD adiciona:</p>
<ul>
<li>um mecanismo identificador universal para <a class="tref internalDFN" title="json-object"
href="#dfn-json-object">objetos JSON</a> através do uso de <a class="tref internalDFN"
title="iri" href="#dfn-iri">IRIs</a>,</li>
<li>uma maneira para diferenciar chaves compartilhadas entre diferentes documentos JSON ao mapea-las a
<a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> via <a class="tref internalDFN" title="context" href="#dfn-context">context</a>,</li>
<li>um mecanismo em que um valor de um <a class="tref internalDFN" title="json-object"
href="#dfn-json-object">objeto JSON</a> pode referir-se a um <a class="tref internalDFN"
title="json-object" href="#dfn-json-object">objeto JSON</a> em um diferente
site na Web,</li>
<li>uma maneira de associar <a class="tref internalDFN" title="string" href="#dfn-string">strings</a> com sua língua,</li>
<li>uma maneira de associar os tipos de dados com valores como datas e horas,</li>
<li>e uma maneira fácil de espressar um ou mais grafos direcionados, tais como rede social,
em um único documento.</li>
</ul>
<p>
JSON-LD é projetado para ser usado diretamente como JSON, sem nenhum conhecimento de RDF [
<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>].
Ele também é projetado para ser usado como RDF, se desejado, para uso com outras tecnologias de Dados Linkados
como SPARQL. Desenvolvedores que exigem qualquer uma destas facilidades
listadas acima ou precisam serializar dados de um Grafo RDF ou um Conjunto de Dados RDF em uma sintaxe baseada em JSON
vão achar JSON-LD interessante. Pessoas que pretendem usar JSON-LD com
ferramentas RDF vão perceber que pode ser listado como outra sintaxe RDF, como Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>].
Detalhes completos de como JSON-LD se relaciona com RDF estão na seção <a href="#relationship-to-rdf"
class="sec-ref"><span class="secno">9.</span> <span class="sec-title">Relacionamento com RDF</span></a>.
</p>
<p>
A sintaxe é projetada para não perturbar sistemas em produção que já usem JSON, mas
fornece um caminho de atualização suave do JSON para o JSON-LD. Como a forma
dos dados varias extremamente, JSON-LD apresenta mecanimso para reformatar documentos em uma
estrutura determinística que simplifica seu processamento.</p>
<section class="informative" id="how-to-read-this-document">
<h3 aria-level="2" role="heading" id="h3_how-to-read-this-document"><span class="secno">1.1 </span>Como Ler este Documento</h3>
<p><em>Esta seção é não-normativa.</em></p>
<p>This document is a detailed specification for a serialization of Linked Data
in JSON. The document is primarily intended for the following audiences:</p>
<ul>
<li>Software developers who want to encode Linked Data in a variety of programming languages that can use JSON</li>
<li>Software developers who want to convert existing JSON to JSON-LD</li>
<li>Software developers who want to understand the design decisions and language syntax for JSON-LD</li>
<li>Software developers who want to implement processors and APIs for JSON-LD</li>
<li>Software developers who want to generate or consume Linked Data, an RDF graph, or an RDF Dataset in a JSON syntax</li>
</ul>
<p>A companion document, the JSON-LD Processing Algorithms and API specification
[
<cite><a class="bibref" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>],
specifies how to work with JSON-LD at a higher level by providing a standard library interface for common JSON-LD operations.
</p>
<p>To understand the basics in this specification you must first be familiar with JSON,
which is detailed in [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>].</p>
<p>This document almost exclusively uses the term <abbr title="Internationalized Resource Identifier">IRI</abbr> (
<a href="http://www.w3.org/TR/ld-glossary/#internationalized-resource-identifier">Internationalized Resource Indicator</a>)
when discussing hyperlinks. Many Web developers are more familiar with the
URL (<a href="http://www.w3.org/TR/ld-glossary/#uniform-resource-locator">Uniform Resource Locator</a>)
terminology. The document also uses, albeit rarely, the URI (
<a href="http://www.w3.org/TR/ld-glossary/#uniform-resource-identifier">Uniform Resource Indicator</a>) terminology.
While these terms are often used interchangeably among technical communities,
they do have important distinctions from one another and the specification goes to great lengths to try and use the proper terminology at all times.
</p>
</section>
</section>
<section class="informative" id="design-goals-and-rationale">
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_design-goals-and-rationale"><span class="secno">2. </span>Design Goals and Rationale</h2>
<p><em>Esta seção é não-normativa.</em></p>
<p>JSON-LD satisfies the following design goals:</p>
<dl>
<dt>Simplicity</dt>
<dd>
No extra processors or software libraries are necessary to use JSON-LD in its most basic form.
The language provides developers with a very easy learning curve.
Developers only need to know JSON and two <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a> (<code>@context</code> and <code>@id</code>) to use the basic functionality in JSON-LD.
</dd>
<dt>Compatibility</dt>
<dd>
A JSON-LD document is always a valid JSON document.
This ensures that all of the standard JSON libraries work seamlessly with JSON-LD documents.
</dd>
<dt>Expressiveness</dt>
<dd>The syntax serializes directed graphs.
This ensures that almost every real world data model can be expressed.
</dd>
<dt>Terseness</dt>
<dd>The JSON-LD syntax is very terse and human readable, requiring as little effort as possible from the developer.</dd>
<dt>Zero Edits, most of the time</dt>
<dd>JSON-LD ensures a smooth and simple transition from existing JSON-based systems.
In many cases, zero edits to the JSON document and the addition of one line
to the HTTP response should suffice (see <a class="sectionRef sec-ref" href="#interpreting-json-as-json-ld">section 6.8 Interpreting JSON as JSON-LD</a>).
This allows organizations that have already deployed large JSON-based infrastructure to use JSON-LD's features in a way that is not disruptive to their day-to-day operations and is transparent to their current customers.
However, there are times where mapping JSON to a graph representation is a complex undertaking.
In these instances, rather than extending JSON-LD to support esoteric use cases, we chose not to support the use case.
While Zero Edits is a design goal, it is not always possible without adding great complexity to the language.
JSON-LD focuses on simplicity when possible.
</dd>
<dt>Usable as RDF</dt>
<dd>
JSON-LD is usable by developers as idiomatic JSON, with no need to understand
RDF [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>].
JSON-LD is also usable as RDF, so people intending to use JSON-LD with RDF tools will find it can be used like any other RDF syntax.
Complete details of how JSON-LD relates to RDF are in section
<a href="#relationship-to-rdf" class="sec-ref"><span class="secno">9.</span> <span class="sec-title">Relationship to RDF</span></a>.</dd>
</dl>
</section>
<section class="normative" id="terminology">
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_terminology"><span class="secno">3. </span>Terminology</h2>
<section class="normative" id="general-terminology">
<h3 aria-level="2" role="heading" id="h3_general-terminology"><span class="secno">3.1 </span>General Terminology</h3>
<p>
This document uses the following terms as defined in JSON [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>].
Refer to the <em>JSON Grammar</em> section in [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>] for formal definitions.
</p>
<dl>
<dt><dfn title="json-object" id="dfn-json-object">JSON object</dfn></dt>
<dd>
An object structure is represented as a pair of curly brackets surrounding zero or more key-value pairs.
A key is a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>.
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.
</dd>
<dt><dfn title="array" id="dfn-array">array</dfn></dt>
<dd>
An array structure is represented as square brackets surrounding zero or more values.
Values are separated by commas.
In JSON, an array is an <em>ordered</em> sequence of zero or more values.
While JSON-LD uses the same array representation as JSON, the collection is <em>unordered</em> by default.
While order is preserved in regular JSON arrays, it is not in regular JSON-LD arrays unless specifically defined
(see <a class="sectionRef sec-ref" href="#sets-and-lists">section 6.11 Sets and Lists</a>).
</dd>
<dt><dfn title="string" id="dfn-string">string</dfn></dt>
<dd>
A string is a sequence of zero or more Unicode characters, wrapped in double quotes, using backslash escapes (if necessary).
</dd>
<dt><dfn title="number" id="dfn-number">number</dfn></dt>
<dd>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.</dd>
<dt><dfn title="true" id="dfn-true">true</dfn> and <dfn title="false" id="dfn-false">false</dfn></dt>
<dd>Values that are used to express one of two possible boolean states.</dd>
<dt><dfn title="null" id="dfn-null">null</dfn></dt>
<dd>
The <a class="tref internalDFN" title="null" href="#dfn-null">null</a> value, which is typically used to clear or forget data.
For example, a key-value pair in the
<code>@context</code> where the value is <a class="tref internalDFN" title="null" href="#dfn-null">null</a> explicitly decouples a
<a class="tref internalDFN" title="term" href="#dfn-term">term</a>'s association with an
<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.
A key-value pair in the body of a JSON-LD document whose value is
<a class="tref internalDFN" title="null" href="#dfn-null">null</a> has
the same meaning as if the key-value pair was not defined. If <code>@value</code>,
<code>@list</code>, or
<code>@set</code> is set to <a class="tref internalDFN" title="null" href="#dfn-null">null</a> in expanded form,
then the entire <a class="tref internalDFN" title="json-object" href="#dfn-json-object">JSON object</a> is ignored.
</dd>
</dl>
</section>
<section class="informative" id="data-model-overview">
<h3 aria-level="2" role="heading" id="h3_data-model-overview"><span class="secno">3.2 </span>Data Model Overview</h3>
<p><em>Esta seção é não-normativa.</em></p>
<p>
Generally speaking, the data model used for JSON-LD is a labeled, directed <a class="tref internalDFN" title="graph" href="#dfn-graph">graph</a>.
The graph contains
<a class="tref internalDFN" title="node" href="#dfn-node">nodes</a>, which are connected by
<a class="tref internalDFN" title="edge" href="#dfn-edge">edges</a>.
A <a class="tref internalDFN" title="node" href="#dfn-node">node</a> is typically data such as a
<a class="tref internalDFN" title="string" href="#dfn-string">string</a>,
<a class="tref internalDFN" title="number" href="#dfn-number">number</a>,
<a class="tref internalDFN" title="typed-value" href="#dfn-typed-value">typed values</a> (like dates and times) or an
<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.
There is also a special class of <a class="tref internalDFN" title="node" href="#dfn-node">node</a> called a
<a class="tref internalDFN" title="blank-node" href="#dfn-blank-node">blank node</a>,
which is typically used to express data that does not have a global identifier
like an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.
<a class="tref internalDFN" title="blank-node" href="#dfn-blank-node">Blank nodes</a> are identified using a
<a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a>.
This simple data model is incredibly flexible and powerful, capable of modeling
almost any kind of data. For a deeper explanation of the data model, see
section <a href="#data-model" class="sec-ref"><span class="secno">7.</span> <span class="sec-title">Data Model</span></a>.
</p>
<p>
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
<a href="#relationship-to-rdf" class="sec-ref"><span class="secno">9.</span> <span class="sec-title">Relationship to RDF</span></a>.
</p>
</section>
<section class="normative" id="syntax-tokens-and-keywords">
<h3 aria-level="2" role="heading" id="h3_syntax-tokens-and-keywords"><span class="secno">3.3 </span>Syntax Tokens and Keywords</h3>
<p>JSON-LD specifies a number of syntax tokens and <dfn title="keyword" id="dfn-keyword">keywords</dfn> that are a core part of the language:</p>
<dl>
<dt><code>@context</code></dt>
<dd>
Used to define the short-hand names that are used throughout a JSON-LD document.
These short-hand names are called <a class="tref internalDFN" title="term" href="#dfn-term">terms</a> and help developers to express specific identifiersin a compact manner.
The <code>@context</code> keyword is described in detail in
<a class="sectionRef sec-ref" href="#the-context">section 5.1 The Context</a>.
</dd>
<dt><code>@id</code></dt>
<dd>
Used to uniquely identify <em>things</em> that are being described in the document with <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> or <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifiers</a>.
This keyword is described in <a class="sectionRef sec-ref" href="#node-identifiers">section 5.3 Node Identifiers</a>.
</dd>
<dt><code>@value</code></dt>
<dd>
Used to specify the data that is associated with a particular <a class="tref internalDFN" title="property" href="#dfn-property">property</a> in the graph.
This keyword is described in <a class="sectionRef sec-ref" href="#string-internationalization">section 6.9 String Internationalization</a> and <a class="sectionRef sec-ref" href="#typed-values">section 6.4 Typed Values</a>.
</dd>
<dt><code>@language</code></dt>
<dd>
Used to specify the language for a particular string value or the default language of a JSON-LD document.
This keyword is described in <a class="sectionRef sec-ref" href="#string-internationalization">section 6.9 String Internationalization</a>.
</dd>
<dt><code>@type</code></dt>
<dd>
Used to set the data type of a <a class="tref internalDFN" title="node" href="#dfn-node">node</a> or
<a class="tref internalDFN" title="typed-value" href="#dfn-typed-value">typed value</a>.
This keyword is described in
<a class="sectionRef sec-ref" href="#typed-values">section 6.4 Typed Values</a>.
</dd>
<dt><code>@container</code></dt>
<dd>
Used to set the default container type for a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>.
This keyword is described in <a class="sectionRef sec-ref" href="#sets-and-lists">section 6.11 Sets and Lists</a>.
</dd>
<dt><code>@list</code></dt>
<dd>
Used to express an ordered set of data.
This keyword is described in <a class="sectionRef sec-ref" href="#sets-and-lists">section 6.11 Sets and Lists</a>.
</dd>
<dt><code>@set</code></dt>
<dd>
Used to express an unordered set of data and to ensure that values are always represented as arrays.
This keyword is described in <a class="sectionRef sec-ref" href="#sets-and-lists">section 6.11 Sets and Lists</a>.
</dd>
<dt><code>@reverse</code></dt>
<dd>
Used to express reverse properties.
This keyword is described in <a class="sectionRef sec-ref" href="#reverse-properties">section 6.12 Reverse Properties</a>.
</dd>
<dt><code>@index</code></dt>
<dd>
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 <a class="sectionRef sec-ref" href="#data-indexing">section 6.16 Data Indexing</a>.
</dd>
<dt><code>@base</code></dt>
<dd>
Used to set the base <abbr title="Internationalized Resource Identifier">IRI</abbr> against which <a class="tref internalDFN" title="relative-iri" href="#dfn-relative-iri">relative IRIs</a> are resolved.
This keyword is described in <a class="sectionRef sec-ref" href="#base-iri">section 6.1 Base IRI</a>.
</dd>
<dt><code>@vocab</code></dt>
<dd>
Used to expand properties and values in <code>@type</code> with a common prefix <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.
This keyword is described in <a class="sectionRef sec-ref" href="#default-vocabulary">section 6.2 Default Vocabulary</a>.
</dd>
<dt><code>@graph</code></dt>
<dd>
Used to express a <a class="tref internalDFN" title="graph" href="#dfn-graph">graph</a>.
This keyword is described in <a class="sectionRef sec-ref" href="#named-graphs">section 6.13 Named Graphs</a>.
</dd>
<dt><code>:</code></dt>
<dd>The separator for JSON keys and values that use <a class="tref internalDFN" title="compact-iri" href="#dfn-compact-iri">compact IRIs</a>.</dd>
</dl>
<p>All keys, <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a>, and values in JSON-LD are case-sensitive.</p>
</section>
</section>
<section class="normative" id="conformance">
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">4. </span>Conformance</h2>
<p>
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.
</p>
<p>A <a class="tref internalDFN" title="json-ld-document" href="#dfn-json-ld-document">JSON-LD document</a> complies with this specification if it follows the normative statements in
appendix <a href="#json-ld-grammar" class="sec-ref"><span class="secno">8.</span> <span class="sec-title">JSON-LD Grammar</span></a>.
JSON documents can be interpreted as JSON-LD by following the normative statements
in
<a class="sectionRef sec-ref" href="#interpreting-json-as-json-ld">section 6.8 Interpreting JSON as JSON-LD</a>.
For convenience, normative statements for documents are often phrased as statements
on the properties of the document.</p>
<p>The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119"
title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>,
<em class="rfc2119" title="SHALL">SHALL</em>, <em class="rfc2119" title="SHALL NOT">SHALL NOT</em>,
<em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>,
<em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119"
title="NOT RECOMMENDED">NOT RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>,
and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification
have the meaning defined in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].</p>
</section>
<section class="informative" id="basic-concepts">
<!--OddPage-->
<h2 aria-level="1" role="heading" id="h2_basic-concepts"><span class="secno">5. </span>Basic Concepts</h2>
<p><em>Esta seção é não-normativa.</em></p>
<p>JSON [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>] is a lightweight,
language-independent data interchange format.
It is easy to parse and easy to generate.
However, it is difficult to integrate JSON from different sources as the data may contain keys that conflict with other data sources.
Furthermore, JSON has no built-in support for hyperlinks, which are a fundamental building block on the Web.
Let's start by looking at an example that we will be using for the rest of this section:</p>
<div class="example">
<div class="example-title"><span>Example 1</span>: Sample JSON document</div><pre class="example">{
"name": "Manu Sporny",
"homepage": "http://manu.sporny.org/",
"image": "http://manu.sporny.org/images/manu.png"
}</pre></div>
<p>It's obvious to humans that the data is about a person whose
<code>name</code> is "Manu Sporny" and that the <code>homepage</code> property
contains the URL of that person's homepage. A machine doesn't have such an
intuitive understanding and sometimes, even for humans, it is difficult to
resolve ambiguities in such representations. This problem can be solved by
using unambiguous identifiers to denote the different concepts instead of tokens
such as "name", "homepage", etc.</p>
<p>Linked Data, and the Web in general, uses <a class="tref internalDFN" title="iri"
href="#dfn-iri">IRIs</a> (Internationalized Resource Identifiers as described
in [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>]) for unambiguous
identification. The idea is to use
<a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> to assign
unambiguous identifiers to data that may be of use to other developers. It
is useful for <a class="tref internalDFN" title="term" href="#dfn-term">terms</a>,
like <code>name</code> and <code>homepage</code>, to expand to <a class="tref internalDFN"
title="iri" href="#dfn-iri">IRIs</a> so that developers don't accidentally
step on each other's terms. Furthermore, developers and machines are able to
use this
<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> (by using a web browser, for instance) to go to the term and get a definition
of what the term means. This process is known as <a class="tref internalDFN"
title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> dereferencing.
</p>
<p>Leveraging the popular <a href="http://schema.org/">schema.org vocabulary</a>,
the example above could be unambiguously expressed as follows:</p>
<div class="example">
<div class="example-title"><span>Example 2</span>: Sample JSON-LD document using full IRIs instead of
terms
</div><pre class="example">{
"<span class="highlight">http://schema.org/name</span>": "Manu Sporny",
"<span class="highlight">http://schema.org/url</span>": <span class="highlight">{ "@id": </span>"http://manu.sporny.org/" <span class="highlight">}</span>, <span class="comment">← The '@id' keyword means 'This value is an identifier that is an IRI'</span>
"<span class="highlight">http://schema.org/image</span>": <span class="highlight">{ "@id": </span>"http://manu.sporny.org/images/manu.png" <span class="highlight">}</span>
}</pre></div>
<p>In the example above, every property is unambiguously identified by an
<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> and all values representing <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> are explicitly marked as such by the
<code>@id</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>.
While this is a valid JSON-LD document that is very specific about its data,
the document is also overly verbose and difficult to work with for human developers.
To address this issue, JSON-LD introduces the notion of a
<a class="tref internalDFN" title="context" href="#dfn-context">context</a> as described in the next section.</p>
<section class="informative" id="the-context">
<h3 aria-level="2" role="heading" id="h3_the-context"><span class="secno">5.1 </span>The Context</h3>
<p><em>Esta seção é não-normativa.</em></p>
<p>When two people communicate with one another, the conversation takes place