Sorry, that is unclear.
Currently, if a removal is attempted against an object that has live
references, the removal is aborted -- a very safe approach to be sure.
My thought was that we could possibly make this more intelligent and at
the same time allow the registry to deal with routine business evolution
-- users leaving the company, data models being refactored, etc.
So, my thinking was to allow a registry administrator to delete an
object and at the time of removal specify that all references to the
object being deleted be targetted/based at/on a new object. The new
object could be an equivalent object, or even a link to an auditable
event which would allow browsers to at least see that a reference was
forcibly removed.
Thanks,
Matt
Farrukh Najmi wrote:
>
> Matt,
>
> Please clarify clearly what you intended to convey in this comment.
> Thanks.
>
> Line 1410: "I would prefer if we could allow an overide that says
> "point references to this object, such as an auditable event that
> chronicles the deletion"."
>
