Dear All,
The CIDOC CRM master in a logical sense is an SIS-TELOS knowledge base,
product of
ICS-FORTH since 1990, which guarantees the formal logical consistency of
IsA relations of classes and properties. It provides much better views
than Protege.
TELOS can be transformed into RDF/RDFS, except for property-properties.
Otherwise, there were never a consistent version, not talking of a bunch
of extensions.
From this, the Word document is manually maintained and the
Cross-Reference Manual and RDFS is semiautomatically generated.
This is not satisfactory, because we have to create "in sync" the Word
document, an LoD version, the RDFS
versions, OWL versions, Translations and their versions in several
languages, amendment lists and
preferably pointers to issues and e-mail discussions. All this times the
extensions, and now even with an FOL notation. Tomorrow RDFS may be
abandoned for another model. We may like to have 3 RDFS syntax forms.
I do not see any means to maintain all this in XML only. We have tried
in the past TMX for the translations, but it turned out to be complex
and tools were not tuned to that. Multilingual manual writing tools
could do part of the job, but not the logics.
Appears we are first on the world to take formal ontologies seriously,
otherwise, all this should exist on the market. The complexity of
creating user documents seems not to be common knowledge.
Currently, we are about finalizing the alpha version of the new CRM
Website. It became a complex piece of
S/W, with a database in the center managing the logical structure of the
CRM master document and all by-products as tables and fields. We hope
that it will help collaborative work on these products:
Think of updating a Chinese version of a scope note etc.
A TEI encoded version could be an intermediate product. Need to
undestand what we gain. Could be interesting for interfacing with other
apps. Word is very handy to do edit changes during discussions on the
screen. Impossible without a WYSIWYG editor.
We'll present details this week.
Best,
Martin
On 17/5/2015 1:24 μμ, Sebastian Rahtz wrote:
It seems to me self-evident that the CRM should be managed as an
information resource (ie as a structured XML file) instead of a
word-processor presentational document. And if its going to be in XML,
I'd agree that TEI is the obvious format to choose since it is already
used for literate programming, and has a lot of the necessary elements
and semantic constructs, and tools, all in space. It is not
insignificant that the TEI is aligned with the CRM in that its
interested in digital cultural heritage, and that the TEI is
consciously interested in the relationship between its world and the
CRMs.
However, I would like to hear more from Martin or whoever on how the
CRM is authored at the moment. What is the master copy, how is it
managed, what are the tools used and/or needed by the editors? is the
appearance of being a large Word document actually right?
As the author/maintainer of much of the TEI processing software
(including OxGarage which Jim mentioned) and the
chief designer of its current meta language, I can fairly lay claim to
being someone who understands the implications :-}
Nothing would make me happier [1] than helping transform the CRM
master into a beautiful TEI XML file, if there
is sufficient interest.
[1] thats not actually true. I have a long list.
Sebastian Rahtz
Chief Data Architect
University of Oxford IT Services
_______________________________________________
Crm-sig mailing list
[email protected]
http://lists.ics.forth.gr/mailman/listinfo/crm-sig
--
--------------------------------------------------------------
Dr. Martin Doerr | Vox:+30(2810)391625 |
Research Director | 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) |
|
N.Plastira 100, Vassilika Vouton, |
GR70013 Heraklion,Crete,Greece |
|
Web-site: http://www.ics.forth.gr/isl |
--------------------------------------------------------------
