- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 21 Jul 2014 21:36:03 +0200
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-hydra@w3.org
> Think of an HTML form using GET. And more specifically, think of the enctype attribute on <form>. It can have the following values: - application/x-www-form-urlencoded - multipart/form-data - text/plain These are ways to tell the client (browsers) how the values should be sent. We're doing the exact same here: Hydra's representation is HTML's enctype. @Markus: notice there are 3 values above by the way; maybe another (minor) case to not choose just a boolean: new alternatives can always come up, even for something simple as <form>. > I think we should try to avoid the need to handle all the complexity that > Turtle escaping introduces. I don't want to introduce a dependency on Turtle > and I don't want developers to have to deal with it (or use a Turtle > library). The proposed expansion mechanism allows makes it trivial to decode > values: a simple regex or a couple of lines of code are more than enough. Strong +1 here, very good argument for not doing Turtle. Ruben
Received on Monday, 21 July 2014 19:36:43 UTC