Re: Client POC

Hi Hydranians

It took me some time, but finally I was able to introduce few features and 
improvements for the client POC that I committed several months ago.

In general it's mostly about introducing RDF lists and resource collections 
(previously only literals were supported).

To summarize:

- the API documentation is still not fully hydra compliant, i.e. I'm still 
hesitate to use collections - I will have different data models for data 
types and operations (operation may return Collection, but range for a 
property isn't supposed to be a Collection - I think). Actually I was 
wondering how it should be implemented correctly - if the API documentation 
says that an operation returns a collection, should I put it also in the 
operation response? I prefer not to have these elements in the data payload 
as it would mean additional graph processing to get rid of any non data 
related resources before presenting

- Hydra is somehow ignorant when it comes to RDF lists - I'm denoting that 
an operation or a property is an RDF list by using an OWL'ish "strongly 
typed" RDF list inherited class (some restrictions etc.). I acknowledge RDF 
lists as somehow a separate beings as from RDF point of view it's a 
different beast

- There are few things missing that might cope in handy; i.e. hot to denote 
a display name property or a template - this might be useful when browsing a 
list of entities that can be used as a
value of a relation. Currently it ends up with a property marked as a entity 
"key" with OWL's InverseFunctionalProperty which isn't very nice.

- Current implementation uses a default GET collection operation for a given 
class of resource in several relations, but something more sophisticated 
should be used, i.e. a searchable endpoint that would drive a 
search-as-you-type behaviour. Any ideas on this?

As previously, demo is available at http://szczepanscy.priv.pl/ursa

Feel free to share any thoughts on this.

Best

Karol

PS. Markus, is your PHP JSON-LD processor fixed? It didn't accept @type in 
literals and it prevents me from testing my API documentation generator with 
your console.

Received on Monday, 25 January 2016 19:39:37 UTC