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

Re: ldp-ISSUE-40 (image): creating/deleting/changing non RDF resources [Use Cases and Requirements]

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Thu, 22 Nov 2012 13:40:08 -0500
To: Henry Story <henry.story@bblfish.net>
CC: Arnaud Le Hors <lehors@us.ibm.com>, Linked Data Platform Working Group <public-ldp-wg@w3.org>
Message-ID: <FFED4F38-4E79-4679-8823-5B9CE6EAFF6E@emc.com>

On 22 Nov 2012, at 10:20, "Henry Story" <henry.story@bblfish.net<mailto:henry.story@bblfish.net>> wrote:
I am not sure what "Create an un-contained resource<http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#Create_an_un-contained_resource>" is about, but probably it's about a PUT
in a container of a resource. (the section is empty)
I think there should be a section
     - Create a non-rdf resource
  and it should specify that in a container that allows that (hot to signal this should be
specified ) one can  POST a binary with a mime type to the container.

in AtomPub, a collection lists the media types it accepts, and i think this is pretty much the only way to handle this. specify what you accept, and then clients know what they can POST.

     From there DELETEing and PUTing such a resource should be easy to define.
One would not specify a diff for such a resource of course, and any other linked data
specific operations. But one should be able from the header to find metadata about that

one thing to keep in mind is how to find the media resource. when you GET container contents, you get the metadata entry. from there, there must be a well-defined link to the media resource which then allows you to interact with the media resource.


Received on Thursday, 22 November 2012 18:41:01 UTC

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