During CIDOC 2005, a CIDOC CRM SIG Meeting took place.
It could be clarified, that CIDOC Conferences will also be open to
non-CIDOC members at a higher fee.
A CRM tutorial was held with 30 participants.
In the following meetings, the following topics were discussed:
A) Progress of the ISO submission:
1. Resolve the naming difference between the ISO version and the version
4.0 on http://cidoc.ics.forth.gr:
E70 Stuff becomes E70 Thing in ISO 21127,
E8 Acquisition Event becomes E8 Acquisition
E11 Modification Event becomes E11 Modification
E12 Production Event becomes E12 Production
E16 Measurement Event becomes E16 Measurement
E65 Creation Event becomes E65 Creation
E66 Formation Event becomes E66 Formation
Decision:
The Naming as in ISO will be introduced into CICOC CRM version 4.1 to
avoid diverging
versions. The reason for the change of naming were difficulties when
trying to make an as literal
as possible translation to French, and other languages as well.
2. The Group asked Nick Crofts, convener of the ISO Working Group for
ISO21127 to apply for
a "core standard status" for the CRM, which means that the standard will
be available free of charge.
3. The Group decided that no perm,anent maintenance procedure from the ISO
side is necessary.
This is good practice for standards describing changing practices.
The standard can be amended at any time, and must be reviewed after five
years.
B) The Group was informed by me (Martin Doerr) about the status of the CRM-FRBR
Harmonization:
A first draft model has been created. Now the scope notes are under
development. The
ambition is to have a first consolidated draft this summer, which is
verbose enough so that
it can be circulated to the wider audience for general discussion. The
activity has the full
support from CIDOC and IFLA. The next FRBR-CRM meeting will take place
July 4-6 in Heraklion.
C) CIDOC and TEI support the collaboration between TEI and CIDOC. Christian
Emil Ore, current chair of CIDOC,
is also a member of TEI and the TEI Working Group on ontologies and member
of CRM-SIG. He will lead the
harmonization of TEI and CIDOC CRM, and communicate the respective progress
and any questions to
be discussed to CRM SIG.
D) There was a discussion about how to apply the CRM:
One has to distinguish a) the data acquisition level, that typically
includes the primary repository,
b) the integration level, which may be achieved by global mediators or data
warehouse style integration
and harvesting, and c) the interpretation level which includes story
telling, teaching, web presentations etc.
At data acquisition level, CRM compatible, rich data formats are recommended,
optimized in form and language to the
specific task. In order to solve the problem of shared notions of identity,
federations of local (i.e. within the primary
repositories) and global authorities are recommended that will maintain once
established equivalences.
At integration level, a minimal global finding aids model for access was
discussed that still preserves CRM semantics:
A "CRM Core" of about 15 fields was drafted (attached). This is not a
proposed documentation structure!
The Group is asked to COMMENT widely on this draft.
E) CCO provides guidelines for selecting, ordering, and formatting data used to
populate catalog records.
(http://www.vraweb.org/CCOweb/). The organisation asks for comments on the
latest draft. The work was presented
at the CIDOC Conference and seems to be highly relevant and thorough. At
some points, there seem to exist
possible conflicts with the CIDOC CRM (the recommendations to document
related places), which will be further
investigated by CRM SIG and the Documentation Standards Working Group. The
idea is that CIDOC expresses a
constructive criticism as soon as possible, which will be elaborated by the
relevant CIDOC Working Groups.
All comments welcome.
F) The next full CRM Workshop is envisaged winter, early 2006. There will be a
local CRM workshop in Sweden in
October/November 2005, and another FRBR-CRM Meeting in 2005 still to be
announced.
Best,
Martin
--
--------------------------------------------------------------
Dr. Martin Doerr | Vox:+30(2810)391625 |
Principle Researcher | Fax:+30(2810)391638 |
| Email: [email protected] |
|
Center for Cultural Informatics |
Information Systems Laboratory |
Institute of Computer Science |
Foundation for Research and Technology - Hellas (FORTH) |
|
Vassilika Vouton,P.O.Box1385,GR71110 Heraklion,Crete,Greece |
|
Web-site: http://www.ics.forth.gr/isl |
--------------------------------------------------------------
<?xml version='1.0' encoding='UTF-8' ?>
<!--Generated by Turbo XML 2.3.1.100.-->
<!---->
<!--#DOCUMENTATION:Represents the described CRM Entity. Corresponds to Dublin
Core resource.-->
<!ELEMENT CRM_Core (Category+ , Classification* , Identification+ ,
Description? , Event* , Relation*)>
<!--#DOCUMENTATION:One of the CIDOC CRM Classes, or a mapping to/from DCMI Type
Vocabulary. General term to characterize the nature of the described item.
Compatibility: DC.Type, CIDOC CRM class system.
-->
<!ELEMENT Category (#PCDATA)>
<!--#DOCUMENTATION:Any category classifying the described item. Preferrably
from controlled vocabularies.
Compatibility: CIDOC CRM P2 has type. E55 Type. Includes: DC.Format, DC.Language
-->
<!ELEMENT Classification (#PCDATA)>
<!--#DOCUMENTATION:Any name or identifier used for the particular item
described.
Compatibility: DC.Title and DC.Identifier. CIDOC CRM P1 is identified by: E41
Appellation
-->
<!ELEMENT Identification (#PCDATA)>
<!--#DOCUMENTATION:An account of the nature or content of the described item.
Compatibility: DC.Description, CIDOC CRM P3 has note: E62 String
-->
<!ELEMENT Description (#PCDATA)>
<!--#DOCUMENTATION:Any Event the described item was present at. (In
generalization any period the object existed in ?)
Compatibility: CIDOC CRM E5 Event
Allows for expressing DC.Creator, DC.Publisher, DC.Contributor, DC.Date,
DC.Coverage
-->
<!ELEMENT Event (Role_in_Event* , Event_Type* , Participant* ,
Participant_Type* , Stuff_Present* , Stuff_Present_Type* , Date? , Place?)>
<!--#DOCUMENTATION:Role of the described Item in the Event:
Compatibility: Any subproperty of CIDOC CRM P12B was present at.
Allows for connecting DC.Creator, DC.Contributor, DC.Publisher, DC.Coverage
DC.Date.
-->
<!ELEMENT Role_in_Event (#PCDATA)>
<!--#DOCUMENTATION:Classification of the Event, e.g. Publication, Production,
Creation, Finding, Use)
Compatibility: subclasses of CIDOC CRM E5 Event, and compatible E55 Type
-->
<!ELEMENT Event_Type (#PCDATA)>
<!--#DOCUMENTATION:Any Actor participating or being present in the Event.
Compatibility: DC.Creator,DC.Publisher,DC.Contributor, DC.Relation if an Agent
is referred.
CIDOC CRM P12B was present at: E39 Actor
-->
<!ELEMENT Participant (#PCDATA)>
<!--#DOCUMENTATION:Any kind of Actor participating or being present in the
Event. This expresses incomplete knowledge.
Compatibility: CIDOC CRM P12B was present at: E39 Actor. P2 has type: E55 Type
-->
<!ELEMENT Participant_Type (#PCDATA)>
<!--#DOCUMENTATION:Any Stuff being present in the Event.
Compatibility: DC.Relation
CIDOC CRM P12B was present at: E70 Stuff
-->
<!ELEMENT Stuff_Present (#PCDATA)>
<!--#DOCUMENTATION:Any kind of Stuff being present in the Event.
Compatibility: DC.Relation
CIDOC CRM P12B was present at: E70 Stuff
-->
<!ELEMENT Stuff_Present_Type (#PCDATA)>
<!--#DOCUMENTATION:A time date range constraining the event related to the
described item.
Compatibility: CIDOC CRM P4 has time-span:E52 Time-Span.P82 at some time
within: E61 Time Primitive.
Includes: DC.Date, DC.Coverage depending on the role of the item in the Event
(Role_in_Event)
-->
<!ELEMENT Date (#PCDATA)>
<!--#DOCUMENTATION:A time date range constraining the event related to the
described item.
Compatibility: CIDOC CRM P7 took place at E53 Place.
Includes: DC.Coverage depending on the role of the item in the Event
(Role_in_Event)
-->
<!ELEMENT Place (#PCDATA)>
<!--#DOCUMENTATION:Any not event-mediated relation. Restricted to: part of,
reference, similarity for which causal events are not established.
Compatibility: subset of DC.Relation
-->
<!ELEMENT Relation (To+ , Relation_Type)>
<!ELEMENT To (#PCDATA)>
<!ELEMENT Relation_Type (has_part , part_of , refers_to , referred_to_by ,
shows_features_of)>
<!ELEMENT refers_to EMPTY>
<!ELEMENT referred_to_by EMPTY>
<!ELEMENT part_of EMPTY>
<!ELEMENT has_part EMPTY>
<!ELEMENT shows_features_of EMPTY>
