pierrechoffe
commented
7 years ago @rtroncy here is an example of a simpler representation together with the long path.
This schema shows the Derivation Type Assignment we decided together on page 1. On page 2, I added a "simpler" property : Uxx_is_derivation_type_of. We may not want to ask for "all the possible derivation types of a Work", since it can only have one per institution. OK, institutions may have different points of view, and this query may highlight this, but this is a very limited option. Therefore, the property is oriented the other way around : "what works are (transcription, reduction, etc.)".
So my question is two-fold :
- is this property useful ?
- is its implementation correct ? (it is not implemented as a real shortcut but as a simpler property - simpler in the sense that we lose information : author, date, place)
rtroncy
pasqLisena
@rtroncy you recently said to the nice folk at Erlangen that "we love shortcuts". Can we clarify when shortcuts are useful and how to model and implement them ?
A simple example is u24_has_award. To state that a CD received a Diapason d'Or, we model it through a long path with M34_Award_Assignment, see schema.
But you can see in this schema that we also created u24_has_award : F24_Publication_Expression _u24_hasaward M36_Award "diapason d'or"
The "long path" gives us more info, e.g. the author of the award ("Diapason"), the year, place.
The shortcut just gives us a handy way to answer the simple question "what awards did this CD receive" and also "which CDs received a Diapason". If we want to add a year in our request, we need the long path, so u24 is not a real shortcut, it's a simpler representation, hence the broad title of this issue.
(Yet, I use the word "shortcut" because on a similar case, _R40_has_representativeexpression, the FRBRoo documentation speaks about shortcut for F1 - R50i - F42 - R41 - F2)
So :