Comments on: REST design question #3: meaning of a link https://quoderat.megginson.com/2005/02/18/rest-design-question-meaning-of-a-link/ Open information and technology. Tue, 22 Feb 2005 23:25:50 +0000 hourly 1 http://wordpress.com/ By: Bo https://quoderat.megginson.com/2005/02/18/rest-design-question-meaning-of-a-link/#comment-95 Tue, 22 Feb 2005 23:25:50 +0000 /?p=22#comment-95 Don’t really see what you’re getting at here though I’d be happy to continue discussing RESTful architectures with you.

]]>
By: AsynchronousBlog https://quoderat.megginson.com/2005/02/18/rest-design-question-meaning-of-a-link/#comment-94 Sat, 19 Feb 2005 23:24:15 +0000 /?p=22#comment-94 REST Design questions 2 and 3
Dave Megginson continues with his REST design questions. Herein, I respond: Question #2 … Yup, I’ve used query-paramaters in the way you describe to paramaterize a large resource space. I don’t consider it particular inelegant or ugly, but maybe th…

]]>
By: Quoderat » REST design question #4: how much normalization? https://quoderat.megginson.com/2005/02/18/rest-design-question-meaning-of-a-link/#comment-96 Tue, 30 Nov -0001 00:00:00 +0000 /?p=22#comment-96 […] find the name of the director or production company, but it still knows where to look for more complete information. It can also use t […]

]]>
By: Quoderat » REST design question #5: the “C” word (content) https://quoderat.megginson.com/2005/02/18/rest-design-question-meaning-of-a-link/#comment-97 Tue, 30 Nov -0001 00:00:00 +0000 /?p=22#comment-97 […] nd the edge of the content problem dipping in its toes with issues like identification and linking, but now that the design questions ar […]

]]>
By: Quoderat » REST design question #5: the “C” word (content) https://quoderat.megginson.com/2005/02/18/rest-design-question-meaning-of-a-link/#comment-98 Tue, 30 Nov -0001 00:00:00 +0000 /?p=22#comment-98 […] nd the edge of the content problem dipping in its toes with issues like identification and linking, but now that the design questions ar […]

]]>