Within Atompub, the distinction between edit and edit-media was largely a bit of a necessary hack given the lack of any kind of formal data model around a resource and it's data model. Within ldp, there exists the opportunity to tighten this up significantly by leveraging things like "describedBy" and "describes". A resource and that resource's metadata are essentially two distinct related resources (in fact, there can be a one-to-many relationship between the two). These can, and should be managed just as you would manage any other kind of resource relationship. On Wed, Oct 3, 2012 at 2:44 PM, Wilde, Erik <Erik.Wilde@emc.com> wrote: > hello. > > On 2012-10-03 11:08 , "Henry Story" <henry.story@bblfish.net> wrote: > >I worked on the Atom spec. And at the time I put together an AtomOwl > >ontology http://bblfish.net/work/atom-owl/2006-06-06/AtomOwl.html > >I am not sure it is that good. > >But it could be a basis to see how close ldp ontology is to Atom. > > there are some differences because of the different metamodel foundations, > but the general concepts we're dealing with have a lot of similarities. > http://dret.typepad.com/dretblog/atom-landscape.html just got a very > useful addition, btw, which is a mechanism how DELETE events can now be > represented in atom (RFC 6721). now a collection manager can provide a > feed of updates, and others can listen and perform all possible actions > (create/update/delete) to synchronize their local collections. very useful! > > cheers, > > dret. > > >
Received on Thursday, 4 October 2012 19:39:57 UTC