Dear Sebastian,
On 17/5/2015 4:23 μμ, Sebastian Rahtz wrote:
On 17 May 2015, at 13:37, martin <[email protected]> wrote:
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.
how does one get access to the data behind this SIS-TELOS system? is it not a
slight concern that the master is held
in what is effectively a proprietary system?
Please do understand me right. We do all these services for free. None
of this is because we would defend
jobs or technology. Everything we do is a big concern, not a slight
one;-) . Everything better costs again. We need funding for each
migration:-( .
The SIS-TELOS we have distributed to the partners in the past. You can
have it for free. The data are exported in a human and machine readable
syntax (TELOS) like RDFS. It's just a format of the nineties. We have
the transformer to RDFS.
I do not see any means to maintain all this in XML only.
I don’t see why it would be a problem? i mean, what aspects of the master
cannot be represented in XML?
I am not saying it would be easy or convenient to work on necessarily, but it
must be possible
The process, operations are complex and need control. XML is not a
database, it does not have functions. Of course you can put in in XML,
and then use an XML database on top to do the operations.
It does not help you running IsA constraints on classes and properties,
and trigger sequences of changes.
That needs code.
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.
translations are a pain, I agree. for the TEI, we have managed to create a
system for maintaining multi-lingual versions of the reference materials, but
managing the human-readable prose is hard
Our problem is the dependency management. The meaning of CRM constructs
is highly cross-correlated.
The S/W we have designed, seems to solve the problem. We'll see. When we
showed the design, other CRM-SIG members did not even look at the
logical issues :-[ .
….
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.
forgive me, but this looks like a tail wagging a dog :-}
Well, forgive me also, what is the dog: The application S/W or the data
structure ;-) ?
If the search and update operations are simple, a data structure may be
the dog.
Otherwise....;-)
If anybody is seriously interested, we can send the complete
requirements analysis.
Then we can make together checklists what the benefits are.
The CRM maintenance costs us some 25.000 Euros per year. Any serious
simplification
and increase of efficiency is money back in our pocket. We get 7% of our
budget from
the government.
We need to be able to distribute the maintenance process and keep
automatically control of the consistency.
If we may go out of this business some day, nobody will be able to
continue the
process as it stands now.
Cheers,
Martin
Sebastian Rahtz
Chief Data Architect
University of Oxford IT Services
+44 1865 283431
--
--------------------------------------------------------------
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 |
--------------------------------------------------------------
