A) Patrick gave a presentation with title "Subject relationships in FRBROO and their implication on CIDOC CRM" to address the issues
- Intermediate class between Conceptual Object and Information Object
- Appellation as a subclass of String
After the presentation we discuss about the substance of Appellation and if the appellation has alternative form and history. Also we changed in the SIS base the Appellation and we put Appellation isA Information Object in order to check the consequences.
In parallel we examined the Issue 144 according to which E7 Activity. P16 used specific object (was used for):E70 Thing should be superproperty of F33 Identifier Assignment.R26: F13 Name, and this implies: that E41 Appellation isA E70 Thing!! In order to solve this ambiguity we should consider E41 Appellation isA Information Object.
B) Then the SIG addresses the issue of subject relationships. Should we have an intermediate class in CIDOC CRM between E28 Conceptual Object and E73 Information Object, so that we could solve the current conflict between the modelling of subject relationships in FRBRER and in CIDOC CRM, which results in an impossibility to model them in FRBRoo?
Stephen Stead makes the following proposal:
Under this view F1 Work has aboutness as well as F2 expression has aboutness. This situation represents a systematic problem of modelling alternative granularity.
We consider E41 Appellation IsA E73 Information Object and we have to rewrite the scope note. Patrick will make a proposal to express the new substance of Appellation and will also look at P139 has alternative form if it is a symmetric property on not by end of August / beginning of September.
We made changes in CRM text property P3 has note. The scope note of P3 was rephrased in the following manner: "This property is a container for all informal descriptions about an object that have not been [instead of: "cannot be"] expressed in terms of CRM constructs."
The group will come back to this issue during the meeting, if there is some time left.
Martin Doerr and Dolores Iorizzo volunteer to draft a short text on this issue.
We need to reorganize the conceptual object level.
The discussion is postponed. Martin Doerr suggested that the SIG evaluate all the consequences of the following structure:
Edinburgh 10/7/2007
E89 Propositional Object
| Subclass of: | E28 Conceptual Object |
| Superclass of: | E73 Information Object E30 Right |
| Scope note: | This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or mental things and that are documented as single units or serve as topic of discourse. This class also comprises items that are "about" something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object. |
| Examples: |
|
| Properties: | P148 has component (is component of) E89 Propositional Object P67 refers to (is referred to by): E1 CRM Entity (P67.1 has type: E55 Type) P129 is about (is subject of): E1 CRM Entity |
P67 refers to (is referred to by)
| Domain: | E89 Propositional Object |
| Range: | E1 CRM Entity |
| Superproperty of: | E31 Document. P70 documents (is documented in): E1 CRM Entity E32 Authority Document. P71 lists (is listed in): E55 Type E89 Propositional Object. P129 is about (is subject of): E1 CRM Entity E36 Visual Item. P138 represents (has representation): E1 CRM Entity |
| Quantification: | many to many (0,n:0,n) |
| Scope note: | This property documents that an E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the E89 Propositional Object. |
| Examples: |
|
| Properties: | P67.1 has type: E55 Type |
P129 is about (is subject of)
| Domain: | E89 Propositional Object |
| Range: | E1 CRM Entity |
| Subproperty: | E89 Propositional Object. P67 refers to (is referred to by): E1 CRM Entity |
| Quantification: | many to many (0,n:0,n) |
| Scope note: |
This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an E1 CRM Entity, in that it describes the primary subject or subjects of an E89 Propositional Object. |
| Examples: |
|
P148 has component (is component of)
| Domain: | E89 Propositional Object |
| Range: | E89 Propositional Object |
| Superproperty of: | |
| Subproperty of: | |
| Quantification: | (0:n,0:n) |
| Scope note: | This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. |
| Examples: | The Italian text of Dante's textual work entitled "Divina Commedia" (E33) P148 has component The Italian text of Dante's textual work entitled "Inferno" (E33) |
E90 Symbolic Object
| Subclass of: | E28 Conceptual Object E72 Legal Object |
| Superclass of: | E73 Information Object E41 Appellation |
| Scope note: |
This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units.
It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string. |
| Examples: |
|
| Properties: | P106 is composed of (forms part of) E90 Symbolic Object |
P106 is composed of (forms part of)
| Domain: | E90 Symbolic Object |
| Range: | E90 Symbolic Object |
| Superproperty of: | |
| Subproperty of: | |
| Quantification: | (0:n,0:n) |
| Scope note: | This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. |
| Examples: |
|
Crete 12 May 2008