I am glad I asked. :-)
I agree with Sebastian.
What I meant was - don't you consider the requirements first before
implementing the solution - a key principle of the CIDOC CRM an any other
project that might utilise a technology.
In other words the usual approach is to understand the process and requirements
first (and that is not just the requirements and processes of CRM SIG members)
and then choose the appropriate implementation. Not choose the technical
implementation first and then think about the requirements and user needs
afterwards.
Requirement 1. We need to structure the document to make it easier to manage
and maintain?Requirement 2. We need interchange with other TEI documents?
Requirement 3. We need accessible interfaces for non-technologists for find CRM
entities and relationships and also useful patterns of entities and
relationships ?Requirement 4....etc, etc
D
On Sunday, 17 May 2015, 11:24, Sebastian Rahtz
<[email protected]> wrote:
#yiv1256237994 #yiv1256237994 _filtered #yiv1256237994
{font-family:Wingdings;} _filtered #yiv1256237994 {} _filtered #yiv1256237994
{font-family:Calibri;} _filtered #yiv1256237994
{font-family:Consolas;}#yiv1256237994 p.yiv1256237994MsoNormal, #yiv1256237994
li.yiv1256237994MsoNormal, #yiv1256237994 div.yiv1256237994MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;color:black;}#yiv1256237994
a:link, #yiv1256237994 span.yiv1256237994MsoHyperlink
{color:blue;text-decoration:underline;}#yiv1256237994 a:visited, #yiv1256237994
span.yiv1256237994MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv1256237994 pre
{margin:0in;margin-bottom:.0001pt;font-size:10.0pt;color:black;}#yiv1256237994
p.yiv1256237994MsoListParagraph, #yiv1256237994
li.yiv1256237994MsoListParagraph, #yiv1256237994
div.yiv1256237994MsoListParagraph
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;color:black;}#yiv1256237994
span.yiv1256237994HTMLPreformattedChar
{font-family:Consolas;color:black;}#yiv1256237994
span.yiv1256237994EmailStyle20 {color:#1F497D;}#yiv1256237994
.yiv1256237994MsoChpDefault {font-size:10.0pt;} _filtered #yiv1256237994
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv1256237994 ol
{margin-bottom:0in;}#yiv1256237994 ul {margin-bottom:0in;}#yiv1256237994 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 thechief 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 thereis sufficient interest.
[1] thats not actually true. I have a long list.
Sebastian Rahtz Chief Data ArchitectUniversity of Oxford IT Services
_______________________________________________
Crm-sig mailing list
[email protected]
http://lists.ics.forth.gr/mailman/listinfo/crm-sig
