Cidoc conceptual Reference Model



Download 2.67 Mb.
Page53/74
Date09.01.2017
Size2.67 Mb.
#8471
1   ...   49   50   51   52   53   54   55   56   ...   74

Proofreading:


Page xi: The last paragraph of the terminology of Subproperty has been changed

from: In Some object-oriented languages, such as C++, have no equivalent to the specialization of properties

to: Some object-oriented programming languages, such as C++, do not contain constructs that allow for the expression of the specialization of properties as sub-properties

This is related to ISSUE 174.



Page xii: The last sentence of the terminology of shortcut has been changed

from: The CRM allows shortcuts as cases of less detailed knowledge, while preserving in its schema the relationship to the full information.

to: The CRM declares shortcuts explicitly as single properties in order to allow the user to describe cases in which he has less detailed knowledge than the full data path would need to be described. For each shortcut, the CRM contains in its schema the properties of the full data path explaining the shortcut

This is related to ISSUE 174.



Page xiii: In the paragraph of property quantifiers, the first sentence have been changed

from: “We use the term property quantifiers for the declaration of the allowed number of instances of a certain property that an instance of its range or domain may have.”

to: “We use the term "property quantifiers" for the declaration of the allowed number of instances of a certain property that can refer to a particular instance of the range class or the domain class of that property”

This is related to ISSUE 179.



Page xiv: The first sentences of the last paragraph of this page have been changed

from: The CRM defines some properties as being necessary for their domain or as being dependent from their range" seems to be wrong.

to: The CRM defines some dependencies between properties and the classes that are their domains or ranges. These can be one or both of the following:

A) the property is necessary for the domain

B) the property is necessary for the range, or, in other words, the range is dependent on the property.

The possible kinds of dependencies are defined in the table above. Note that if a dependent property is not specified for an instance of the respective domain or range, it means that the property exists, but the value on one side of the property is unknown.

This is related to ISSUE 175.

Page xix: The first paragraph in the examples under the figure has been changed

from: “The diagram above shows a partial view of the CRM, representing reasoning about spatial information. Five of the main hierarchy branches are included in this view: E39 Actor, E51 Contact Point, E41 Appellation, E53 Place, and E70 Thing. The relationships between these main classes and their subclasses are shown as arrows. Properties between classes are shown as green rectangles. A ‘shortcut’ property is included in this view: P59 has section (is located on or within) between E53 Place and E18 Physical Thing is a shortcut of the path through E46 Section Definition. In some cases the order of priority for property names has been modified in order to facilitate reading the diagram from left to right.”

to: “The diagram above shows a partial view of the CRM, representing reasoning about spatial information. Five of the main hierarchy branches are included in this view: E39 Actor, E51 Contact Point, E41 Appellation, E53 Place and E70 Thing. All classes are shown as blue-white rectangles. Properties are shown as single arrows. In some cases the order of priority for property names has been reversed in order to facilitate reading the diagram from left to right. Double arrows indicate IsA relations between classes and their subclasses or between properties and their subproperties. 'Shortcuts' are indicated with light grey rectangles and their names are written in italics, such as the P59 has section (is located on or within) between E53 Place and E18 Physical Thing, which is a shortcut of the path through E46 Section Definition.”

This is related to ISSUE 168



Page xix: The last sentence in the second paragraph has been changed:

from: An instance of E53 Place may consist of or form part of another instance of E53 Place, thereby allowing a hierarchy of physical ‘containers’ to be constructed”

to: An instance of E53 Place may consist of or form part of another instance of E53 Place, thereby allowing a hierarchy of geometric ‘containers’ to be constructed

This is related to ISSUE 186



Page xx: The third paragraph inside the parenthesis the text has been changed

from: “The E2 Temporal Entity class is an abstract class (i.e. it has no instances) that serves to group together all classes with a temporal component, such as instances of E4 Period, E5 Event and E3 Condition State.”

to: “The E2 Temporal Entity class is an abstract class (i.e. it has no direct instances) that serves to group together all classes with a temporal component, such as instances of E4 Period, E5 Event and E3 Condition State.”

This is related to ISSUE 187



Page 43:In the example of P20 the word “alter” changed to “altar”

Amendments to version 5.0.4

Change the text in objectives of the CIDOC CRM


The third paragraph in the chapter entitled “Objectives of the CIDOC CRM” in page i has been changed
From:

“It intends to provide an optimal analysis of the intellectual structure of cultural documentation in logical terms. As such, it is not optimised to implementation-specific storage and processing aspects. Rather, it provides the means to understand the effects of such optimisations to the semantic accessibility of the respective contents”.

To:

It intends to provide a model of the intellectual structure of cultural documentation in logical terms. As such, it is not optimised for implementation-specific storage and processing aspects. Implementations may lead to solutions where elements and links between relevant elements of our conceptualizations are no longer explicit in a database or other structured storage system. For instance the birth event that connects elements such as father, mother, birth date, birth place may not appear in the database, in order to save storage space or response time of the system. The CRM allows us to explain how such apparently disparate entities are intellectually interconnected, and how the ability of the database to answer certain intellectual questions is affected by the omission of such elements and links.


This is related to the ISSUE 176

P109 is subproperty of P49


Resolving the ISSUE 193, the CRM-SIG decided that the property P109 has current or former curator (is current or former curator of) is a Subproperty of P49 has former or current keeper (is former or current keeper of). This decision produced the following changes in the document:

Page xxvi: The CIDOC CRM Property Hierarchy has been updated

Page 50: the Superproperty section of P49 has been updated

Page 65: the Subproperty section of P109 has been updated


P111 is subproperty of P16


Resolving the ISSUE 194, the CRM-SIG decided that P111 added (was added by) isA P16 used specific object. This decision produced the following changes in the document:

Page xxv: The CIDOC CRM Property Hierarchy has been updated

Page 41: the Superproperty section of P16 has been updated

Page 66: the Subproperty section of P111 has been updated




Download 2.67 Mb.

Share with your friends:
1   ...   49   50   51   52   53   54   55   56   ...   74




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

    Main page