Cidoc conceptual Reference Model


P167 was at (was place of)



Download 2.67 Mb.
Page68/74
Date09.01.2017
Size2.67 Mb.
#8471
1   ...   64   65   66   67   68   69   70   71   ...   74

P167 was at (was place of)

In 34th CRM-SIG and 27th FRBR-CIDOC CRM group meeting, resolving the issue 234, the label of the property P176 has been changed:


FROM:

P167 was at (was place of)

TO:


P167 at (was place of)

Knowledge Creation Process


In 34th CRM-SIG and 27th FRBR-CIDOC CRM group meeting, resolving the issue 276, an entry about knowledge creation process has been added to Terminology



Knowledge Creation Process

All knowledge in an information system is introduced into that system by some human agent either directly or indirectly. Despite this fact, many, if not most, statements within such a system will lack specific attribution of authority. In the domain of cultural heritage, however, there are clear systems of responsibility for collection documentation and management, ideally specified in institutional policy and protocol documents. Thus, it is reasonable to hold that such not explicitly attributed statements represent the official view of the administrating institution of that system.

This is to not say that an information system represents at any particular moment a completed phase of knowledge that the institution promotes. Rather, it is to say that is represents a managed set of data that, at any state of elaboration, adheres to and strives to some explicit code of standards. So long as the information is under active management it remains continuously open to revision and improvement as further research reveals further understanding surrounding the objects of concern.

A distinct exception to this rule is represented by information in the data set that carries with it an explicit statement of responsibility.

In CRM such statements of responsibility are expressed though knowledge creation events such as E13 Attribute Assignment with subclasses. Any information in a CRM model that is based on an explicit creation event for that piece of information is attributed to be the responsibility of the actor identified as causal in that event (provided the creator’s identity has been made explicit for that event). For any information connected to knowledge creation events that do not explicitly reference their creator, as well as any information not connected to creation events, the responsibility falls back to the institution responsible for the database/knowledge graph. That means that for information only expressed through shortcuts such as ‘P2 has type’, where no knowledge creation event has been explicitly specified, the originating creation event cannot be deduced and the responsibility for the information can never be any other body than the institution responsible for the whole information system.

In the case of an institution taking over stewardship of a database transferred into their custody, two relations of responsibility for the knowledge therein can be envisioned. If the institution accepts the dataset and undertakes to maintain and update it, then they take on responsibility for that information and become the default authority behind its statements as described above. If the institution accepts the data set and stores it without change as a closed resource, then it can considered that the default authority remains the original steward.




Proofreading:



Page 78: The statement in First Order Logic is corrected.

Page 92: the class number in the example of P138 represents (has representation) is corrected.

Amendments 6.2.2

E10 Transfer of Custody


In 34th CRM-SIG and 27th FRBR-CIDOC CRM group meeting, resolving the issue 276 the scope note of E10 has been changed. This change was left out of the amendments of the affected the version 6.2.1. while the scope note of E10 has been changed in the text of version 6.2.1.

E78 Collection


In the 35th joined meeting of the CIDOC CRM SIG and 28th FRBR - CIDOC CRM Harmonization meeting, resolving the issue 270 the name and the scope note of the class E78 has been changed
FROM
E78 Collection
Scope note: This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan.
Items may be added or removed from an E78 Collection in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Collection often referred to with the name of the E78 Collection (e.g. “The Wallace Collection decided…”).
Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Collection. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.

TO:
E78 Curated Holding

Scope note: This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan. Typical instances of curated holdings are museum collections, archives, library holdings and digital libraries. A digital library is regarded as an instance of E18 Physical Thing because it requires keeping physical carriers of the electronic content.


Items may be added or removed from an E78 Curated Holding in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Curated Holding often referred to with the name of the E78 Curated Holding (e.g. “The Wallace Collection decided…”).

Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Curated Holding. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.





Download 2.67 Mb.

Share with your friends:
1   ...   64   65   66   67   68   69   70   71   ...   74




The database is protected by copyright ©ininet.org 2024
send message

    Main page