Dear all, As this issue arises from a discussion between George and us at the Canadian Heritage Information Network (CHIN), I just wanted to confirm that we are greatly interested in this issue.
The main reason is that we must have a French version in order to be able to use CIDOC CRM within our organization. Indeed, we have rules on bilingualism that oblige us to have a quality French equivalent (that meets the quality and maintenance standards of governmental agencies) in some strict time limits of the standards to which we refer. We are contributing to the French translation initiative presented by Anaïs. In addition, for administrative reasons, we are in the process of setting up a specific translation process for the Canadian team. Of course, we will share with you as soon as possible the documents that we will make publicly available to our editors and partners. Here is a list of what we plan to share in the coming year: 1. Google Docs translation templates 2. Protocol to convert Google Doc Templates in Markdown (our goal is to publish on Github Pages) 3. Stylesheet 4. Index of CIDOC CRM entities (translated) 5. Update protocol (e.g. 7.0 to 7.1) 6. Spreadsheet for keeping track of the typos in the English version 7. List of the translation challenges 8. Best practices for translation We hope that our work will serve as a foundation for the development of general recommendations and protocols in order to further democratize CIDOC CRM. We look forward to participating in discussions concerning this issue. Best regards, Philippe Le jeu. 25 févr. 2021 à 12:23, Anaïs Guillem <anais.guil...@gmail.com> a écrit : > Hi CRM-lovers, > I would like to follow up on George's email about the translation. In > October 2019, a group of French archaeologists and CH specialists expressed > an interest to translate the latest version and the future version 7 in > order to disseminate CIRDOC CRM more easily. Now, the project of > translation is international (France, Belgium and Canada) and a > collaborative effort. It is mostly inspired by Wiki contributions and > everything is done in Gitlab with version control. The group meets (via > Zoom) once a month to establish some priorities and discuss the different > issues. > > The project is open to anyone interested in contributing to the > translation in French: you just need a Huma-Num account. > https://gitlab.huma-num.fr/bdavid/doc-fr-cidoc-crm > > The translation files could be used for translations in other languages. > The diagrams are also in the process of translation. The translation issues > are discussed in the Gitlab issues. The how-to is explained in the Wiki > section of the gitlab project. > > It would be very interesting to know if there are currently other > translations projects in other languages to compare the process and > methodology. The git repository could be cloned if another group wants to > translate the ontology in another language. > > Have a nice afternoon, > Cheers > Anais > > > Le jeu. 25 févr. 2021 à 08:23, George Bruseker <george.bruse...@gmail.com> > a écrit : > >> Dear all, >> >> >> With the advent of CIDOC CRM 7.1, a new stable community version (aimed >> for ISO approval) of the CIDOC CRM is established. This is the occasion for >> the broader community wishing to implement the standard on a stable basis >> to invest and engage with a mature ontological specification and text. >> >> A key aspect of this work at the community implementation level is to >> render the standard in various languages so that it can be studied, >> appropriated and applied without linguistic barriers by different >> linguistic and cultural communities around the world. >> >> Towards this end, the task of translation is key and an important >> intellectual process and product of the CIDOC CRM community in its own >> right. >> >> The formulation of open, transparent and regular protocols and processes >> for creating a translation would thus be a crucial groundwork to lay out in >> order to give the appropriate support and weight to the translation efforts >> of the CIDOC CRM semantic data community. >> >> At present, a search of the website (using the website search tools) >> returns only one article regarding translation. It is an issue from 2002 ( >> http://www.cidoc-crm.org/Issue/ID-58-how-to-organize-the-translation-of-the-model) >> on how to organize the translation of the CIDOC CRM. >> >> It would seem then that there is a need to pick up this issue again and >> address its various aspects (especially given the phenomenal growth of the >> CIDOC CRM uptake and the spread of its use to different linguistic >> communities around the world). >> >> It seems prudent therefore to communallly create a formulation of >> guidelines for translation best practice and, separately, open and explicit >> protocols for submission and acceptance of CIDOC CRM translations, to be >> developed and put into action by the community. >> >> The spirit of the guidelines and protocols should be to make a >> transparent space for engaging in this important work and understanding its >> relation to the overall CIDOC CRM community effort. It should aim to >> support existing translation efforts and provide an obvious, open and >> transparent path for additional translation efforts. >> >> Of consideration for inclusion in these guidelines and protocols are the >> following topics: >> >> Protocol for Starting an Official Translation >> >> Who can start an official translation, are there any preconditions? >> >> Protocol for Accepting an Official Translation >> >> What are the criteria for accepting a translation as official? >> >> When do the translated classes and properties pass into the >> serializations? >> >> Is there recognition of the translating group in the serialization (for >> the respective translation element) >> >> Recommended Tools for Supporting Translation >> >> Are there any tools recommended for supporting translation? Any >> recommended methods? >> >> Networks of Support (Community of Translation Projects) >> >> The translation of the CIDOC CRM is the translation of an aimed for >> neutral ontological description of CH data. The translation of the standard >> requires a creative effort to understand and elucidate the conceptual >> objects specified in the ontology. Given the complexity of this effort >> involving philosophical, computer science and cultural heritage specific >> knowledge, the process can be quite challenging. Sharing experiences across >> language translations may help eludicate problems in understanding the >> standard or finding useful philosophic correlate expressions in different >> languages. >> >> Do/can we facilitate a place of exchange on these topics? >> >> Means of Approaching (Ontological Translation Methodology) >> >> Are there better or worse methods for approaching the translation task as >> such? >> >> E.g.: should one translate classes and properties from E1 to En, P1 to Pn >> or should one follow the ontological hierarchy? >> >> What are key terms that might best be approached first in order to >> support the general translation? (E.g.: Space Time Volume?) >> >> Change Management - Version Compare >> >> What is the best way to manage iteration between version and efficient >> translation? (don’t want to retranslate all if possible) >> >> Place of Publication of Translation and Level of Recognition >> >> Where are official translations published? Are they sufficiently visible? >> What is their relation to serializations? >> >> Copyright Issues >> >> Under what copyright should translations be made? >> >> Infrastructure to Support Publication / Promotion of Translations >> >> Is there any? Should there be any? >> >> Template for Translators’ Introduction >> >> The translation work in itself is another intellectual work which >> requires many important choices and requires the introduction of an >> interpretation of meaning and sense. A translator’s introduction then would >> be important in order to convey important decisions and methodological >> choices. Should this be standardized? >> >> >> The above represents a first set of ideas. I propose we have a general >> discussion of this question and see if there is interest and capacity in >> the membership to create such guidelines and protocols. >> >> >> Sincerely, >> >> George >> >> >> _______________________________________________ >> Crm-sig mailing list >> Crm-sig@ics.forth.gr >> http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > > > -- > Anaïs Guillem > Architect-archaeologist > +33 630005089 > _______________________________________________ > Crm-sig mailing list > Crm-sig@ics.forth.gr > http://lists.ics.forth.gr/mailman/listinfo/crm-sig > -- *Philippe Michon* Semantic Web Analyst Canadian Heritage Information Network philippe.mic...@canada.ca illipm...@gmail.com https://name.pn/philippe-michon Analyste en web sémantique Réseau canadien d'information sur le patrimoine philippe.mic...@canada.ca illipm...@gmail.com https://name.pn/philippe-michon
_______________________________________________ Crm-sig mailing list Crm-sig@ics.forth.gr http://lists.ics.forth.gr/mailman/listinfo/crm-sig
