Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015) from David Wood on 2015-06-11 (public-annotation@w3.org from June 2015)

From: David Wood <david@3roundstones.com>
Date: Thu, 11 Jun 2015 13:58:03 -0400
To: Mark Baker <distobj@acm.org>
Cc: Frederick Hirsch <w3c@fjhirsch.com>, W3C Public Annotation List <public-annotation@w3.org>, "public-ldp@w3.org" <public-ldp@w3.org>
Message-Id: <5A825790-1721-45D8-8632-4B137EAD66A6@3roundstones.com>

Mark (Hi, Mark!) is correct; interrelated specs invariably become a morass. If you want to prove it, try to trace through HTTP, URI, etc, to figure out which characters are allowed in an HTTP URL. Kudos to anyone who can do it in within a single day.

Of course we should be as clean as possible. Just don’t insist upon perfection.

Regards,
Dave
--
http://about.me/david_wood

> On Jun 11, 2015, at 01:14, Mark Baker <distobj@acm.org> wrote:
> 
> This reminds me of that time when we had to revise HTTP to support GIF89a in addition to HTML. And then the CSS update, oy! Don't get me started on JPG!
> 
> No, of course that never actually happened, because that would be silly :P

Received on Thursday, 11 June 2015 17:58:51 UTC