Skip to content

Commit 11dad44

Browse files
gkellogggkellogg
committed
Merge remote-tracking branch 'origin/master' into final-cg-reports
2 parents ddd04c0 + efc7879 commit 11dad44

File tree

5 files changed

+24
-21
lines changed

5 files changed

+24
-21
lines changed

‎Gemfile.lock‎

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ GEM
2020
hamster (3.0.0)
2121
concurrent-ruby (~> 1.0)
2222
htmlentities (4.3.4)
23-
i18n (0.9.3)
23+
i18n (1.0.1)
2424
concurrent-ruby (~> 1.0)
2525
json-ld (2.2.1)
2626
multi_json (~> 1.12)
@@ -36,25 +36,26 @@ GEM
3636
sparql (>= 2.2, < 4.0)
3737
sxp (~> 1.0)
3838
link_header (0.0.8)
39-
linkeddata (3.0.0)
39+
linkeddata (3.0.1)
4040
equivalent-xml (~> 0.6)
4141
json-ld (>= 2.2.1, < 4.0)
4242
ld-patch (~> 0.3, >= 0.3.3)
4343
nokogiri (~> 1.8)
44+
nokogumbo (~> 1.5)
4445
rdf (~> 3.0)
4546
rdf-aggregate-repo (>= 2.2.1, < 4.0)
4647
rdf-isomorphic (~> 3.0)
4748
rdf-json (>= 2.2, < 4.0)
4849
rdf-microdata (>= 2.2.3, < 4.0)
49-
rdf-n3 (>= 2.2, < 4.0)
50+
rdf-n3 (~> 3.0)
5051
rdf-normalize (~> 0.3, >= 0.3.3)
51-
rdf-rdfa (>= 2.2.4, < 4.0)
52+
rdf-rdfa (~> 3.0)
5253
rdf-rdfxml (>= 2.2.1, < 4.0)
5354
rdf-reasoner (~> 0.5.0)
5455
rdf-tabular (>= 2.2.1, < 4.0)
5556
rdf-trig (>= 2.2, < 4.0)
5657
rdf-trix (>= 2.2.1, < 4.0)
57-
rdf-turtle (~> 3.0)
58+
rdf-turtle (~> 3.0, >= 3.0.1)
5859
rdf-vocab (~> 3.0)
5960
rdf-xsd (~> 3.0)
6061
shex (~> 0.5, >= 0.5.2)
@@ -64,11 +65,13 @@ GEM
6465
multi_json (1.13.1)
6566
net-http-persistent (3.0.0)
6667
connection_pool (~> 2.2)
67-
nokogiri (1.8.1)
68+
nokogiri (1.8.2)
6869
mini_portile2 (~> 2.3.0)
69-
public_suffix (3.0.1)
70-
rake (12.3.0)
71-
rdf (3.0.1)
70+
nokogumbo (1.5.0)
71+
nokogiri
72+
public_suffix (3.0.2)
73+
rake (12.3.1)
74+
rdf (3.0.2)
7275
hamster (~> 3.0)
7376
link_header (~> 0.0, >= 0.0.8)
7477
rdf-aggregate-repo (2.2.1)
@@ -86,12 +89,12 @@ GEM
8689
rdf (~> 3.0)
8790
rdf-normalize (0.3.3)
8891
rdf (>= 2.2, < 4.0)
89-
rdf-rdfa (2.2.4)
92+
rdf-rdfa (3.0.1)
9093
haml (~> 5.0)
9194
htmlentities (~> 4.3)
92-
rdf (>= 2.2, < 4.0)
95+
rdf (~> 3.0)
9396
rdf-aggregate-repo (>= 2.2, < 4.0)
94-
rdf-xsd (>= 2.2, < 4.0)
97+
rdf-xsd (~> 3.0)
9598
rdf-rdfxml (2.2.1)
9699
htmlentities (~> 4.3)
97100
rdf (>= 2.2, < 4.0)
@@ -129,7 +132,7 @@ GEM
129132
rdf-xsd (>= 2.2, < 4.0)
130133
sparql (>= 2.2, < 4.0)
131134
sxp (~> 1.0)
132-
sparql (3.0.0)
135+
sparql (3.0.1)
133136
builder (~> 3.2)
134137
ebnf (~> 1.1)
135138
rdf (~> 3.0)

