RE: In the spec, swap RFC4627 for RFC7159

Hi Thomas,

I've thought about this before myself but am still on the fence on what to
do. Unfortunately, RFC7159 isn't simply a reclassification of RFC4627 to
bring it on the standards track but also contains a number of BC-breaking
changes. For example, it loosens the restriction on top-level constructs (in
RFC4627 only objects and arrays are allowed, in RFC7159 everything is). I'd
thus prefer to not make this change at this point.

Is there any reason to update the ref apart from "let's use the latest

Markus Lanthaler

> -----Original Message-----
> From: Thomas Steiner []
> Sent: Thursday, March 06, 2014 1:37 PM
> To: Linked JSON
> Subject: In the spec, swap RFC4627 for RFC7159
> Hi all,
> Finally with the Internet Engineering Task Force (IETF) ending their
> work on RFC7159 (, I suggest
> the JSON-LD spec refers to RFC7159 rather than the older RFC4627.
> Thoughts? FWIW, I've sent pull request
> proactively.
> Best,
> Tom
> --
> Thomas Steiner, Employee, Google Inc.
> Version: GnuPG v1.4.12 (GNU/Linux)
> iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b
> 0ttom.hTtP5://xKcd.c0m/1181/

Received on Thursday, 6 March 2014 16:00:37 UTC