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: Steve K Speicher <sspeiche@us.ibm.com>
Date: Mon, 5 Nov 2012 14:55:55 -0500
To: public-ldp-wg@w3.org
Message-ID: <OFF03EEDE1.641A3C92-ON85257AAD.006C406F-85257AAD.006D7D84@us.ibm.com>
Perhaps a more typical use case that I've seen that has the same low level 
needs is that someone wants to "move" a bug from one project/product to 
another.  The ideal would be that the URI for that bug would not change, 
only the container it is in.

For example, there would be 2 containers:
:projectA
   a ldp:Container;
   rdfs:member <http://example.org/resources/bug123> .

:projectB
   a ldp:Container.
 
The desired end resource would be to have bug123 to be a member of 
projectB.  It "might' be a fine outcome if there was a new resource (new 
URI) created and the old URI is left with a redirect left in place.

Leaving hierarchy out as doesn't pertain to this case.

Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web -> 
http://open-services.net

"Linked Data Platform (LDP) Working Group Issue Tracker" 
<sysbot+tracker@w3.org> wrote on 11/05/2012 10:39:49 AM:

> From: "Linked Data Platform (LDP) Working Group Issue Tracker" 
<sysbot+tracker@w3.org>
> To: public-ldp-wg@w3.org, 
> Date: 11/05/2012 10:42 AM
> Subject: ldp-ISSUE-30 (bugtrack): Hierarchical bugtracking service [Use 
> Cases and Requirements]
> 
> 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:56:31 UTC

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