Dear all, The current scope note of E55 Type is as follows
"This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes. E55 Type is the CRM's interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties." In the first paragraph the class is restricted to " concepts denoted by terms from thesauri and controlled vocabularies". The FRBRoo class F3 Manifestation product type is a subclass of E55 Type. An instance of F3 Manifestation product type is typically an abstraction over what exemplars (physical printed books) of a print have in common. It is too strong to require that such an abstraction has to be denoted by a term from a thesaurus or a controlled vocabulary to be an instance of F3 Manifestation product type. As all instances of any CRM/FRBRoo class it has to have an identification but that is a weaker condition. My suggestion is that the scopenote should be weakened to something like "This class comprises concepts typically denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes. E55 Type is the CRM's interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties." Regards Christian-Emil
