Closed EssyGreen closed 11 years ago
Another way of resolving this could be to have an iProvable interface instead of a Conclusion object. That way anything that exhibits the following properties can be proven
This would enable greater flexibility since it would separate the inheritance (what kind of object this is, what sort of shape it has) from its function (what things can this object do/interact with).
Thus there must be a collection of relevant sources representing evidence/citations for the ProofStatement to make any sense. These are currently held in the "Conclusion" object. Ergo the Confidence and ProofStatement should be properties of the Conclusion and not of the Attribution.
Sorry, didn't catch the reasoning there. Why is a problem that the proof statement is associated with the person who made it? Seems to make sense to me....
I don't have a problem with the Proof being associated with the person who made it but that is implicit by the Attribution in any resource. It's the evidence which is missing and the other half of the equation. For example, I (contributor) could prove that England (place) is in the UK (place), but I can't "prove England". And neither holds any water without the references to the evidence to support my argument. Since none of these are available in the Attribution then the proof is meaningless in the context of the Attribution.
Since none of these are available in the Attribution then the proof is meaningless in the context of the Attribution.
But the proof statement isn't outside the context of the conclusion. Attribution has no meaning outside the context of the data being attributed.
Maybe I can ask from a different angle: why is it okay to have a contributor reference (or timestamp, or whatever else is there) on attribution if it's not okay to have a proof statement on it?
Let's take some examples of things which are Resources and hence have Attributions:
If I'm missing something please illuminate :)
(Just doing some triage.)
The notion of proof statement was refactored and clarified at #144 et. al.
Attribution is effectively documenting the creator of the Resource. (Which is also done via the Dublin Core description so this seems to me to clash.)
Proof, by definition, is the justification for some sort of statement, usually something like why A = B. But, whilst A could be assumed to be the Resource that the attribution is contained in, there is nowhere to define B so it doesn't make any sense.
In a genealogical sense the Proof is a weighing up of the evidence to form a rational conclusion. To use FamilySearch's own definition (see https://www.familysearch.org/learn/wiki/en/Genealogical_Proof_Standard):
Thus there must be a collection of relevant sources representing evidence/citations for the ProofStatement to make any sense. These are currently held in the "Conclusion" object. Ergo the Confidence and ProofStatement should be properties of the Conclusion and not of the Attribution.