Re: ISSUE-66: LinkedDataT

Hi Markus

On 5 Aug 2014, at 23:39, "Markus Lanthaler" <markus.lanthaler@gmx.net> wrote:

> On 5 Aug 2014 at 16:24, John Walker wrote:
>> Maybe, for those that don't have time to watch the recording of the
>> APICraft session, you can give a brief summary of the different
>> approaches?
> 
> Unfortunately I don't have the time for doing that at the moment. I do know,
> however, that Ícaro (that's why I CCed you) is working on a survey. So he
> might be able to share his results soon.
> 
> For the people that missed it, here's the recording of the API Craft
> hypermedia panel: http://bit.ly/1tTqy6s (it begins at minute 45)
> 
> The other thing that might be interesting and that I haven't shared before
> is a talk I gave at OSCON because it doesn't use an automatically created
> vocabulary as the issue tracker demo does (apart from the EntryPoint) but
> Schema.org.
> 
>  Slides: http://bit.ly/oscon-2014
>  API loaded in HydraConsole: http://bit.ly/1r8IWDR
>  Code (PHP): http://bit.ly/hydra-oscon
> 
> 
>> Also would be interesting to hear your opinion on to what
>> extent they re-invent or are compatible with the basic RDF data model.
> 
> Most approaches treat the data as an opaque blob, i.e., they are not really
> interested in it. Instead, they focus on adding mechanisms to express links
> and in some cases also operations to JSON.

So you get a web of JSON documents rather than HTML documents. Can't help but think that could be more easily achieved had URL been a native data type in JSON from the get go. Can understand it'd be tricky to add it at this stage, hence all the bolt-on mechanisms.

The stuff about operations is really interesting, but seems to me (maybe I'm biased) that being able to advertise the possible states and transitions as Linked Data as Hydra enables is extremely useful (although maybe a steep learning curve for those unfamiliar with the concepts)

John

> 
> 
> --
> Markus Lanthaler
> @markuslanthaler
> 
> 
> 
>

Received on Wednesday, 6 August 2014 05:04:30 UTC