W3C home > Mailing lists > Public > public-hydra@w3.org > July 2014

Re: Call for consensus on defining IRI template expansion (ISSUE-30)

From: Ruben Verborgh <ruben.verborgh@ugent.be>
Date: Thu, 17 Jul 2014 10:29:07 +0200
Cc: "public-hydra@w3.org" <public-hydra@w3.org>, Gregg Kellogg <gregg@greggkellogg.net>, Markus Lanthaler <markus.lanthaler@gmx.net>
Message-Id: <05A8B483-904A-4636-AF5D-1DF30E953BA5@ugent.be>
To: Tomasz Pluskiewicz <tomasz@t-code.pl>
> I feel like these decisions are a little bit out of scope for Hydra itself.

As a client, I need to know how to use the URI template
before I can make an API request. Seems necessarily in scope to me.

> Is there no such proposal elsewhere?

I haven't seen any, no.

> The value could then simply be a turtle-formatted RDF object. Even with
> the angle brackets to be consistent.

And also with escaping?

> Though I would not allow prefixed URIs.

Would be difficult indeed if no prefixes are agreed upon
(and it's probably better not to).

> However your initial question was more about how Hydra should define
> what is the parameter and not how to put it there. I think this should
> be the focus.

Both are needed for a client to work.

Received on Thursday, 17 July 2014 08:29:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:53:59 UTC