Issue 159: Constructing appellations

Starting Date: 
2007-07-10
Working Group: 
1
Status: 
Done
Closing Date: 
2008-05-12
Background: 

In this session Patrick made a presentation about the model developed in FRBRoo for constructing normalised appellations. We discussed about to put F33 Identifier Assignment in CRM and to generalize the E42 Object Identifier to be E42 Identifier.

Stephen remarked that Identifier is a good construct but it should be represented by an assigning activity which says for whom it is preferred. An argument was that the identifier assignment has type.
The group made the proposal for collapsing E15 to F33 and E42 to F14.
Should Identifier Rules be regarded as a specialisation of E29 Design or Procedure?

Outcome: 

The SIG accepted the model developed in FRBRoo for constructing normalised appellations and at the price of only minimal changes in CIDOC CRM we decided (1) no specific class is defined for Identifier Rule (this is covered by E29 Design or Procedure), (2)  E42 Object Identifier is redefined as E42 Identifier (not just for physical objects), (3) E15 Identifier Assignment is declared as equivalent to F33 Identifier Assignment in FRBRoo. We had to revise the scope notes.
Martin should make a proposal  up to the end of this meeting

The revised scope  notes follow:

E15 Identifier Assignment

Subclass of: E13 Attribute Assignment
Scope note:

This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.

Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.

The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property.

Examples:
  • replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
  • Assigning the author-uniform title heading “Goethe, Johann Wolfgang von, 1749-1832. Faust. 1. Theil.” for a work (E28)
  • 01 June 2001 Assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)
Properties: P37 assigned (was assigned by): E42 Identifier
P38 deassigned (was deassigned by): E42 Identifier
P142 used constituent (was used in): E41 Appellation

 

E42 Identifier

Subclass of: E41 Appellation
Scope note:  This class comprises codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.
Examples:
  • “MM.GE.195”
  • “13.45.1976”
  • “OXCMS: 1997.4.1”
  • ISSN “0041-5278”
  • ISRC “FIFIN8900116”
  • Shelf mark “Res 8 P 10”
  • “Guillaume de Machaut (1300?-1377)” [a controlled personal name heading that follows the French rules]

Edinburgh 9-11 July 2007

The first and the third example of E15

  • Replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens
  • On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E42,E82) to Guillaume de Machaut (E21)

The scope note of E42

This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.

The first and the second  example of P142 used constituent (was used in)

Examples:

  • On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E15)used constituent “Guillaume, de Machaut” (E82 Actor Appellation)
  • On June 1, 2001 assigning the personal name heading “Guillaume, de Machaut, ca. 1300-1377” (E15)used constituent “ca. 1300-1377” (E49 Time Appellation

Nuremberg 4-7 December 2007

 

Proposal accepted

Heraklion, May 2008