The documentation is initially from Thanasis, but everything has moved a long way since he worked on it, and in particular we need to realign it with the API.
There are two main bits to the model -- an Attribute Assignment which represents the condition assessment of an artwork, and a Modification that is the conservation work done on the object.
I think both should hang off the Object, with a part_of link to a wrapper Conservation Project activity. This would follow the Production / Encounter / Creation / Publication / etc pattern for activities related to objects/works for the Modification, and use the attributed_by existing pattern for the assessment.
Thus we would need to add crm:P31_was_modified_by / modified_by to a Modification as part of the Object API, but the Modification itself just follows the regular Production (etc) pattern.
I don't think we should just drop it for 1.0, as it's two full sections of CDWA:
The documentation is initially from Thanasis, but everything has moved a long way since he worked on it, and in particular we need to realign it with the API.
There are two main bits to the model -- an Attribute Assignment which represents the condition assessment of an artwork, and a Modification that is the conservation work done on the object.
I think both should hang off the Object, with a part_of link to a wrapper Conservation Project activity. This would follow the Production / Encounter / Creation / Publication / etc pattern for activities related to objects/works for the Modification, and use the attributed_by existing pattern for the assessment.
Thus we would need to add crm:P31_was_modified_by / modified_by to a Modification as part of the Object API, but the Modification itself just follows the regular Production (etc) pattern.
I don't think we should just drop it for 1.0, as it's two full sections of CDWA:
And the modeling work is already mostly done