Fwd: Core Vocabulary diagram might be confusing

---------- Forwarded message ----------
From: László Lajos Jánszky <laszlo.janszky@gmail.com>
Date: 2014-09-04 11:47 GMT+02:00
Subject: Re: Core Vocabulary diagram might be confusing
To: Ruben Verborgh <ruben.verborgh@ugent.be>


I think the diagram is not ordered enough, and the two arrow types are way
to similar...

I don't think we need more diagrams. In my opinion it is much easier to
start with a new tool (framework, technology, vocab, etc..) by reading
tutorials about it. For example what would be the requests and responses of
a simple todo list API which uses Hydra and JSON-LD, etc... I think 2-3
tutorials with increasing difficulty levels would be enough. What we
currently have is documentation only, which is great, but has no use for
beginners. They have to learn RDF, JSON-LD and the Hydra vocab, which can
take a long time, and by reading the documentation they cannot decide
whether it will worth the effort or not...


2014-08-25 14:43 GMT+02:00 Ruben Verborgh <ruben.verborgh@ugent.be>:

Dear all,
>
> Some feedback on the hypermedia-web list about
> the diagram featured in the Core Vocabulary spec.
>
> > From: Niels Krijger <nfkrijger@gmail.com>
> > Subject: Re: Yahapi, Yet Another Hypermedia(ish) API specification
> > Date: 20 Aug 2014 04:11:06 GMT+2
> > To: Ruben Verborgh <ruben.verborgh@ugent.be>
> > Cc: hypermedia-web@googlegroups.com
> > Reply-To: niels@kryger.nl
> >
> > I had a brief look at Hydra while writing my blogpost (the blogpost of
> Kevin "
> http://sookocheff.com/posts/2014-03-11-on-choosing-a-hypermedia-format/"
> on which I based my own blog pointed me towards Hydra).
> > I removed Hydra altogether because I found it too difficult to adopt or
> translate to a practical example. I was scared away because of this picture
> in particular: http://www.hydra-cg.com/spec/latest/core/#hydra-at-a-glance
> > I didn't understand it :-(
>
> This person seems to have skimmed the document
> looking for a clarifying image, unsuccessfully.
> Maybe there should be a more high-level diagram too.
>
> Best,
>
> Ruben
>