Since the version 1.6, the data navigator can render deleted objects. The XML of deleted objects contains a "nav:deleted" element detailing when/by whom/how the object was deleted - e.g.:

<image . . . >

. . .

<nav:deleted Code="Normal" Time="2012-11-24T20:35:54.907Z" PurgeTime="2012-12-01T20:35:54.907Z" UserId="1705">

<user idref="obj1705">

. . . user that deleted the object . . .

</user>

</nav:deleted>

. . .

</image>

Deleted objects can contain references to objects that are no longer in the database (i.e. that have been deleted and purged). References to such objects are removed from the XML of the deleted obejcts, and listed in a special "nav:invalidRefs" element - e.g.:

<story . . .>

. . .

<nav:invalidRefs>

<nav:attr n="story.objs" ids="33479" /> 

</nav:invalidRefs>

. . . 

</story>

indicates that the story references an object with id 33479 via its 'objs' attribute, and that such object no longer exists.

The commands do.ashx?cmd=feed and do.ashx?cmd=auditnav have a new deleted options that indicates if deleted objects should be rendered or not. Possible values are:

•Exclude: deleted objects are not rendered and cause an error (the default);

•Include: both deleted and normal objects are rendered;

•Only: only deleted objects are rendered, attempts to render normal objects cause an error.

Note that when rendering also deleted objects - i.e. every time deleted is not Exclude - the do.ashx?cmd=feed commands does NOT cache the generated XML, each request will re-generate it from scratch.