Dear Mark, wow, this is though. Values for element FRBRcountry have three important constraints, and I hope we can find a way to satisfy all three at the same time: 1) Values must be taken from the ISO 3166 (alpha-2) country codes, when existing (which is difficult in and by itself, as ISO 3166 only maps countries that existed from 1974 onward, and if we have a piece of legislation still enacted but coming from a country that stopped existing before 1974, we have problems). 2) Values must be short enough so as to be re-usable in the Work URIs as their first fragment 3) They must, you know, identify the country and/or jurisdiction of the document. ISO 3166 is by no means complete. It only lists countries existing in 1974 and onward (so when we'll be dealing with past countries, we will have to invent something). ISO 3166-2 (
http://en.wikipedia.org/wiki/ISO_3166-2 ) has most sub-country jurisdictions (US states, Italian regions and provinces, German Ländern, etc.). For UK (
http://en.wikipedia.org/wiki/ISO_3166-2:GB ), we have codes the four main countries (actually, two separate codes for Welsh, in English and Welsh), plus "England: 27 two-tier counties, 32 London boroughs, 36 metropolitan districts, 55 unitary authorities, 1 city corporation. Northern Ireland: 26 districts, Scotland: 32 council areas, Wales: 22 unitary authorities". We also have codes for England and Wales, Great Britain and United Kingdom (the difference between the latter two somehow escapes me, but anyhow). To summarize, my opinion is this: 1) if we have an appropriate code in ISO 3166-1 or ISO 3166-2, we should use it. 2) If we do not have an appropriate code, we should invent one with a special syntax 3) If we need multiple codes, currently the standard does not allow multiple FRBRCountry. If the need really exist, we should modify the standard. Hope this clarifies. Ciao Fabio -- On 14/nov/2012, at 15.13, Jones, Mark (LNG-LON) wrote: > Hi guys, > > Following on from this earlier discussion around the usage of the FRBRcountry element in terms of its use for non-country jurisdictions (e.g. California), as I understand it this is to be used to indicate "the country or jurisdiction to be used in the work-level URI of this document". > > In the case of UK Acts, they are created by the UK Parliament and will have jurisdiction over England but may not have jurisdiction over Scotland, Wales or Northern Ireland. I think this can apply at the overall Act level but the differences in jurisdiction are often within Acts with sections only applying to e.g. England and Wales. > > An example of this is
http://www.legislation.gov.uk/ukpga/2000/22 with the Parts of the Act applying to different jurisdictions: > - Part I: England and Wales > - Part II: England and Wales > - Part III: England, Wales, Scotland and Northern Ireland > - Part IV: England and Wales > - Part V: England, Wales and Scotland > - Part VI: England, Wales, Scotland and Northern Ireland > > And even with these Parts there are sections with even more granularity in terms of jurisdiction. > > How does Akoma Ntoso deal with this kind of complicated situation, where different sections of an Act have differing jurisdictions? I assume the FRBRcountry element would need to be defined as gb/uk with additional metadata to indicate the jurisdictional information throughout the document. > > > cheers > > Mark > > > > From:
legaldocml@lists.oasis-open.org [ mailto:
legaldocml@lists.oasis-open.org ] On Behalf Of Ashok Hariharan > Sent: 13 July 2012 11:23 > To:
akomantoso-xml@googlegroups.com;
legaldocml@lists.oasis-open.org > Subject: [legaldocml] Re: [akomantoso-xml] FRBRcountry > > Here is an earlier clarification of such a case from monica : > > <
http://code.google.com/p/akomantoso/wiki/Note_country_code_for_non_country_entities > > > > On Fri, Jul 13, 2012 at 1:37 AM, Grantcv1 <
grant.vergottini@gmail.com> wrote: > The FRBRcountry element prescribes ISO 3166-1 values for the country or the jurisdiction. In Monica's sample for California, she uses a value of "us" for the value of this element. I have a bit of a problem with this. The jurisdiction of this law is California, not the US. That California is part of the US isn't particularly relevent to the document. Shouldn't the FRBRcountry element really identify the jurisdicition that the law applies to - and then be able to handle jurisdictions that aren't countries? > > -Grant > -- > You received this message because you are subscribed to the Google Groups "akomantoso-xml" group. > To view this discussion on the web visit
https://groups.google.com/d/msg/akomantoso-xml/-/n6VxVZtcJoAJ . > To post to this group, send email to
akomantoso-xml@googlegroups.com. > To unsubscribe from this group, send email to akomantoso-xml+
unsubscribe@googlegroups.com. > For more options, visit this group at
http://groups.google.com/group/akomantoso-xml?hl=en . > > LexisNexis is a trading name of REED ELSEVIER (UK) LIMITED - Registered office - 1-3 STRAND, LONDON WC2N 5JR. Registered in England - Company No. 02746621 > > > -- Fabio Vitali Tiger got to hunt, bird got to fly, Dept. of Computer Science Man got to sit and wonder "Why, why, why?' Univ. of Bologna ITALY Tiger got to sleep, bird got to land, phone: +39 051 2094872 Man got to tell himself he understand. e-mail:
fabio@cs.unibo.it Kurt Vonnegut (1922-2007), "Cat's cradle"
http://vitali.web.cs.unibo.it/