[Crm-sig] Issue 457: harmonization of graphical documentation about CRM
Dear all, Before the meeting to be held next week, I am sharing with you a first version of the CIDOC CRM Diagramming Guidelines <https://docs.google.com/document/d/1uKTzopAEvu6b1d_UtExrQBpeIkt4kbNK8s-bsM-Nwt4/edit>. During the meeting, we will have the chance to review the broad outlines of this document, but also to concretely experiment with what an implementation of these guidelines could look like in a tool like diagrams.net/draw.io. Looking forward to seeing you next week, Philippe -- *Philippe Michon* (he/il – https://name.pn/philippe-michon) Acting Manager Canadian Heritage Information Network (CHIN) Department of Canadian Heritage, Government of Canada 1030 Innes Road, Ottawa (Ontario) K1B 4S7 philippe.mic...@pch.gc.ca illipm...@gmail.com Gestionnaire intérimaire Réseau canadien d'information sur le patrimoine (RCIP) Ministère du Patrimoine canadien, Gouvernement du Canada 1030 chemin Innes, Ottawa (Ontario), K1B 4S7 philippe.mic...@pch.gc.ca illipm...@gmail.com ___ Crm-sig mailing list Crm-sig@ics.forth.gr http://lists.ics.forth.gr/mailman/listinfo/crm-sig
Re: [Crm-sig] New Issue: Common Policy / Method for Implementing the .1 Properties of Base and Extensions in RDF
_has_range" don't have a scope note at all. 7. It is also difficult to easily find all the information about .1 properties. Would it be useful to have a dedicated section for them in the introduction? Best, Philippe Le jeu. 24 mars 2022 à 08:51, Martin Doerr via Crm-sig a écrit : > I think this is a good idea! > > Martin > > On 3/24/2022 1:23 PM, Pavlos Fafalios via Crm-sig wrote: > > Dear George, all, > > The new version of PC classes file (for CRMbase version 7.1.1) has been > already produced (as discussed in the last meeting) and will be soon > available through the crm website (see issue 567 > <https://cidoc-crm.org/Issue/ID-567-module-for-pc-properties>). > > Thinking of it again: > Since the namespace for the PC classes is the same with that of the base > classes/properties, why not including them directly within the base RDFS? > (i.e. providing at the end a single rdfs file that also includes the PCs). > Properties of properties are part of the official documentation (of the > base model, or of an extension), so why not including the corresponding PC > classes in the same RDFS file instead of providing and maintaining a second > file? (this applies for both the base model and the extensions) > > This is just a suggestion without knowing any discussions, or decisions > made, when implementing the PC classes for the first time several years ago > (there might be a good reason for having a second file...). > > Best regards, > Pavlos > > On Thu, Mar 24, 2022 at 11:41 AM George Bruseker via Crm-sig < > crm-sig@ics.forth.gr> wrote: > >> Dear all, >> >> Subsequent to another thread I started here I am proposing that there be >> a conversation about having a standard policy and method for creating, >> documenting and making available the .1 properties for base and its >> extensions in the RDF serialization. At present to my knowledge the PC >> classes are only available for CRMBase and relative to version 6.2.1. Other >> extensions however also use .1 constructions and, moreover, CRMbase moves >> forward and its PC classes should hypothetically move with it. Therefore, I >> propose we discuss, create and implement a common policy for creating this >> rdf derivative to support rdf implementations that adopt the .1 >> constructions. >> >> Best, >> >> George >> ___ >> Crm-sig mailing list >> Crm-sig@ics.forth.gr >> http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > > > -- > Pavlos Fafalios > > Postdoctoral researcher (Marie Curie IF - Project ReKnow > <https://reknow.ics.forth.gr/>) > Centre for Cultural Informatics & Information Systems Laboratory > Institute of Computer Science - FORTH > > and > > Visiting Lecturer > Department of Management Science & Technology > Hellenic Mediterranean University > > Address: N. Plastira 100, Vassilika Vouton, 70013 Heraklion, Greece > Email: fafal...@ics.forth.gr > Tel: +30-2810-391619 > Web: http://users.ics.forth.gr/~fafalios/ > > > ___ > Crm-sig mailing > listCrm-sig@ics.forth.grhttp://lists.ics.forth.gr/mailman/listinfo/crm-sig > > > > -- > > Dr. Martin Doerr > > Honorary Head of the > 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 > > Vox:+30(2810)391625 > Email: mar...@ics.forth.gr > Web-site: http://www.ics.forth.gr/isl > > ___ > Crm-sig mailing list > Crm-sig@ics.forth.gr > http://lists.ics.forth.gr/mailman/listinfo/crm-sig > -- *Philippe Michon* (he/il – https://name.pn/philippe-michon) Semantic Web Analyst Canadian Heritage Information Network (CHIN) Department of Canadian Heritage, Government of Canada 1030 Innes Road, Ottawa (Ontario) K1B 4S7 philippe.mic...@canada.ca illipm...@gmail.com Tel: 613-998-3721 ext. 225 or 1-800-520-2446 Analyste en web sémantique Réseau canadien d'information sur le patrimoine (RCIP) Ministère du Patrimoine canadien, Gouvernement du Canada 1030 chemin Innes, Ottawa (Ontario), K1B 4S7 philippe.mic...@canada.ca illipm...@gmail.com Tél. : 613-998-3721 poste 225 ou 1-800-520-2446 ___ Crm-sig mailing list Crm-sig@ics.forth.gr http://lists.ics.forth.gr/mailman/listinfo/crm-sig
Re: [Crm-sig] Issue 528 HW: Where to put the translations
Dear all, George's email reminds me that I did not indicate here what I was going to present quickly tomorrow. In my progress report, I will talk about the work done on the CIDOC CRM Translation Best Practices Guide <https://docs.google.com/document/d/1H6e-kJLWWYvAfJfHzyHQQruWRHlSigrFCDdJxFXHgeM/edit> and the plan/outline we have prepared for the Governance Guidelines <https://docs.google.com/document/d/1_tbN7RadpmxO9CzfD5CN4AcJWZb47Um2jCBY7r0VL5w/edit> . In addition to George's presentation, Martin will present the work done on the interchange format/protocol. I hope time will allow us to reflect together on some of the questions we have. Here's the list: 1. Do you have any other ideas for the order in which we could translate CIDOC CRM? 2. Do you have any ideas for materials that we could reuse to create an introduction for translators? 3. Do you have any ideas or questions that we should include in our governance guidelines? 4. If the SIG website is updated to better present translation initiatives, what would you like to find there? 5. Do you think it would be beneficial to have a working group that would allow translation initiatives to identify common issues? 6. Are you interested in helping us in drafting the governance guidelines? See you tomorrow, Philippe Le jeu. 10 févr. 2022 à 06:05, George Bruseker via Crm-sig < crm-sig@ics.forth.gr> a écrit : > Dear all, > > A sub aspect of the issue that Philippe will introduce around translations > is 'where to put the translations' on the website. I was tasked with doing > this some SIGs ago. The HW has been there for a while. Time permitting, we > can look at it! > > > https://docs.google.com/document/d/1BiGrX_pieVCCwlNf-JQweHkwTp57mfY58SIPxBvwkhw/edit?usp=sharing > > Best, > > George > > > ___ > Crm-sig mailing list > Crm-sig@ics.forth.gr > http://lists.ics.forth.gr/mailman/listinfo/crm-sig > -- *Philippe Michon* Consultant en informatique appliquée à l'histoire 450-513-2313 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
Re: [Crm-sig] New Issue: Non-human Actors
, trees, and other >> >> biological actors >> >> >> >> Collective Biological Agent: subclass of Biological Agent and >> >> Collective Agent: used for flocks, forests and other group >> >> biological actors (unlike human groups, such groups are inherently >> >> corporeal) >> >> >> >> And at that point we might consider renaming our existing classes to >> >> 'human' xxx >> >> >> >> So >> >> >> >> E39 Human Agent: subclass of agent, no real change in intension, the >> >> kind of entity that can take action for which legal responsibility >> >> can be attributed within human cultures societies >> >> >> >> E21 Human Person: no real change in intension but its superclass >> >> becomes individual biological agent and human agent (ie an animal >> >> that can be held legallly responsible for its actions) >> >> >> >> E74 Group no real change in intension, but it gains a super class >> >> Collective Agent so it can be queried together with other agent >> >> groups. >> >> >> >> This analysis does not get into the properties which are, of course, >> >> fundamental but sketches a possible path for creating the structure >> >> necessary to create this extension of scope in such a way that it >> >> would respect the principle of monotonicity in revising the model >> >> while allowing the growth of the model to handle the many use cases >> >> of documented animal agency that fall within CH institution's >> >> documentary scope. >> >> >> >> Hope this is a good starting point for a constructive discussion! >> >> >> >> Best, >> >> >> >> George >> >> >> >> -- >> >> >> >> Dr. Martin Doerr >> >> >> >> Honorary Head of the >> >> >> >> 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 >> >> >> >> Vox:+30(2810)391625 >> >> Email: mar...@ics.forth.gr >> >> Web-site: http://www.ics.forth.gr/isl [1] >> > >> > -- >> > >> > Rob Sanderson >> > Director for Cultural Heritage Metadata >> > Yale University >> > >> > -- >> > >> > Dr. Martin Doerr >> > >> > Honorary Head of the >> > >> > 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 >> > >> > Vox:+30(2810)391625 >> > Email: mar...@ics.forth.gr >> > Web-site: http://www.ics.forth.gr/isl [1] >> > ___ >> > Crm-sig mailing list >> > Crm-sig@ics.forth.gr >> > http://lists.ics.forth.gr/mailman/listinfo/crm-sig [16] >> > >> > -- >> > >> > Rob Sanderson >> > Director for Cultural Heritage Metadata >> > Yale University >> > >> > Links: >> > -- >> > [1] >> > >> https://can01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ics.forth.gr%2Fisldata=04%7C01%7Cpat.riva%40concordia.ca%7Cc79309f39b794e1f071208d98cfc5da8%7C5569f185d22f4e139850ce5b1abcd2e8%7C0%7C0%7C637695838964034138%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=o0ecAyLDntcn6tU3%2B%2F4DgFq50GBAzGW1291wi9QhdwE%3Dreserved=0 >> > [2] http://concordia.ca >> > [3] >> > >> https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fid.loc.gov%2Fauthorities%2Fnames%2Fnb2015016669.htmldata=04%7C01%7Cpat.riva%40concordia.ca%7Cc79309f39b794e1f071208d98cfc5da8%7C5569f185d22f4e139850ce5b1abcd2e8%7C0%7C0%7C637695838963964170%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=hdNSl4RqY9oAtWoVxSp3xl9fCc21yLNCKsHF8lEspgs%3Dreserved=0 >> > [4] >> > >> https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fid.loc.gov%2Frwo%2Fagents%2Fnb2017006372.
Re: [Crm-sig] HW for Issue 528
Dear all, Next Tuesday, I will have the chance to present to you the progress report of the CIDOC CRM Translation Guidelines Working Group. The presentation will focus on the document called "CIDOC CRM Translation Best Practices Guide <https://docs.google.com/document/d/17oPq4jfMVYnOX693qHQnBg_KOobccjRqj1lRAPWwBaM/edit?usp=sharing>". The committee is always interested in new ideas to improve the document so do not hesitate to write to us if you have any questions or comments. @George, I will be happy to give you some time in my session to present your thoughts about the translation section on the website. :) Best, Philippe Le jeu. 7 oct. 2021 à 06:05, George Bruseker via Crm-sig < crm-sig@ics.forth.gr> a écrit : > Dear all, > > I was charged with HW from issue 528. > > > http://www.cidoc-crm.org/Issue/ID-528-guidelines-and-protocols-for-translating-cidoc-crm > > "HW: GB to determine the most suitable place on the website for the > translations and the translation guidelines to appear under." > > I hereby link my proposal for the SIG's consideration. > > > https://docs.google.com/document/d/1BiGrX_pieVCCwlNf-JQweHkwTp57mfY58SIPxBvwkhw/edit > > Best, > > George > > ___ > Crm-sig mailing list > Crm-sig@ics.forth.gr > http://lists.ics.forth.gr/mailman/listinfo/crm-sig > -- *Philippe Michon* Consultant en informatique appliquée à l'histoire 450-513-2313 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
[Crm-sig] Issue 528: Guidelines and Protocols for Translating CIDOC CRM
Dear all, In anticipation of the SIG meeting, I wanted to inform you of the progress of the work of the CIDOC CRM Translation Guidelines Working Group. First of all, I would like to remind you that our current mandate is to discuss issues related to translation, in particular questions relating to methodology, protocols, and tools. The working group is made up of 13 members who represent at least 8 different languages. I would like to take this moment to thank those who have contributed to the reflection during these last two months. The working group met twice. The first meeting made it possible to present our respective projects in addition to initiating a reflection on the needs that the group should address. The second meeting made it possible to identify more clearly the needs and the documentation that we will have to develop. We have also highlighted certain aspects that go beyond our mandate. Without going into details in this email, we are considering the creation of 5 potential documents: 1. "Guide of CIDOC CRM Best Translating Practices" which will define the different levels of translation, the expertise required, the workflows and recommendations on how to properly develop a style guide. 2. "Governance Guidelines" which will define the licensing options, a translation policy and rules to ensure quality translations. 3. "Comparison and Update Protocol" which will make it possible to easily compare versions, in particular by explaining how changes will be tracked. This document will also include the mechanisms to ensure the improvement of the original version, in particular by the presentation of a clear communication protocol between the SIG and the translation initiatives. 4. "Introduction for translators who are new to CIDOC CRM" which will serve as a practical guide for translators who are less familiar with CIDOC CRM. It is presently contemplated to reuse documents which already exist. 5. "Tools and Interchange Protocols" which will define the technological aspects which will facilitate the exchange of information between the SIG and the translation initiatives. We think in particular the questions of formats, templates, styles, compatibility, updates, bibliography management and tools. As mentioned above, some aspects are outside the scope of our working group and for this reason, we would like to solicit the participation of the SIG with regard to the following aspects: 1. We believe that it is important to give visibility to translation initiatives on the CIDOC CRM website, in particular to be able to quickly identify current initiatives, but also to easily access the documentation that we are going to produce. 2. We would also need your insight into governance, particularly in terms of licensing, the ecosystem the initiatives will be part of, and publication formats. 3. We believe that a comprehensive glossary to cover certain ambiguous terms would be very useful to allow a quality translation. 4. Finally, in order to facilitate the creation of references, direct access to the SIG bibliography on Zotero would be appreciated. In conclusion, the next few months will be devoted to writing this documentation and we invite those wishing to participate in the initiative to contact us. Everything will be presented to you in a more detailed fashion during the SIG meeting; here is the visual support <https://docs.google.com/presentation/d/1HeAbTIbWuvczEPBasZfyFpDNocyYGbgENATJApMuaJM/edit#slide=id.p> that will accompany the presentation if you ever want to consult it in advance. All the best, Philippe -- *Philippe Michon* (he/il – https://name.pn/philippe-michon) Semantic Web Analyst Canadian Heritage Information Network (CHIN) Department of Canadian Heritage, Government of Canada 1030 Innes Road, Ottawa (Ontario) K1B 4S7 philippe.mic...@canada.ca illipm...@gmail.com Tel: 613-998-3721 ext. 225 or 1-800-520-2446 Analyste en web sémantique Réseau canadien d'information sur le patrimoine (RCIP) Ministère du Patrimoine canadien, Gouvernement du Canada 1030 chemin Innes, Ottawa (Ontario), K1B 4S7 philippe.mic...@canada.ca illipm...@gmail.com Tél. : 613-998-3721 poste 225 ou 1-800-520-2446 ___ Crm-sig mailing list Crm-sig@ics.forth.gr http://lists.ics.forth.gr/mailman/listinfo/crm-sig
[Crm-sig] NEW ISSUE: Small Edits Checklist
Dear all, Currently, there is no formal process to identify small errors and/or typos in the CIDOC CRM documentation. If a user notices, for example, a spelling mistake in the text, two options seem possible: - Write an email for an editor to correct the mistake; - Create a dedicated issue. Both options seem not quite adequate: on the one hand, sending an email can discourage those who are not familiar with the structure of the SIG and, on the other hand, the issues should be used for substantive discussions rather than for minor edits. For this reason, should we put in place a tool that would allow anyone to identify minor errors in the CIDOC CRM documentation and which would also be used by editors to follow up? If so, do we think a spreadsheet with a structure similar to this <https://docs.google.com/spreadsheets/d/1RG9fSLev_1Tv6iFUtkFSsjhJdKG-D6_AGc-XrTIzhlU/edit?usp=sharing> would be a good place to start? Note that this document is currently hosted on the Canadian Heritage Information Network's Google Drive, but if everyone agrees this is relevant, it should be hosted by the SIG. In the context of this issue, I would particularly like to obtain your comments on the following questions: 1. Should this be implemented? 2. Does this type of tool/document seem relevant to us? 3. Do we like the current structure or would it be better to make some changes? 4. How should we make this document accessible? Is one link in this issue sufficient? 5. Regardless of where the document is published, would it be relevant to present the objectives and a tutorial on how to use this document in a few paragraphs? 6. Any other questions to discuss? Kind regards, Philippe -- *Philippe Michon* (he/il – https://name.pn/philippe-michon) Semantic Web Analyst Canadian Heritage Information Network (CHIN) Department of Canadian Heritage, Government of Canada 1030 Innes Road, Ottawa (Ontario) K1B 4S7 philippe.mic...@canada.ca illipm...@gmail.com Tel: 613-998-3721 ext. 225 or 1-800-520-2446 Analyste en web sémantique Réseau canadien d'information sur le patrimoine (RCIP) Ministère du Patrimoine canadien, Gouvernement du Canada 1030 chemin Innes, Ottawa (Ontario), K1B 4S7 philippe.mic...@canada.ca illipm...@gmail.com Tél. : 613-998-3721 poste 225 ou 1-800-520-2446 ___ Crm-sig mailing list Crm-sig@ics.forth.gr http://lists.ics.forth.gr/mailman/listinfo/crm-sig
Re: [Crm-sig] CRM translation working group
Dear all, I have just sent an email (in order to plan the first meeting of the working group) to those of you who have expressed an interest in contributing to this issue regarding the translation of CIDOC CRM. I hope I have not forgotten anyone. If you have not received this email and would like to participate in the initiative, please email me and I will be happy to add you to the list. Best regards, Philippe Le sam. 13 mars 2021 à 14:12, Puyu Wang a écrit : > Dear all, > Please also count me into the CRM translation working group. > I am interested in joining. Looking forward to the meeting. > > All best, > > Puyu Wang > > > > -- > *From:* Crm-sig on behalf of Philippe > Michon via Crm-sig > *Sent:* Tuesday, March 9, 2021 6:13 AM > *To:* Sakiko Kawabe > *Cc:* crm-sig > *Subject:* Re: [Crm-sig] CRM translation working group > > > Hi, I am delighted to see so much enthusiasm for the translation working > group following yesterday's discussion. > > Since some people who would like to collaborate on the initiative may not > have been with us yesterday, I would like to quickly introduce the topic > again here. > > The official version 7.1 was released last week and will be the basis for > submission to ISO. As such, the CRM SIG invites the community to contribute > to the creation or update of the translations of the model documentation. > > In order to ensure efficient and quality translations, the CRM SIG > believes that it is important to define clear guidelines and protocols. To > do this, it was decided to set up a committee to reflect on and propose a > first version of this documentation. Yesterday's discussion stems from the > proposal made by George Bruseker ( > http://www.cidoc-crm.org/Issue/ID-58-how-to-organize-the-translation-of-the-model > ). > > It was also proposed that the committee focus, in particular, but not > exclusively, on the following aspects: > > 1. Content Guidelines > > 2. Interoperability Standard and Versioning Tools > > 3. Communication and Validation Protocols > > If you are interested in participating in this initiative, do not hesitate > to express your interest here before March 19th. Then we could schedule a > meeting somewhere in April. > > Thank you all for your interest, Philippe > > > Le mar. 9 mars 2021 à 07:24, Sakiko Kawabe via Crm-sig < > crm-sig@ics.forth.gr> a écrit : > > Hi, we Japanese community also decided to organize some collaborative > works for translation of the newest version of CIDOC CRM into Japanese. > We would start with a simple reading circle where we read the English > version together to understand the concept and terms comprehensively in our > language, while the protocols and guidelines for translation are arranged > in the working group. > > Best, > Sakiko Kawabe > National Museum of Japanese History > > 2021年3月9日(火) 20:38 Franco Niccolucci via Crm-sig : > > Hi George > > you proposed the issue, so you are expected to coordinate the team :) > > Meanwhile, I sent out a circular letter about the CRM translation into > Italian and already got (overnight!) enough qualified volunteers to start > the job. > > So let’s go! > > Franco > > Prof. Franco Niccolucci > Director, VAST-LAB > PIN - U. of Florence > Scientific Coordinator ARIADNEplus > Technology Director 4CH > > Editor-in-Chief > ACM Journal of Computing and Cultural Heritage (JOCCH) > > Piazza Ciardi 25 > 59100 Prato, Italy > > > > Il giorno 9 mar 2021, alle ore 11:23, George Bruseker via Crm-sig < > crm-sig@ics.forth.gr> ha scritto: > > > > I would like to follow from the overall perspective (protocols, > guidelines). > > > > > > > > On Tue, Mar 9, 2021 at 9:45 AM Massoomeh Niknia via Crm-sig < > crm-sig@ics.forth.gr> wrote: > > Hi, > > > > Please count on me as well for the Persian version. > > > > Kind regards, > > Massoomeh > > > >> On 9. Mar 2021, at 10:30, Дарья Юрьевна Гук via Crm-sig < > crm-sig@ics.forth.gr> wrote: > >> > >> Count me in as well for Russian version. > >> > >> > >> With kind regards, > >> Daria Hookk > >> > >> Senior Researcher of > >> the dept. of archaeology of > >> Eastern Europe and Siberia of > >> the State Hermitage Museum, > >> PhD, ICOMOS member > >> > >> E-mail: ho...@hermitage.ru > >> Skype: daria.hookk > >> > https://hermitage.academia.edu/HookkDaria___ > >> Crm-sig mailing list > >> Crm-si
Re: [Crm-sig] Issue:530 Bias in the CRM
;> > we first understand >> > the issues around bias and privileged positions and >> > then how these may >> > or may not impact the development of the model. >> > >> > We will then be more confident in making a more >> > complete statement is >> > future versions. Issue 530 is scheduled to be >> > discussed at the community >> > session of the forthcoming meeting. >> > >> > Looking forward to it. >> > >> > All the best, >> > >> > Thanasis >> > ___ >> > Crm-sig mailing list >> > Crm-sig@ics.forth.gr <mailto:Crm-sig@ics.forth.gr >> > <mailto:Crm-sig@ics.forth.gr> <mailto:Crm-sig@ics.forth.gr >> > <mailto:Crm-sig@ics.forth.gr>>> >> > http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> >> > >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig>> >> > >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> >> > >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > <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 >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig>> >> > >> > ___ >> > Crm-sig mailing list >> > Crm-sig@ics.forth.gr >> > http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> >> > >> ___ >> Crm-sig mailing list >> Crm-sig@ics.forth.gr >> http://lists.ics.forth.gr/mailman/listinfo/crm-sig >> > ___ > Crm-sig mailing list > Crm-sig@ics.forth.gr > http://lists.ics.forth.gr/mailman/listinfo/crm-sig > > > ___ > Crm-sig mailing list > Crm-sig@ics.forth.gr > http://lists.ics.forth.gr/mailman/listinfo/crm-sig > > -- > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> > *Philippe Michon* > Semantic Web Analyst > Canadian Heritage Information Network > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> > <http://lists.ics.forth.gr/mailman/listinfo/crm-sig> > 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
Re: [Crm-sig] CRM translation working group
学研究センター） > E-Mail： skaw...@rekihaku.ac.jp > 〒285-0017 千葉県佐倉市城内町117 > > 金沢大学大学院 人間社会環境研究科（博士後期課程）人間社会環境学専攻 > 人文学コース／文化資源マネージャー養成プログラム > E-Mail： skawabe＠stu.kanazawa-u.ac.jp > > ◇◇◇ > Sakiko KAWABE > E-Mail： sakikok...@gmail.com >saki...@live.jp > > Project Researcher > National Museum of Japanese History > Inter-University Research Institute Corporation > National Institutes for the Humanities > Phone：+81-43-486-4220 (Meta-Resource Research Center) > E-Mail： skaw...@rekihaku.ac.jp > > Ph.D. candidate > Graduate Program in Cultural Resource Management > Humanity Course > Graduate School of Human and Socio-environmental Studies > Kanazawa University > E-Mail： skawabe＠stu.kanazawa-u.ac.jp > <http://skawabe%40stu.kanazawa-u.ac.jp/> > > > > ___ > 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
Re: [Crm-sig] Propose New Issue: Guidelines and Protocols for Translating CIDOC CRM
gt;> 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
