Changelog

ECRM 140617

Removed property P130_features_are_also_found_on, a malformed twin of P130i_features_are_also_found_on (Thanks to Jamie Norrish).
Moved P128i_is_carried_by as a subproperty from of P130_features_are_also_found_on (see above) to P130i_features_are_also_found_on.

Following object properties and their inverse properties have been defined as transitive: P10_falls_within, P86_falls_within, P88_consists_of, P106_is_composed_of, P114_is_equal_in_time_to, P115_finishes, P116_starts, P117_occurs_during, P120_occurs_before, P127_has_broader_term, P148_has_component.

Fixed missing inverse properties and transitivity of P25, P26 and P27.
Fixed wrong domain and range in P137 and P137i.
Replaced rdf:property with owl:ObjectProperty in line 1794.
Fixed wrong hierarchy of P33i which is now a subproperty of P16i.
Added correct scope note to E50 which had the scope note of E49 by mistake.
Added short documentation of the handling of data values (see changelog 101001) to the website.

Removed all Primitive Values (E59, E60, E61, E62) due to new considerations about the handling of data values in the CRM. All object properties with range E59_Primitve_Value and subclasses have been replaced by datatype properties with any range (detailed documentation in progress).
Added "xml:lang=en" to each comment and label.
Removed unnecesary line breaks in all rdf:comments to enhance readability and automatic processing.
Replaced capital "I" with lower case "i" as suffix for inverse properties.
Removed all functional units (see changelog 100707) as they are not part of the CRM definition.
Removed dots and semicolons from the list items of all rdf:comments. All list items in the "examples" sections are now terminated by a line break only.
Removed changelog from file and added it to the website.

Replaced "." with "_" in Labels of Entities and Properties (e.g. E1_CRM_Entity instead of E1.CRM_Entity) to support turtle.
Added Functional units to rdfs:comments of Entities and Properties according to the graphical representation of version 5.0.1.

All scope notes and examples have been revised and updated according to CIDOC CRM Version 5.0.2 January 2010.
Comments have been reformatted: The scope notes are preceeded by the term "Scope note:". Examples are preceeded by the word "Examples:" and each example will start a new line. Examples are separated by semicolon. A dot terminates the example list.

E41_Appellation is no longer a subclass of E62_String. Now, the preferred way to attach a string to an appellation is to use an extension that provides E41_Appellation with an appropriate datatype property (such as has_XSD_String).
Changes in comments according to amendments and proofreading of CIDOC CRM Version 5.0.2 (pp. 129-133).
Examples changed in the comments have been reformatted for better readability: The word "Examples:" and each following example will start a new line. Examples are separated by semicolon.

P67: scope note updated.
P129: scope note updated.
DataTypeProperties of subclasses of E59_PrimitiveValue have been removed. The pure ECRM will no longer provide any specific means to represent primitive values in a data type format (like XSD till now). Instead, derived ontologies may introduce adequate properties. The ECRM as such is not bound to a specific domain nor underlying implementation (apart from OWL). Therefore the decision in favour of a data type format is not made here. The implementation of the primitive value concepts (E59-E62) as OWL classes is kept, though, to ensure compatibility / expressiveness between subontologies with different data type formats.