W3C home > Mailing lists > Public > public-ldp-wg@w3.org > November 2012

Re: ldp-ISSUE-30 (bugtrack): Hierarchical bugtracking service [Use Cases and Requirements]

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Wed, 07 Nov 2012 16:31:28 +0000
Message-ID: <509A8CE0.3080808@epimorphics.com>
To: public-ldp-wg@w3.org


On 05/11/12 15:39, Linked Data Platform (LDP) Working Group Issue 
Tracker wrote:
>   POST /SomeProduct { <> a :Bug } yields { /Bugz/bug2 a :Bug }

I read that as a response of 201/"Location: /Bugz/bug2" and
content { /Bugz/bug2 a :Bug } at /Bugz/bug2.

Presumably POSTing { <> a :FeatureRequest } causes a different template 
for the URI allocated:

Location: /Feature/request2331

This is a great example - the data has driven the server's decisions on 
the response.

	Andy
Received on Wednesday, 7 November 2012 16:31:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:42 UTC