Re: JSON-LD API Best Practices note

Very timely for me too :)

On 7 June 2016 at 04:46, Hendy Irawan <ceefour666@gmail.com> wrote:

> Thank you Gregg :)
>
> This is very useful guide especially for me who is trying to implement
> JSON-LD in our project.
>
> Regards,
> Hendy
>
> On Tue, Jun 7, 2016, 01:31 Gregg Kellogg <gregg@greggkellogg.net> wrote:
>
>> I’ve pushed up an in-progress draft of "Building JSON-LD APIs: Best
>> Practices” [1]. This work started because of questions and general
>> uncertainty on the best use of JSON-LD for building APIs, and generating
>> JSON-LD in general. This is not an attempt to break new ground, but to
>> codify experience that’s been developed over the time of JSON-LD adoption.
>>
>> The purpose of this document is to allow an easy entry point for
>> developers wishing to produce or consume APIs using JSON, pointing out the
>> advantages of JSON-LD. It is _not_ intended to generally promote Linked
>> Data or RDF as an end in itself.
>>
>> At this point, there’s little mention of REST, and describing
>> affordances. As there are different practices for this, my intention is to
>> describe schema.org Actions [2] as one means of describing API
>> affordances, in addition to referencing the standardized Linked Data
>> Platform [3] and ongoing work in the Hydra Vocabulary [4].
>>
>> Suggestions for new best practices, pull requests and general issues can
>> be made on the GitHub issue tracker [5] using the “best practices” label,
>> or on public-linked-json@w3.org.
>>
>> Gregg Kellogg
>> gregg@greggkellogg.net
>>
>> [1] http://json-ld.org/spec/latest/json-ld-api-best-practices/
>> [2] https://schema.org/docs/actions.html
>> [3] http://www.w3.org/TR/ldp/
>> [4] http://www.hydra-cg.com
>> [5] https://github.com/json-ld/json-ld.org/issues
>>
>


-- 

*Jeremy Kelaher*
Head of Architecture


*​​*
*Fairfax Media*

*M* 0412345889
*E jeremy.kelaher*@fairfaxmedia.com.au

-- 
The information contained in this e-mail message and any accompanying files 
is or may be confidential. If you are not the intended recipient, any use, 
dissemination, reliance, forwarding, printing or copying of this e-mail or 
any attached files is unauthorised. This e-mail is subject to copyright. No 
part of it should be reproduced, adapted or communicated without the 
written consent of the copyright owner. If you have received this e-mail in 
error please advise the sender immediately by return e-mail or telephone 
and delete all copies. Fairfax Media does not guarantee the accuracy or 
completeness of any information contained in this e-mail or attached files. 
Internet communications are not secure, therefore Fairfax Media does not 
accept legal responsibility for the contents of this message or attached 
files.