Issue 461: Attribute Assignment of .1 properties
Posted by Robert Sanderson on 3/12/2019
With the addition of P177 assigned property type, we can associate a relationship with an Attribute Assignment. This is wonderful, as it lets us be clear about the relationship that the attribute assignment is expressing.
However, some properties are 3-tuples, as expressed in the first order logic, with a .1 property that qualifies the relationship further. We currently cannot add the qualifier to the attribute assignment when using a property that allows these, and to be able to do so would be very beneficial.
To project the example of P14 into an Attribute Assignment:
The painting of the Sistene Chapel (E7) was carried out by Michaelangelo Buonaroti (E21) in the role of master craftsman (E55).
A very typical attribution of which most organizations have many instances.
An Attribute Assignment could look like:
<aa1> a E13_Attribute_Assignment ;
a E7 Activity ;
rdfs:label “Painting of the Sistene Chapel Activity” ] ;
a E21_Person ;
rdfs:label “Michaelangelo Buonaroti” ] ;
P177_assigned_property_type <P14_carried_out_by> ;
a E55_Type ;
rdfs:label “master craftsman” ] .
Or some other less verbose name for the new property.
Many thanks for your consideration, fellow SIG-folks.
In the 48th CIDOC CRM and 41st FRBR CRM sig meeting (virtual), the sig discussed about adding qualifiers to the attribute assignment when using a property that allows these, and which would be very beneficial and assigned to MD and RS to write a short text to describe the alternatives for assigning .1 properties and discuss materialization of the referred property.
In the 53rd CIDOC CRM & 46th FRBRoo SIG meeting, the SIG reassigned the HW to RS and MD. It is about adding a qualifier to an attribute assignment. Postpone the issue, until HW has been turned in.
HW: MD, RS