RE: Hydra Status

Hi list,

For me, in very simple terms, RDF provides a fundamental syntactical
abstraction that cannot be accurately expressed in any other way.  I think
that abstraction needs to remain at the core of a system design that aims
to be extensible.  I often feel that emphasizing abstraction over concrete
implementation is conveniently dismissed in many systems.  I still believe
that RDF is vitally important to achieve the generic goal of
interoperability.

And, RDF is not always simpatico with the serialization expectations of a
JSON-LD application.  An example is rdf:List vs. @list for ordered (query
generated) collection construction.  if an @list collection does not first
exist as an rdf:List, is it possible to construct one dynamically?  Meaning
if I do a random query on an RDF graph, is it possible to serialize a
"natively unordered" result set as an "ordered collection" JSON-LD @list?.
I have not been able to do it yet (which is not to say that it is not
possible).  But specifiers and API designers should probably be aware that
there may be limitations in RDF that may also limit applications in
JSON-LD.

Cheers,
Christopher