rest-discuss at Yahoo! Groups

Re: S/W engineering radio webcast comments

Subbu Allamaraju — Thu, 15 May 2008 14:41:32 GMT

... These are two *distinct* architectural styles. Not sure what he is trying to sell. Regards, Subbu

Re: character encodings and binary data and URLs

Daniel Yokomizo — Thu, 15 May 2008 14:17:26 GMT

... This is a reference (together with RFC1738 and RFC3986) I use to solve URL encoding issues: http://www.blooberry.com/indexdot/html/topics/urlencoding.htm

Re: auto-discovery of multiple representation types

Julian Reschke — Thu, 15 May 2008 14:03:17 GMT

... Nit: WebDAV nowadays is defined by RFC4918, which *is* based on RFC2616. ... Or, the issue tracker: . ...

Re: auto-discovery of multiple representation types

Eric J. Bowman — Thu, 15 May 2008 13:46:01 GMT

... Your terminology is a bit confusing. A resource is not served by a webserver, only representations are. A resource has an identifier, which a webserver

Re: auto-discovery of multiple representation types

Sebastien Lambla — Thu, 15 May 2008 13:11:09 GMT

[reposted, as I have forgotten the list] ... A representation of a resource carries some or all parts of a resource. A picture of a horse is a representation

character encodings and binary data and URLs

zooko — Thu, 15 May 2008 13:02:30 GMT

Dear people of rest-discuss: What's the right way to specify character encoding in URLs, POST forms, and JSON-encoded data? I work on an open source secure,

Re: S/W engineering radio webcast comments

Stefan Tilkov — Thu, 15 May 2008 09:52:37 GMT

I thought that even the WS-* folks now acknowledge that there is a huge architectural difference, even if they don't concede that there's any benefit to the

S/W engineering radio webcast comments

Sean Kennedy — Thu, 15 May 2008 09:46:21 GMT

Hi, I was recently listening to a webcast by Olaf Zimmerman on Software Engineering radio www.se-radio.net. In this webcast he stated that a good share of the

Re: auto-discovery of multiple representation types

Eric J. Bowman — Wed, 14 May 2008 23:49:23 GMT

... Sorry, I only meant to use the word 'deprecates' not 'obsoletes'. Yes, RFC 2068 is obsoleted as a standalone reference for HTTP. But, if I were to agree

Re: auto-discovery of multiple representation types

Erik Hetzner — Tue, 13 May 2008 16:17:25 GMT

At Tue, 13 May 2008 05:41:21 -0600, ... best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3

Re: auto-discovery of multiple representation types

Eric J. Bowman — Tue, 13 May 2008 11:41:09 GMT

... Really? An RDF document can't be a representation of a resource? I don't see where httpRange-14 or anything else makes such an assertion. ... Fallacious?

Re: auto-discovery of multiple representation types

Sebastien Lambla — Sun, 11 May 2008 19:03:49 GMT

There's been a huge long discussion about this very issue in TAG, you may want to check it out. It comes down to the result of having httpRange-14. If you get

Re: auto-discovery of multiple representation types

mike amundsen — Sun, 11 May 2008 15:50:45 GMT

Lucas: As Mark has pointed out, the Link Header has been around for a while. FireFox and Opera both support it for stylesheets

Re: auto-discovery of multiple representation types

Mark Baker — Sun, 11 May 2008 01:07:36 GMT

... It was never, AFAIK, fully specified, but this was Roy's preferred way (AIUI) of doing conneg; http://www.rfc.net/rfc2068.html#s19.6.2 Also on topic;

Re: auto-discovery of multiple representation types

Lucas Gonze — Sat, 10 May 2008 19:22:48 GMT

I agree. And I think that this gets to the heart of the problem that oEmbed is addressing -- generalizing link-rel functions to arbitrary payload types. So