Dear Vladimir,
You're absolutely right that the procedure could be improved by adequate
IT. If you know of access to suitable S/W, that would be most welcome.
We also appreciate co-development.
Since we provide at FORTH services to CIDOC for free, we are also
limited in the efforts we can put in.
We can coordinate, but not do all jobs. The solution is concentrating
forces with a tight communication and participation, avoiding diverging
activities. I'd regard it as unlucky, if you and other partners
interested could not participate in the next CRM-SIG meeting.
We are aware that the recording of the justifications of decisions could
be improved. We have discussed sound recording. However, writing such
minutes requires considerable time and skills. We would VERY much
appreciate if more partners would contribute to minutes writing. This
is currently our bottle neck.
CRM-SIG has decided to redesign the whole Web-site. When discussing, it
appears that the size of this effort has been underestimated by
partners. As it appears, it will be again we at FORTH that will do the
whole job. We hope that then it will be easier to find things. Just
another team taking over is not practical, because the know-how of the
everyday management is with FORTH. That is bottle-neck number 2.
Probably it would also be good to have an obvious place where we record
modelling principles. I am working on writing up in a
scientific/didactic manner, but this appears also to be a major project.
Simple phrases may be helpful as reference.
For instance:
" ISSUE: "P43 has dimension" should apply to E1 Entity, not E70 Thing "
violates one of the most fundamental principles:
A property should have as domain the most specialized class that is
superclass of all classes for which the property can be applicable (in
the sense of potentiality).
E1 Entity is obviously the most general such class, and hence wrong.
The reason is that assigning properties to higher classes brings with it
the potential that properties should later be restricted to their true
domain in order to avoid problems of interpretation and reasoning.
Such restriction is not backwards compatible. Therefore we require in
CRM-SIG to find a new class in such case.
For reasons of backwards-compatibility, it is even preferable to
restrict the domain further to a class for which the property has fully
be understood. This is one of the major reasons why the CRM is so stable
and grows nearly conflict-free.
We could, for instance, point to such rules in justifications of decisions ?
Best,
Martin
On 3/1/2014 1:17 μμ, Chryssoula Bekiari wrote:
Dear Vladimir
I think the issues you mentioned are under the numbers 156 and 229, and
these issues are on the list.
happy new year
Chryssoula
On 1/1/2014 5:55 μμ, Vladimir Alexiev wrote:
I hope you all had a Merry Christmas and a very happy New Year!
You may find the minutes from the last CIDOC-CRM meeting in
http://www.cidoc-crm.org/special_interest_meetings.html#MINUTES-2013October21
http://www.cidoc-crm.org/docs/29th-meeting-presentations/RulesForCommunication.docx
This is an excellent document that encourages anyone to raise issues
for electronic voting.
However, I have doubts about the efficiency of issue tracking on this
mailing list and at the issue list:
http://www.cidoc-crm.org/work_progress.php
A good example is this issue raised by me 25m ago and re-raised by
Athina Krisotaki 8m ago:
- Nov 2011: ISSUE: "P43 has dimension" should apply to E1 Entity, not
E70 Thing
- Apr 2013: issue 223
- Apr 2013: issue 223 "P43 has dimension" should apply to E1 Entity,
not E70 Thing
It is still not in the issue list.
Other problems:
- One cannot contribute directly to the discussion on an issue but has
to rely on someone manually carrying information over from the mailing
list.
- The justifications of particular resolutions are not recorded in detail
- When the resolution is taken in a face to face meeting, one cannot
contribute unless physically present (the electronic voting should
alleviate this)
I'll be preparing a proposal for a COST Action to support the work of
the CRM SIG
with funding for meetings, workshops, summer schools, individual
trips, electronic communication.
** So I will appreciate all your thoughts and comments on how this
aspect of the work can be improved.
- I've seen excellent examples of integrated issue tracking at the W3C
work groups. They have regular online chats, and a robot watches all
raised issues and tasks, and enters them into a tracker. Another robot
watches mailing list traffic and cross-links all emails mentioning a
particular issue. Maybe we can get and deploy their software.
- Another option would be a dedicated issue tracker such as Jira, the
one in Google Projects, etc
Kindest regards!
Vladimir
_______________________________________________
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 |
--------------------------------------------------------------
