- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Mon, 3 Feb 2014 22:15:30 +0100
- To: <public-hydra@w3.org>
- Message-ID: <031201cf2125$126f8a00$374e9e00$@lanthaler@gmx.net>
On Monday, February 03, 2014 10:05 PM, Kingsley Idehen wrote: > On 2/3/14 3:19 PM, Markus Lanthaler wrote: > > I think the biggest problem is how this stuff is documented and the fact > > that people won't read it:-) It's not a contract. It's a hint. Clients have > > to interpret the response in any case. Some will be more tolerant, some will > > break when they don't get back what they expected. That's similar to how > > people often run into troubles when parts of a website get redesigned and > > "nothing works anymore" because it looks different or they have to take > > different paths. > > This is where TURTLE is your friend. The narrative is more readable in > TURTLE that it will ever be in JSON-LD. Sorry, but I don't see how this is relevant in this context. > JSON-LD is for the coders that don't want to make a TURTLE parser etc.. > But, to write good code you really have to understand what exactly you > are doing. Right. That applies to just about every technology. > I encourage you to discuss in TURTLE so that more folks get involved in > these discussions. Yep.. Ruben will convert the examples to Turtle and we will probably include both versions in the spec eventually. > I make this comment because there was a nice series > of points from 'John Yaya' that kinda got lost in the JSON-LD examples > he made. More folks would zone in if those examples are the more > readable TURTLE :-) Do you have a pointer? That probably happened on another list. At least he didn't post to public-hydra. Cheers, Markus -- Markus Lanthaler @markuslanthaler
Received on Monday, 3 February 2014 21:16:04 UTC