- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Mon, 15 Jun 2015 22:13:27 +0200
- To: <public-hydra@w3.org>
- Cc: <greg@evilfunhouse.com>, "'Ruben Verborgh'" <ruben.verborgh@ugent.be>, "'Kjetil Kjernsmo'" <kjetil@kjernsmo.net>
On 11 Jun 2015 at 11:30, Ruben Verborgh wrote: >> hydra:entrypoint could be a candidate, although I'm not too big a fan of >> the semantics: there's not really one entry point into a TPF interface; >> each fragment is an entry point. > > Yeah, I don't like it for the same reason. It should be something like > hydra:youCanStartAnywhereForExampleHere :-) But I think I can live with > it. What don't you guys like about entrypoint's semantics? That it says it is the "main" entrypoint? >>> hydra:search has an IriTemplate as domain, so is probably not the >>> property we are looking for. >> >> Unless they actually link to the IriTemplate, which arguably would suffice >> in many cases... Wouldn't it? It might even be a good idea > > I think this is a very good idea indeed. > If you link straight to this template, > you directly link to the hypermedia control that does TPF. > Also, it expresses just the semantics you're after, > i.e., "you can search this collection through X". > > I would go for that! That would work but in general I would try to keep the number of Link headers low. What about using hydra:apiDocumentation instead? -- Markus Lanthaler @markuslanthaler
Received on Monday, 15 June 2015 20:14:35 UTC