Re: Returning HTTP codes with HTML descriptions. from Wilde, Erik on 2012-11-03 (public-ldp-wg@w3.org from November 2012)

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Fri, 2 Nov 2012 20:54:42 -0400
To: Alexandre Bertails <bertails@w3.org>
CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>, Andrei Sambra <andrei@fcns.eu>
Message-ID: <37924E9F-5DE0-47B9-8BEF-6D52AB616BD7@emc.com>

hello.

On Nov 2, 2012, at 16:03, "Alexandre Bertails" <bertails@w3.org> wrote:
> There are some interesting ideas in this spec, but in our case, the
> client already understands RDF, so I don't see why we would return
> anything but RDF for "problem details".

i knew you'd say that ;-) then why not derive RDF from the JSON model? that's what i'm doing, the idea is that the abstract model should be consistent across different concrete models.

cheers,

dret.

Received on Saturday, 3 November 2012 00:55:43 UTC