Re: Core Vocabulary diagram might be confusing

>> I just got another mail about the perceived complexity;
> 
> Could you please forward that mail to the list (of course only if the sender
> is OK with it)?

[translated:]

“…to turn it into a success, I think you need to make it very accessible
for RDF-agnostic people (i.e., a bit like JSON-LD did;
it's JSON on the outside, RDF on the inside).
This day, I cannot sell Hydra to [my company],
they perceive it as being too complex.
For the time being, we use HAL with lots of 'assumptions' […].
Not ideal I think, but well…”

Especially note “perceive” above.

>> it would be great if we could start simple, and continue from there.
>> Maybe even a primer would help.
> 
> Let's try to write the spec in a way which makes a primer unnecessary.

The way to do this would be to have the most crucial information on the top.
However, this still doesn't change the fact that complex information will be below;
so if people look at the spec as a whole, it can still be perceived as complex.
Perception is really important there.

HAL et al. are perceived as simple;
using Hydra to express the same is certainly not harder,
but I can understand why people perceive it as such:
there's just much more that is possible with Hydra.

Best,

Ruben

Received on Wednesday, 3 September 2014 21:46:33 UTC