‎spec/latest/json-ld-api-best-practices/index.html‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@
3232
<body>
3333
<section id='abstract'>
3434
<p>
35-
Developers share a common problem: they want a simple, but extensible way to create an API for a web service that gets the job done, doesn't design them into a corner, and allows developers to easily interact with their service without reinventing the wheel. JSON-LD [[JSON-LD]] has become an important solution, as it bridges the gap between formally data and more coloquial JSON interfaces used in APIs from numerous providers. This guide attempts to define certain best practices for publishing data using JSON-LD, and interacting with such services.
35+
Developers share a common problem: they want a simple, but extensible way to create an API for a web service that gets the job done, doesn't design them into a corner, and allows developers to easily interact with their service without reinventing the wheel. JSON-LD [[JSON-LD]] has become an important solution, as it bridges the gap between formally data and more colloquial JSON interfaces used in APIs from numerous providers. This guide attempts to define certain best practices for publishing data using JSON-LD, and interacting with such services.
3636
</p>
3737
</section>
3838

@@ -126,7 +126,7 @@ <h2>Resource Representation</h2>
126126
}
127127
]
128128
</pre>
129-
<p>Expanded form is not useful as is, but is necessary for performing further algorithmic transformaions of JSON-LD data and is useful when validating that JSON-LD entity descriptions say what the publisher means.</p>
129+
<p>Expanded form is not useful as is, but is necessary for performing further algorithmic transformations of JSON-LD data and is useful when validating that JSON-LD entity descriptions say what the publisher means.</p>
130130
</div>
131131
</div>
132132

@@ -137,7 +137,7 @@ <h2>Resource Representation</h2>
137137

138138
<div class="practice">
139139
<p><span id="top-level-object" class="practicelab">Use a top-level object</span></p>
140-
<p class="practicedesc">JSON documents may be in the form of a object, or an array of objects. For most purposes, develpers need a single entrypoint, so the JSON SHOULD be in the form of a single top-level object</p>
140+
<p class="practicedesc">JSON documents may be in the form of a object, or an array of objects. For most purposes, developers need a single entry point, so the JSON SHOULD be in the form of a single top-level object</p>
141141
</div>
142142

143143
<div class="practice">
@@ -153,7 +153,7 @@ <h2>Resource Representation</h2>
153153
<div class="practice">
154154
<p><span id="typed-objects" class="practicelab">Provide one or more types for JSON objects</span></p>
155155
<p class="practicedesc">Principles of <a>Linked Data</a> dictate that messages SHOULD be self describing, which includes adding a <code>type</code> to such messages.</p>
156-
<p>Many APIs use JSON messages where the type of information being conveyed is inferred from the retreaval endpoint. For example, when retrieving information about a Github Commit, you might see the following response:</p>
156+
<p>Many APIs use JSON messages where the type of information being conveyed is inferred from the retrieval endpoint. For example, when retrieving information about a Github Commit, you might see the following response:</p>
157157
<pre class="example" title="Github Commit message">
158158
{
159159
"sha": "7638417db6d59f3c431d3e1f261cc637155684cd",
@@ -292,7 +292,7 @@ <h2>Resource Representation</h2>
292292
<pre class="example" title="Example enumerated value">
293293
{
294294
"@context": ["http://schema.org", <strong>{
295-
<strong>"gender": {"@id": "schema:gender", "@type": "@vocab"}</strong>
295+
"gender": {"@id": "schema:gender", "@type": "@vocab"}
296296
}</strong>],
297297
"id": "https://www.wikidata.org/wiki/Q76",
298298
"type": "Person",

‎spec/latest/json-ld-api/index.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@
9898
note: "v1.0" }
9999
],
100100

101-
github: "https://github.com/json-ld/json-ld.org",
101+
github: "https://github.com/json-ld/json-ld.org/",
102102

103103
// name of the WG
104104
wg: "JSON for Linking Data W3C Community Group",

‎spec/latest/json-ld-framing/index.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@
9393
note: "v1.0" }
9494
],
9595

96-
github: "https://github.com/json-ld/json-ld.org",
96+
github: "https://github.com/json-ld/json-ld.org/",
9797

9898
// name of the WG
9999
wg: "Linking Data in JSON Community Group",

‎spec/latest/json-ld/index.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@
9696
note: "v1.0" }
9797
],
9898

99-
github: "https://github.com/json-ld/json-ld.org",
99+
github: "https://github.com/json-ld/json-ld.org/",
100100

101101
// name of the WG
102102
wg: "JSON for Linking Data W3C Community Group",

0 commit comments

Comments
 (0)