Tatsuya Noyori wrote: > I like Atom syntax. And I think analogy is important. So I > hope that the tombstones is similar in syntax to Atom > syndication format.
I agree. > I hope Sync covers Media Entry, such as image files or pdf > files. And I think Media Entry needs Atom Feed like the following. > > <entry> > <title>Test.gif</title> > <link rel="media" > href="http://localhost:8080/roller/Tokyo/resource/images/Test.gif"/> > > <id>http://localhost:8080/roller/roller-services/app/Tokyo/res > ource/images/Test.gif</id> > <published>2007-11-02T05:20:58Z</published> > <updated>2007-11-02T05:20:58Z</updated> > <content type="xhtml"> > <div xmlns="http://www.w3.org/1999/xhtml"> > <a > href="http://localhost:8080/roller/Tokyo/resource/images/Test.gif"/> > </div> > </content> > </entry> As a RFC 5023 media link entry, it would look like this: <entry> <title>Test.gif</title> <link rel="media" href="http://localhost:8080/roller/Tokyo/resource/images/Test.gif"/> <id>http://localhost:8080/roller/roller-services/app/Tokyo/resource/imag es/Test.gif</id> <published>2007-11-02T05:20:58Z</published> <updated>2007-11-02T05:20:58Z</updated> <content src='http://localhost:8080/roller/Tokyo/resource/images/Test.gif'/> </entry> > <!-- Extended deleted-entry --> > <at:deleted-entry> > <at:link rel="media-trash" > href="http://localhost:8080/roller/Tokyo/resource/images/Test.gif"/> > > <at:id>http://localhost:8080/roller/roller-services/app/Tokyo/ > resource/images/Test.gif<at:id> > <at:deleted>2005-11-29T12:11:12Z<at:deleted> > <at:by> > <at:name>John Doe</at:name> > <at:email>[EMAIL PROTECTED]</at:email> > </at:by> > </at:deleted-entry> > </feed> An AtomPub client that depends on anything more than that <atom:id> element being present in a tombstone is going to be non-portable. For that reason, I recommend against putting additional information in the tombstone. Anyway, it is better to specify the trash/soft delete/undelete mechanism seperately from the tombstone mechanism. - Brian
