- From: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Date: Mon, 11 Jan 2016 11:08:41 +0100
- To: public-hydra@w3.org
- Message-ID: <56937F29.2020500@n-fuse.de>
I think I have named these gains from using RDF as a data model listed on this slide: http://vanthome.github.io/rest-api-essay-presentation/rest_apis.html#43 On 01/11/2016 01:05 AM, Kingsley Idehen wrote: > On 1/6/16 4:09 AM, Thomas Hoppe wrote: >> Hi Paul, >> >> I compared Hydra to other approaches in general a bit here: >> >> http://vanthome.github.io/rest-api-essay-presentation/rest_apis.html#28 >> >> BG, Thomas > > Thomas, > > You characterization of the "Semantic Web" is inaccurate. > > The killer application of the Semantic Web is basically what you see > manifesting via Schema.org adoption i.e., content that is > comprehensible to both humans and machines. > > [1] > http://kidehen.blogspot.com/2015/09/what-happened-to-semantic-web.html > -- What Happend to the Semantic Web ? > > > Kingsley >> >> On 01/04/2016 01:14 PM, Paul Mackay wrote: >>> Hi, >>> >>> I’m iterating on a couple of API projects and have been reviewing >>> the status of current API specification projects. JSON API >>> (http://www.cerebris.com/blog/2015/06/04/jsonapi-1-0/) reached v1.0 >>> earlier this year and is more comprehensive than HAL (see >>> http://jsonapi.org/faq/). I suspect Hydra could be even more >>> flexible and comprehensive in terms of defining an API. However >>> within the JSON API community that spec is being promoted as an >>> anti-bikeshedding tool (avoid lots of debate about small issues) and >>> yet getting to 1.0 involved a lot of bikeshedding! >>> >>> Has there been any comparisons between JSON API and Hydra, and what >>> is behind the design choices of Hydra? I suppose a similar FAQ for >>> Hydra along the lines of why it goes beyond other API framework >>> specifications would be great :) >>> >>> Thanks >>> >>> Paul >>> >>> >>> -- >>> Paul Mackay | 07761 050542 | www.folklabs.com <http://www.folklabs.com/> >> > > > -- > Regards, > > Kingsley Idehen > Founder & CEO > OpenLink Software > Company Web:http://www.openlinksw.com > Personal Weblog 1:http://kidehen.blogspot.com > Personal Weblog 2:http://www.openlinksw.com/blog/~kidehen > Twitter Profile:https://twitter.com/kidehen > Google+ Profile:https://plus.google.com/+KingsleyIdehen/about > LinkedIn Profile:http://www.linkedin.com/in/kidehen > Personal WebID:http://kingsley.idehen.net/dataspace/person/kidehen#this
Received on Monday, 11 January 2016 10:09:33 UTC