[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: AW: [sdo] ISSUE 165: Define behavior of DataObject.delete wrtChangeSummary
Hi Blaise,
If the behavior you describe is acceptable, then we can
close this issue with no action. The current wording is that change
summary represents a diff between the old state and the new state, with created
objects being objects that have entered the scope, and deleted objects being
objects that left the scope. What calls were used to achieve this doesn't
enter into the equation. By the way, do you agree with this definition of
"create" and "delete"? This is also something that is being discussed in
the calls.
I think there is a general feeling in the group that this
behaviour will be surprising to users. Although the spec doesn't really
say so, simply by calling a method named "delete" (as opposed to,
say, "detach"), I think the user has signified an intention, namely, that
he wishes the object be deleted from the data store. And the
worry is, that representing a delete/ reattach as a move, we are losing this
intention.
The
problem with the sentence you quote is that it doesn't say how this scenario is
represented in the change summary, and I'm worried that users will expect it be
represented as a delete and a create. Perhaps the most backwards
compatible way to go is simply to clarify this in the spec. Perhaps
we should simply remove the sentence, that is, unless someone comes up with a
use-case why the user would want to re-attach a deleted object. We
can leave the behaviour implementation dependent. We all agree that most
users don't reattach deleted objects. And if the object is not
reused, we already have the correct behavior: the object appears as deleted in
the change summary. If the user does a re-attach, he's on his
own.
Ron
Von: Blaise Doughan [mailto:blaise.doughan@oracle.com] Gesendet: Donnerstag, 17. September 2009 16:38 An: Barack, Ron Cc: sdo@lists.oasis-open.org Betreff: Re: AW: [sdo] ISSUE 165: Define behavior of DataObject.delete wrt ChangeSummary Hi Ron,
I'm still on leave, but these darn new phones make it too hard to leave
work behind entirely.
If I delete an object, and then re-add it, as a user I would be surprised
to get an error. This use case is not nonsensical but it would be done
rarely.
The
spec is clear on this point, not sure why we would add in weasel words. Is
there a use case this line is preventing?
-Blaise
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]