Cidoc conceptual Reference Model
Download 2.39 Mb.
|
- Navigate this page:
- Amendments to draft version 5.1.1
- The range of P8 took place on or within (witnessed)
- The name of the property P69 is associated with
- Examples in E28 Conceptual Object
- The scope note of E90 Symbolic Object
- New property for E55 Type about narrower term partitive
- The range of P142 used constituent (was used in)
- Examples have been added to E7 Activity
Proofreading:Page xvi: In the 25th CIDOC SIG meeting and the 18th FRBR-CIDOC CRM Harmonization meeting, at April 30th – May 3rd, 2012, at ICS – FORTH, the CRM-SIG, it is decided to made the following changes for clarification reasons to Disjointness from “Classes are disjoint if they share no common instances in any possible world. There are many examples of disjoint classes in the CRM.” To Classes are disjoint if they share no common instances in any possible world. That implies that it is not possible to instantiate an item using a combination of classes that are mutually disjoint or with subclasses of them (see “multiple instantiation” in section “Terminology”). There are many examples of disjoint classes in the CRM. Page 62: In the first sentence of the scope note of P98 brought into life (was born), the phrase E67Birth became E67 Birth Page 65: In P109 has current or former curator (is current or former curator of), the hyperlink of code P49 has former or current keeper (is former or current keeper of) to the subproperty section has been added. Page 70: In the scope note of P128 carries(is carried by), in the first sentence the E73 Information Object became E90 Symbolic Object. Page 119:The range of P128 carries(is carried by), in the table of the section CRM-Compatible Form, set to E90 Symbolic Object. Page 76: the first paragraph of P147 has been changed from This property associates an instance of E78 Collection or collections with subject of a curation activity following some implicit or explicit curation plan. To This property associates an instance of E87 Curation Activity with the instance of E78 Collection that is subject of that curation activity. Page 136:in P111 added(was added by), P113 removed(was removed by) the form of the tense has been corrected. Page 170:in P88 foresees use of (use forseen by), the form of the tense has been corrected. Amendments to draft version 5.1.1Addition to the monotonicity text in page xviIn 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG, resolving the ISSUE 204, decided to add the following text in the monotonicity section in page xvi. The following text is added: Properties, such as having a part, an owner or a location, may change many times for a single item during its existence. Stating instances of such properties for an item in terms of the CRM only means that these properties existed during some particular time-span. Therefore, one item may have multiple instances of the same property reflecting an aggregation of these instances over the time-span of its existence. If more temporal details are required, the CRM recommends explicitly describing the events of acquiring or losing such property instances, such as by E9 Move etc. By virtue of this principle, the CRM achieves monotonicity with respect to an increase of knowledge about the states of an item at different times, regardless of their temporal order. However, for some of these properties many collection databases describe the “current” state, such as “current location” or “current owner”. Using such a “current” state means, that the database manager is able to verify the respective reality at the latest date of validity of the database. Obviously, this information is non-monotonic, i.e., it requires deletion when the state changes. In order to preserve a reduced monotonicity, these properties have time-neutral superproperties by which respective instances can be reclassified if the validity becomes unknown or no longer holds. Therefore the use of such properties in the CRM is only recommended if they can be maintained consistently. Otherwise, they should be reclassified by their time-neutral superproperties. This holds in particular if data is exported to another repository. The range of P8 took place on or within (witnessed)In 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG, resolving the ISSUE 211, decided to change the range of E4 Period.P8 took place on or within (witnessed) to E18 Physical Thing from E19 Physical Object.The following changes took place: Page xvv: on the property hierarchy table Page 4: Properties section of E4 Period Page 39: Properties definition section on Range field. The name of the property P69 is associated withIn 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG, discussing the ISSUE 214 Decided to change the name of the property P69 is associated with to P69 has association with (is associated with). The following changes took place: Page xxvi: on the property hierarchy table Page 14: On the scope note and properties of E29 Design or Procedure Page 55,56: Name, scope note and examples of P69 The following example has been added to the P69
Examples in E28 Conceptual ObjectIn 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG, decided the example of Maxwell equations in F50 Controlled Access Point to be added to E28 Conceptual Object The scope note of E90 Symbolic ObjectIn 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG, decided to finalize the text of the issue 207. From In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized content model, such.. as the property P3 has note allows for describing this content model…P3.1 has type: E55 Type to specify the encoding.. To In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel) New property for E55 Type about narrower term partitiveIn 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG, decided to close the issue 208. The definition of the property, the scope notes and the example are accepted as they are. P150 defines typical parts of (defines typical wholes for) Domain: E55 Type Range: E55 Type Quantification: many to many (0,n:0,n) Scope note: The property "broaderPartitive" associates an instance of E55 Type "A" with an instance of E55 Type "B", when items of type "A" typically form part of items of type "B", such as "car motors" and "cars". It allows Types to be organised into hierarchies. This is the sense of "broader term partitive (BTP)" as defined in ISO 2788 and "broaderPartitive" in SKOS. Examples: car motors (E55) has broader term cars (E55) The range of P142 used constituent (was used in)In 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG resolving the issue 209 decided to change . the range of E15 Identifier Assignment.P142 used constituent (was used in):E41 Appellation to E90 Symbolic Object and the examples from R47 used constituent (was used in), of FRBRv2.0 draft to be transferred to P142 used constituent (was used in). FROM P142 used constituent (was used in) Domain: E15 Identifier Assignment Range: E41 Appellation Subproperty of: E7 Activity. P16 used specific object (was used for): E70 Thing
Examples:
TO
Domain: E15 Identifier Assignment Range: E90 Symbolic Object Subproperty of: E7 Activity. P16 used specific object (was used for): E70 Thing
Examples:
Examples have been added to E7 ActivityIn 27th CIDOC SIG meeting and the 20th FRBR-CIDOC CRM Harmonization meeting, at 19 November – 22 November, 2012, at Amersfoort, Netherlands, the CRM-SIG resolving the issue 216 decided that the scope note of E7 Activity covers the notion of continuity and added two examples to denote the continuity. These are:
Proofreading: Page xxv: The range of the property P8 has been corrected Directory: docs docs -> Application for acem docs -> Observational Assessment of Teaching Practices Teaching Assessment Initiative Proposal Submitted to The Teachers for a New Era project docs -> Traditional British values docs -> From Warfighters to Crimefighters: The Origins of Domestic Police Militarization docs -> Borzoi Club of America Register of Merit Program I. What is a Register Of Merit docs -> Protecting the rights of the child in the context of migration docs -> United Nations E/C. 12/Esp/5 docs -> 9th May 1950 the schuman declaration docs -> Getting To Outcomes® in Services for Homeless Veterans 10 Steps for Achieving Accountability Download 2.39 Mb. Share with your friends:
|