- From: Roger Menday <Roger.Menday@uk.fujitsu.com>
- Date: Thu, 7 Mar 2013 20:40:21 +0000
- To: Erik Wilde <Erik.Wilde@emc.com>
- CC: "public-ldp-wg@w3.org Working Group" <public-ldp-wg@w3.org>
- Message-ID: <0280EAF4-845C-4DAF-A1B5-E815D87923A7@uk.fujitsu.com>
>> Navigation is on the web is moving (i.e. browsing) between domain data >> resources. Along on the way we may want to interact to create new >> resources. This interaction is done using other methods POST, PUT, etc, >> via 'interaction' resources (which are discovered/linked inside the LD). > > just as a clarification: there is no such thing as an "interaction > resource". resources are identified by URI and are encountered by > following links. the link itself has interaction semantics (such as "use > POST when submitting form content to the action URI") based on the link > relation type, and because of these semantics, the client knows what it is > supposed to do (and what it is expecting to happen) when following that > link. I fully agree and concur with you on that. I think it is clear that I introduced these "informational" and "interaction" words for the purposes of clarification in this discussion ... Roger p.s. the informational resources are also the bookmark-able ones. > > for example, while the factory model of POSTing to a factory is a common > how to handle resource creation, it is only one pattern how to use > interactions to create new resources. > http://dret.typepad.com/dretblog/2011/11/creating-resources-with-get-put.ht > ml is another pattern. combining differently typed links (with their > interaction semantics) into meaningful and robust application flows is one > of the biggest challenges when it comes to designing RESTful services. > > cheers, > > dret. >
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Thursday, 7 March 2013 20:41:32 UTC