- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Wed, 16 Jul 2014 13:35:46 +0200
- To: Lee Curtis <lee.curtis@me.com>
- Cc: public-hydra@w3.org
- Message-ID: <CAKaEYhJ82qwAM6rwnwtBn0Q-4V3WM+d1k7UT_qU5ArGFO2YkPw@mail.gmail.com>
On 11 July 2014 10:32, Lee Curtis <lee.curtis@me.com> wrote: > > Hi All, > > Thanks for your hard work on Hydra-CG. I was working on similar, so great > to see I can focus on core logic again :-) > > I believe Hydra is a major step forward to semantic interoperability with > the RoTW (rest of the world) . > > A couple of initial observations: > > My team and I prefer N3 notation. I understand JSON-LD aligns more with > target audience of web developers. Fair call. > +1 Would love to see more support for turtle / n3. Not that there's anything wrong with JSON LD. > > In my domain, both the server and client will share the same Hydra > “contract". > > I’m keen to work with IRITemplates but not sure how they link to > hydra:Class. > > FYI: I have quite a few APIs that I want to abstract via properties, and > use the template to instantiate them. > > I’d love to see some worked examples, ideally in N3/Turtle (since a more > real-world semantic model is easier to read in a clean triple notation, > JSON-LD seems OK for snippets or during transport) > > Showing my ignorance ... > > AFAICT, I can query for all templates that have properties in common with > my hydra:Class (my Endpoint/Servlet?). But since the IRITemplates link via > IRITemplateMapping via Properties - it seems ambiguous. > > Anyways, well done :-) Looking forward to getting it all wired up and > working ... > > Best Regards > > -lee- > > FYI: Our App is at: http://www.scorpio4.com/ - we have more code / tests > /docs to add, but an initial public release is set for end of July. > >
Received on Wednesday, 16 July 2014 11:36:14 UTC