- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Tue, 16 Jun 2015 07:56:07 +0200
- To: Erik Wilde <dret@berkeley.edu>
- Cc: Hydra <public-hydra@w3.org>, Kjetil Kjernsmo <kjetil@kjernsmo.net>, Markus Lanthaler <markus.lanthaler@gmx.net>
> instead of using link relation types which are specific for a media type (which is an anti-pattern that should be avoided) It's not specific for a media type, depending on the definition of "media type". The proposed link would point to a hypermedia control, which can be available in different media types (HTML, JSON, Turtle, …) > - "home" as proposed by https://github.com/mnot/I-D/issues/41 But it's not really "home". The semantics we need are "you can also access this dataset as". > - "service-desc" as proposed by http://tools.ietf.org/html/draft-wilde-service-link-rel-00 It's not a description either, and this is why I don't think that Markus' hydra:apiDocumentation suggestion is appropriate either. > link relations should signal a client *why* to follow a certain link in a given context, and not *what* exactly to expect in terms of media types. "if you want to access this dataset in another way, follow…” Best, Ruben
Received on Tuesday, 16 June 2015 06:08:40 UTC