hypermedia linking - API Craft

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion hypermedia linking
Received-SPF: neutral (google.com: 209.85.214.179 is neither permitted nor denied by best guess record for domain of m...@amundsen.com) client-ip=209.85.214.179;
MIME-Version: 1.0
In-Reply-To: <045ac349-757f-4a64-9e41-2d04affcd5e0@googlegroups.com>
References: <21235821.24.1336790014264.JavaMail.geo-discussion-forums@pbnf3>
	<27688376.1073.1337192194822.JavaMail.geo-discussion-forums@pbbnx3>
	<CAPW_8m5uV7NMgSyNCGT9Axbnj1Zhyx8mM0COriCpHdriKX3...@mail.gmail.com>
	<045ac349-757f-4a64-9e41-2d04affcd5e0@googlegroups.com>
Date: Fri, 18 May 2012 02:11:05 -0400
Message-ID: <CAPW_8m4iZaxMyKwVQzm1GFoCYsxEDFi4Jc+f=Q-yV3anLKs...@mail.gmail.com>
Subject: Re: hypermedia linking
From: mca <m...@amundsen.com>
To: api-craft@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d0444ee1fe3d89804c0496a52

--f46d0444ee1fe3d89804c0496a52
Content-Type: text/plain; charset=ISO-8859-1

and does "Level 3 REST" also say HTML.FORM@method="get" is an anti-pattern?

mca
http://amundsen.com/blog/
http://twitter.com@mamund
http://mamund.com/foaf.rdf#me




On Fri, May 18, 2012 at 1:26 AM, Matthew Bishop <m...@thebishops.org> wrote:

> URI Templates is an antipattern for Level 3 REST (it makes sense for the
> lower levels however). The reason is Level 3 REST clients should be looking
> for links that have certain rel names and following them, not constructing
> URLs.
>
>
> On Wednesday, May 16, 2012 11:23:27 AM UTC-7, Mike Amundsen wrote:
>>
>> Matt:
>>
>> <snip>
>> In general, Level 3 REST APIs should not require any string math on the
>> client. Consider it a code smell.
>> </snip>
>> Interesting POV.
>>
>> So you think RFC6570 (URI Templates) is an anti-pattern for REST
>> implementations?
>>
>> HTML.FORM@method="get" is an anti-pattern for REST, too?
>>
>> mca
>> http://amundsen.com/blog/
>> http://twitter.com@mamund
>> http://mamund.com/foaf.rdf#me
>>
>>
>>
>>
>> On Wed, May 16, 2012 at 2:16 PM, Matthew Bishop <m...@thebishops.org>wrote:
>>
>>> I can't figure out a good use case for the {id} expands in the URL given
>>> that the representation has the ID in the object too. A developer would
>>> find it frustrating and nonobvious to have to do the string math themselves.
>>>
>>> In general, Level 3 REST APIs should not require any string math on the
>>> client. Consider it a code smell.
>>>
>>> Matt Bishop
>>>
>>
>>

--f46d0444ee1fe3d89804c0496a52
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

and does &quot;Level 3 REST&quot; also say HTML.FORM@method=3D&quot;get&quo=
t; is an anti-pattern?<div><br clear=3D"all">mca<br><a href=3D"http://amund=
sen.com/blog/" target=3D"_blank">http://amundsen.com/blog/</a><br><a href=
=3D"http://twitter.com" target=3D"_blank">http://twitter.com</a>@mamund<br>
<a href=3D"http://mamund.com/foaf.rdf#me" target=3D"_blank">http://mamund.c=
om/foaf.rdf#me</a><br><br><br>
<br><br><div class=3D"gmail_quote">On Fri, May 18, 2012 at 1:26 AM, Matthew=
 Bishop <span dir=3D"ltr">&lt;<a href=3D"mailto:m...@thebishops.org" target=
=3D"_blank">m...@thebishops.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
URI Templates is an antipattern for Level 3 REST (it makes sense for the lo=
wer levels however). The reason is Level 3 REST clients should be looking f=
or links that have certain rel names and following them, not constructing U=
RLs.<div class=3D"HOEnZb">
<div class=3D"h5"><div><br></div><div><br>On Wednesday, May 16, 2012 11:23:=
27 AM UTC-7, Mike Amundsen wrote:<blockquote class=3D"gmail_quote" style=3D=
"margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">Ma=
tt:<div>
<br></div><div>&lt;snip&gt;</div><div>In general, Level 3 REST APIs should =
not require any string math on the client. Consider it a code smell.<br>&lt=
;/snip&gt;</div><div>Interesting POV.=A0</div><div><br></div><div>
So you think RFC6570 (URI Templates) is an anti-pattern for REST implementa=
tions?</div><div><br></div><div>HTML.FORM@method=3D&quot;get&quot; is an an=
ti-pattern for REST, too?</div><div><br></div><div>mca<br><a href=3D"http:/=
/amundsen.com/blog/" target=3D"_blank">http://amundsen.com/blog/</a><br>

<a href=3D"http://twitter.com" target=3D"_blank">http://twitter.com</a>@mam=
und<br><a href=3D"http://mamund.com/foaf.rdf#me" target=3D"_blank">http://m=
amund.com/foaf.rdf#me</a><br><br><br>
<br><br><div class=3D"gmail_quote">On Wed, May 16, 2012 at 2:16 PM, Matthew=
 Bishop <span dir=3D"ltr">&lt;<a href=3D"mailto:m...@thebishops.org" target=
=3D"_blank">m...@thebishops.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

I can&#39;t figure out a good use case for the {id} expands in the URL give=
n that the representation has the ID in the object too. A developer would f=
ind it frustrating and nonobvious to have to do the string math themselves.=
<br>


<br>
In general, Level 3 REST APIs should not require any string math on the cli=
ent. Consider it a code smell.<br>
<br>
Matt Bishop<br>
</blockquote></div><br></div>
</blockquote></div></div></div></blockquote></div><br></div>

--f46d0444ee1fe3d89804c0496a52--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
