Re: "Hosting POSTed resources" user-story

Eric,

I've had no takers for my request to edit the "Hosting POSTed resources", so as this is roughly in line with your current task to add narrative for ISSUE-30 I'd like to combine them. i.e. Volunteer you.
I think "Hosting POSTed resources" can be renamed as "Hierarchical bugtracking service", and the user story can talk about the capabilities you'd like in such a service. Links to real tools (and ontologies?) offering equivalent functionality would be useful.

* nested containers
* moving resources between containers.

Thanks in advance, Steve.

On 29 Nov 2012, at 00:10, steve.battle@sysemia.co.uk wrote:

> I would like a volunteer to rewrite the "Hosting POSTed resources" user-story <http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#Hosting_POSTed_Resources>. The story would also benefit from being renamed.
> 
> Currently, it is a single example that motivated discussion about identifying and naming a created resource from within a posted RDF representation (the resulting resolution of issue-20 being that the null relative URI named the created resource). Tim Berners-Lee also raised the related "relative URIs are crucial" issue (resolved by issue-29 as best-practice).
> 
> We think it would be good to keep these issues represented as a user-story. We need a paragraph or two covering the issues; Why are these relative URIs useful in particular applications? However, in it's present form it'll have to go. 
> 
> Steve.
> 
> Steve Battle
> 
> -- 
> Steve Battle
> Semantic Engineer
> 
> E-mail: steve.battle@sysemia.co.uk
> Web: www.sysemia.com
> 
> Sysemia Limited
> The Innovation Centre, Bristol&  Bath Science Park, Dirac Crescent, Emerson's Green, Bristol BS16 7FR
> Registered in England and Wales. Company Number: 7555456
> 
> DISCLAIMER
> 
> Information contained in this e-mail is intended for the use of the addressee only, and is confidential and may also be privileged. If you receive this message in error, please advise us immediately. If you are not the intended recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Attachments to this e-mail may contain software viruses which may damage your systems. Sysemia Ltd have taken reasonable steps to minimise this risk, but we advise that any attachments are virus checked before they are opened.
> 
> 
> 
> 
> 
>