Re: Hydra adapter for Ruby Oat serializer library

Hi Paul,

Sounds good. I don't use Ruby so haven't checked it out, but having the
ability to ask for a representation in a variety of formats sounds good.

Might also be worth looking at the 'Profile' Link relation (
https://tools.ietf.org/html/rfc6906). The Content-Type header indicates how
the data has been serialised (e.g. JSON), but the Profile can give you
extra information about the data (like what a valid data structure looks
like). A piece of JSON could represent loads of things in many different
formats, so it's good to have some way of nailing down what it represents.

I have to admit I haven't read the IETF spec, but that's a good chapter
about it in the Restful Web APIs book (O'Reilly). I guess the Profile isn't
needed so much in JSON-LD as it can support semantic information within
itself (using known vocabularies), but might be useful for the other JSON
representations.

Cheers,

Kev

On 19 January 2016 at 18:36, Markus Lanthaler <markus.lanthaler@gmx.net>
wrote:

> On Tuesday, January 19, 2016 5:51 PM, Paul Mackay wrote:
> > Thanks Markus,
> >
> > In general, what do you think about APIs offering different ways to
> > serialise content which could be determined by Accept headers, as
> > opposed to an API just providing one approach to serialization? Is
> > that kind of thing important for growing Hydra acceptance in your
> > view?
>
> Definitely. I think the more tooling we can provide, the better. Most
> people actually don't want to think about things like API standards,
> serialization formats etc. They want to concentrate on their application
> domain and increase the value their APIs provide. While we are at a mostly
> OK'ish tool support server side, lots still needs to be done client side.
> We need to move to a state where developers can use a single, high-quality
> client-side library to access all the APIs they need to interact with.
>
>
> Btw. could you please officially join the Hydra W3C Community Group? See
>
>   http://www.hydra-cg.com/#community
>
>
> Thanks,
> Markus
>
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>


-- 
www.dataunity.org
twitter: @data_unity