- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Wed, 7 Oct 2015 21:43:37 +0200
- To: Asbjørn Ulsberg <asbjorn@ulsberg.no>
- Cc: "Hydra" <public-hydra@w3.org>, "Kingsley Idehen" <kidehen@openlinksw.com>
Well, it was all about returned values. For a UI you have to know whether the returned is either a multi or single values. This was reflected in the UI either with a grid or key-value pair fields. As for custom extensions, we had to cover (in short): - C# dictionary / Java map data structures (formally it's key-value pairs collection, but key is unique) - this is actually not covered natively by RDF itself, we hade our own structure here - multi-values for grid based views - single-values for key-value pair views - named individuals (i.e. enumerated values) for dropdowns - other than RDF expected/returned values (i.e. API allowed to have an URI for resource's label accepting ... string - this doesn't fit to hydra's class expectation) - property value change event (we had to know whether the value changed to send back a CQRS command to the server). >From all of these sorting was the easiest - this required rdf lists which are the simplest to identify as there is a separate class for that! Regards Karol -----Oryginalna wiadomość----- From: Asbjørn Ulsberg Sent: Wednesday, October 7, 2015 9:08 PM To: Karol Szczepański Cc: Hydra ; Kingsley Idehen Subject: Re: the necessity of describing responses in-band 2015-10-07 19:34 GMT+02:00 Karol Szczepański <karol.szczepanski@gmail.com>: > I did create to one of the projects we had a prototype of a Hydra driven > AngularJS client that built dynamically views from server side provided > information. Very interesting! > It was based on the API documentation part of Hydra rather than on > on-the-fly discovered hypermedia controls. Unfortunately, Hydra is not > there > yet to fully support this approach and we had to use few "extensions". I'm very interested to know what limits you faced and which extensions you had to create. I believe Hydra should support what an AngluarJS application needs to function out of the box, without any extensions. This is exactly what I want to achieve as well! > I'm going to shed some more light on this in a separate post as it > touches a private project of mine that actually struggles from similar > issues. I'm looking forward to hearing more about this. Exciting stuff! :) -- Asbjørn Ulsberg -=|=- asbjorn@ulsberg.no «He's a loathsome offensive brute, yet I can't look away»
Received on Wednesday, 7 October 2015 19:43:45 UTC