Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Merge pull request #42 from lanthaler/json-ld-is-w3c-standard

JSON-LD is a W3C standard: Update the text and the link to the spec
  • Loading branch information...
commit 70d23c84b79b1343d6eff67d2be550469d130aba 2 parents bcc33aa + 2d21f7e
@jaytaph jaytaph authored
Showing with 6 additions and 6 deletions.
  1. +6 −6 _posts/2012-12-17-json.html
View
12 _posts/2012-12-17-json.html
@@ -39,20 +39,20 @@
{% endhighlight %}
-<p>Although JSON isn't hypermedia, some standardisation is on its way to make JSON hypermedia. Two of these, JSON-LD and HAL,
- formalizes these links so any client can instantly follow and discover these links, without any additional knowledge on how this
- has been setup.
+<p>Although JSON does't have inherent hypermedia support, some standardisation is on its way to change that. JSON-LD, which is already an official W3C standard,
+ and HAL, which is a personal project, formalize the expression of links in JSON so that clients can instantly follow and discover these links without having
+ to rely on out-of-band additional knowledge.</p>
<h3>See also</h3>
<ul>
<li><a href="http://stateless.co/hal_specification.html">HAL specification</a>
- <li><a href="http://json-ld.org/">JSON-LD specification</a>
+ <li><a href="http://www.w3.org/TR/json-ld/">JSON-LD specification</a>
</ul>
<h3>Caveats</h3>
<ul>
- <li>Because there is no standardized way, JSON for APIs can and most probably will result in tight coupling between
- clients and servers. Servers need to know exactly how you provide links in JSON (if at all). Using HAL or JSON-LD can
+ <li>Because JSON by itself has no hypermedia support, using JSON for APIs can and most probably will result in tight coupling between
+ clients and servers. Servers need to know exactly how you provide links in JSON (if at all). JSON-LD, a W3C Recommendation, or HAL can
reduce this coupling and allow you to formally present (hypermedia) links in your API.
</li>
</ul>
Please sign in to comment.
Something went wrong with that request. Please try again.