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: Richard Cyganiak <richard@cyganiak.de>
Date: Mon, 5 Nov 2012 19:36:17 +0000
Message-Id: <A07CF4C7-15F0-4FC0-A110-B01C1F4877C4@cyganiak.de>
To: Linked Data Platform (LDP) Working Group <public-ldp-wg@w3.org>
Eric, question for clarification: Is moving/reassigning the comment a matter of deleting the old one and creating a new one? If not, why not?

Best,
Richard


On 5 Nov 2012, at 15:39, Linked Data Platform (LDP) Working Group Issue Tracker wrote:

> ldp-ISSUE-30 (bugtrack): Hierarchical bugtracking service [Use Cases and Requirements]
> 
> http://www.w3.org/2012/ldp/track/issues/30
> 
> Raised by: Eric Prud'hommeaux
> On product: Use Cases and Requirements
> 
> issues:
>  nested containership.
>  moving contained members.
> 
> POST /SomeProduct { <> a :Bug } yields { /Bugz/bug2 a :Bug }
> POST /Bugz/bug2 { <> a :Comment } yields { /Comments/comment3 a :comment }
> Alice notices that /Bugz/bug2 is the same as /Bugz/bug1, reassigns comment3 and deletes bug2.
> 
> or with names reflecting the hierarchy:
> POST /SomeProduct { <> a :Bug } yields { /SomeProduct/Bugz/bug2 a :Bug }
> POST /SomeProduct/Bugz/bug2 { <> a :Comment } yields { /SomeProduct/Bugz/bug2/Comments/comment3 a :comment }
> Alice notices that /SomeProduct/Bugz/bug2 is the same as /SomeProduct/Bugz/bug1, reassigns comment3 and deletes bug2.
> 
> 
> 
> 
Received on Monday, 5 November 2012 19:36:46 UTC

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