Ids proposal - sometime they come back... again!

[monica.palmirani <monica.palmirani@unibo.it>]

Dear colleagues,

a new proposal concerning the ids, coming from Veronique, was presented and discussed in the last unofficial TC on March 21.
See the proposal in attachment.

The proposal aims to cope with the problem of the synchronization among different linguistic versions of the same work document.

The idea proposed is to use originalId in several different manners according to the different situations:
1) <point currentId="art_6__par_2__list_1__pnt_στ"
originalId="art_6__par_2__list_1__pnt_f">
In case there is a master language version (in this case the English). We use originalId for recording the Id of the master language version.

2) <point currentId="art_6__par_2__list_1__pnt_στ" originalId="2013-619191">
In case there isn't a master language version, we use originalId for recording a meaningless and opaque id.

3) <point currentId="art_6__par_2__list_1__pnt_ε"
originalId="art_6__par_2__list_1__pnt_f">
This is the case of renumbering in monolingual document. We use originalId in a third manner for recording the original position before the renumbering.

4) <point currentId="art_6__par_2__list_1__pnt_ε"
originalId="2013-619191">
This is the case of renumbering in Greek document. We use originalId in a fourth manner for recording the original position before the renumbering using opaque id.

We have other several cases where originalId assumes different semantics with different meanings.

Three considerations and one proposal:

a) it is not good to have originalId with different purposes and different semantics, otherwise we need in the metadata block some more elements that say us in which semantic we are (e.g. FRBRTranslation or FRBRlanguage);
b) it is not good to introduce opaque id in oridinalId, mixed with different semantic naming convention, because it breaks interoperability among different institutions that are adopting different methodologies. Moreover the originalId in opaque format produces a new problem: naming convention for new provisions inserted (e.g. between 2013-619191 and 2013-619192, I need to insert new art_6__par_2__list_1__pnt_e1, how I call the new originalId?  2013-619191-1?)
c) the work level id is nice idea, but we have also the scenario where I need to markup the third version, from the scratch, without knows nothing about the first original XML version because I have only PDF in my hand (e.g. very old act);
d) mark-up a renumbering modifications about a provision (e.g. third unnumbered paragraph) and linguistic versions mapping (e.g. with different numbering order and odd structure not corresponding) are both legal intellectual activities, so both of them are subjective interpretation and not objective mark-up.

Proposal:

1) to use originalId with semantic naming convention and to point out to a conventional language id (e.g. France, English)
2) to use  FRBRTranslation attribute "pivot" for expressing in which language we have the master copy
3) to add new attribute to FRBRTranslation "mapper" for expressing in which language we have assumed the mapping (in any case we need a new meta something for tracking the different method used in originalId).
4) to use renumbering metadata in <textMod> block for tracking the renumbering sequences over time, instead of inside of <temporalData> in order to have a unique synchronized block where to write and to read information about the renumbering.

With this proposal the cases appear as follow:
1) <point currentId="art_6__par_2__list_1__pnt_στ"
originalId="art_6__par_2__list_1__pnt_f">
the same but with in FRBRTranslation pivot="eng"

2) <point currentId="art_6__par_2__list_1__pnt_στ"
originalId="art_6__par_2__list_1__pnt_f">
the same but with in FRBRTranslation mapper="eng"

3) <point currentId="art_6__par_2__list_1__pnt_ε"
originalId="art_6__par_2__list_1__pnt_f">
renumbering in monolingual version with renumbering meta data in <textMod>

4)<point currentId="art_6__par_2__list_1__pnt_ε"
originalId="art_6__par_2__list_1__pnt_f">
renumbering in multiple language versions with renumbering meta data in <textMod> and with FRBRTranslation mapper="eng" or FRBRTranslation pivot="eng", depending to the case.

I hope this find well most of you. See you in the TC meeting at 28 March 1.30 EDT.

Good night!
Monica

-- 
===================================
Associate professor of Legal Informatics 
School of Law
Alma Mater Studiorum Università di Bologna 
C.I.R.S.F.I.D. http://www.cirsfid.unibo.it/ 
Palazzo Dal Monte Gaudenzi - Via Galliera, 3 
I - 40121 BOLOGNA (ITALY) 
Tel +39 051 277217 
Fax +39 051 260782 
E-mail  monica.palmirani@unibo.it 
====================================

Attachment: currentId-originalId-v1.pdf
Description: Adobe PDF document

Attachment: currentId-originalId-v1.odt
Description: application/vnd.oasis.opendocument.text