Open azaroth42 opened 4 years ago
Discussion in call on 2020-10-07: Allow carried_by
on the Name, as it is a linguistic object as well as an appellation.
(Would also work with Identifier, as carried_by is for Symbolic Object, of which Linguistic Object is a descendent)
Propose defer to 1.1
Related to #348
With #586 this becomes much easier. The AttributeAssignment can used_specific_object
of the part that carries the name. It can in turn carry the LinguisticObject that contains the text of the name. Then the Name and the text are not the same thing ... but I think that's okay -- the text is the source of the name, not the name itself.
Not sure we need an entry in the model for it, but perhaps a cookbook recipe?
From Rijksmuseum data mapping exercise...
Names of objects can be inscribed on some identifiable part of them, such as the back or frame of a painting. The text of the name is thus
carried_by
the part of the object. The API division of the model has parts as separate documents, and there is no way to refer to arbitraryName
nodes.Possible solutions:
carried_by
the part of the object, which doesn't itself know the text of the name.carries
, and the name on the object has asameAs
link to it?used_specific_object
the physical part ... except we don't really know this. It could have been assigned and then written on the back of the painting long afterwards.(Thanks to @edwardanderson for this)