W3C home > Mailing lists > Public > public-ldp@w3.org > June 2013

Re: Proposal to close ISSUE-19: Adressing more error cases, as is

From: Henry Story <henry.story@bblfish.net>
Date: Tue, 4 Jun 2013 07:21:33 +0200
Cc: public-ldp@w3.org
Message-Id: <E554556E-AAAA-4546-8309-6CC4C160E125@bblfish.net>
To: Kingsley Idehen <kidehen@openlinksw.com>

On 3 Jun 2013, at 22:30, Kingsley Idehen <kidehen@openlinksw.com> wrote:

> On 6/3/13 3:31 PM, Erik Wilde wrote:
>> which would get to the touchy issue of media types. application/api-problem+json and application/api-problem+xml are the current media types, would an RDF model follow what pattern and expose application/api-problem+turtle? 
> No, since API problems ultimately boil down to entity relationships. The format is ultimately irrelevant.

Agree with Kingsely. This issue is not touchy: it is settled. 

In RDF you don't need to create a media type for your responses, text/turtle will
do.  The reason you have to do this with JSON is because, lacking namespaces you have no idea without the
media type wha the content is. 

More useful would be to find which ontologies express the relevant information the user would need.


Social Web Architect
Received on Tuesday, 4 June 2013 05:22:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:16:35 UTC