eId for elements with duplicate numbers

[Greg Kempe]

Hello all,

We sometimes encounter a work that (erroneously) has multiple sections or paragraphs (which should be numbered uniquely) that have the same number. We must honour the erroneous numbering. Is there a suggestion for how to consistently create eIds for these elements?

example:

<section eId="sec_?">

  <num>4</num>

  ...

</section>

...

<section eId="sec_?">

  <num>4</num>

  ...

</section>

My idea is to do something such as 'sec_4_1' and 'sec_4_2'. That is:

1. follow the normal numbering process to produce 'sec_4'

2. produce a second number obtained by following a process similar to that for un-numbered elements (ie. count the number of preceding elements with the id 'sec_4')

3. separate the 'sec_4' from the second number with '_' so that it doesn't clash with 'sec_41'.

How have others solved this problem?

Thanks,

Greg

--

Greg Kempe

CTO and Co-founder, Laws.Africa

https://laws.africa · gr...@laws.africa · +27 78 246 1116

[Ashok Hariharan]

hi Greg --

 

My idea is to do something such as 'sec_4_1' and 'sec_4_2'. That is:

This kind of thing seems fairly common. I do what you mention above. I couldn't get an answer in cases like this, as to how they resolve referential issues - which section 4 do they mean when another document or the same one cites section 4, it was entirely subjective, so i left it at that (upto the judgement of the person making the reference). 

Ashok

 

1. follow the normal numbering process to produce 'sec_4'

2. produce a second number obtained by following a process similar to that for un-numbered elements (ie. count the number of preceding elements with the id 'sec_4')

3. separate the 'sec_4' from the second number with '_' so that it doesn't clash with 'sec_41'.

How have others solved this problem?

Thanks,

Greg

--

Greg Kempe

CTO and Co-founder, Laws.Africa

https://laws.africa · gr...@laws.africa · +27 78 246 1116

--
You received this message because you are subscribed to the Google Groups "akomantoso-xml" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akomantoso-xm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/akomantoso-xml/CAB%2Bz6DRLvWhWMExYdmOEVRbJ%3DLa07nP8Ab5PRrGMTryOu_6MTw%40mail.gmail.com.

[monica.palmirani]

Dear Greg,

we have the same problem with the multi-versioning XML document where two versions of the same section 4 are annotated in the same physical XML file.

In this case I use sec_4-e1 where e1 is the eventRef annotated in

<lifecycle>  

    <eventRef eId="e1" date="1997-08-29" source="#ro_1" type="generation"/>

</lifecycle>  

In your case I am ok with your solution if you use "sec_4-1" because the "_" symbol is used for the normal annotation of the hierarchy.

Cheers,
Monica

To view this discussion on the web visit https://groups.google.com/d/msgid/akomantoso-xml/CAMxPVW57dugdrr0On%2B-o0Gjm1SXgTUguiqsY9HjosXGRXnPKGw%40mail.gmail.com.

-- 
===========================================
Full professor of Legal Informatics 
School of Law 
Coordinator of MSCA-ITN EJD LAST-JD-RIoE
Scientific Director of Legal Blockchain Lab
Director of the Summer School LEX
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.p...@unibo.it

[Grant Vergottini]

This problem occurs frequently for me. It's not always erroneous, it's often deliberate. In some cases it's a new provision with a future operative date that will replace a provision that is to be repealed on the same date. Rather than trying to force a unique @eId, I allow the duplicate @eId and ensure that my code knows that duplicates may exist and applies disambiguation rules when it occurs. For example, in some jurisdictions (California and Oregon) I've seen language that reads Section 11 (as amended by 2020 Chap 10, sec 12). I carry that disembiguation language through.

--
You received this message because you are subscribed to the Google Groups "akomantoso-xml" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akomantoso-xm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/akomantoso-xml/CAB%2Bz6DRLvWhWMExYdmOEVRbJ%3DLa07nP8Ab5PRrGMTryOu_6MTw%40mail.gmail.com.

--

____________________________________________________________________
  Grant Vergottini
  CEO & Founder, Xcential
  email: grant.ve...@xcential.com
  phone: 858.361.6738