Thank you. 

This pertains strongly on the idea that relations are resources. If they
are resources, you can PUT. GET and DELETE them. Matts suggestion about
letting people update them with POST sounded good, but if you cannot use
DELETE with content, that raises some problems.

Either we devise a language to embed in the POST content (like Delete,
Update, Create), to work around the problems with where content can be.

Or, we dissallow people to post RDF statements directly to the
datastream.

Or, we allow RDF statements to be POSTed only for updates, never for
deletes.

I actually do not know which of these I prefer. 

On second thoughts, getting the entire RELS-EXT datastream
on /objects/{pid}/relations and being able to post an entire new version
directly to this location could work. If you wanted to combine with the
original relations, you must do it yourself, but you can post RDF
directly, instead of converting this to an URL

Regards

On Fri, 2009-10-30 at 15:03 +0100, Ben Ranker wrote:
> I’m mostly just following the discussion (which I’m very happy to be seeing,
> by the way), but I wanted to clarify this one minor offhanded suggestion:
> 
> Quoth Asger Askov Blekinge on Fri, Oct 30, 2009 at 08:16:49AM -0400:
> > Allowing people to post RDF directly sounds like a good idea, but it has
> > implications. To delete relations, you would then
> > DELETE /objects/{pid}/relations with the RDF content to remove?
> 
> DELETE with content is not allowed in HTTP/1.1.
> 
> RFC 2616, section 9.7 DELETE doesn’t explicitly allow sending an entity body
> in a DELETE reqest, and so section 4.3 Message Body disallows it.
> 
> 4.3 Message Body
> [...]
> “A message-body MUST NOT be included in a request if the specification of
> the request method (section 5.1.1) does not allow sending an entity-body in
> requests.”
> [...]
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fedora-commons-developers mailing list
Fedora-commons-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to