- From: Wilde, Erik <Erik.Wilde@emc.com>
- Date: Wed, 27 Mar 2013 17:37:47 -0400
- To: Richard Cyganiak <richard@cyganiak.de>
- CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
hello richard. On 2013-03-27 13:55 , "Richard Cyganiak" <richard@cyganiak.de> wrote: >I'm not convinced that the WG should take on the work of designing a >general purpose RDF-based feed/syndication mechanism. We have enough on >our plate. i thought this was exactly what we had on our plate, and PROV would be a good way of showing that we can actually do it. we want to expose containers (feeds) of resources (entries), and we want to expose linked data that allows clients to interact with these by reading, creating, updating, and deleting them. we had a lot of discussions around atom when we started, and i understand than some of the design decisions are different because of a different metamodel foundation. but i cannot remember anybody saying that what we wanted to do was fundamentally different. i am interested to hear where you think the fundamental differences are (apart from the RDF vs XML discussion). when i look at all of our user stories, these are stories which trivially map to feed architectures, apart from the fact that we have the RDF requirements. and even if you don't want to call them feeds (because of the XML implication), i would be interested where you think that our task is to design something fundamentally different. thanks and cheers, dret.
Received on Wednesday, 27 March 2013 21:38:26 UTC