[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [legalcite-markup-discuss] Cross-walks to existing database systems
On Thu, Oct 31, 2013 at 5:57 AM, Chet Ensign <email@example.com> wrote:
>>> Another omission from the charter is discovery, reporting and mapping
> between existing legal metadata database holdings.
> There was discussion of that in earlier conversations - my take is that our
> work should support those use cases / business needs but we shouldn't try to
> propose how it should be done.
I'm wondering what the legalcite TC structures will look like. If they
are arbitrary flat records (item type + fields), a defined mapping
into RDF would presumably be needed to get consistent results with
systems that handle records in that form.
>>> It is unreasonable to think that existing metadata databases will
> covert their legacy (from a legalcite viewpoint) data into the model
> produced by the proposed TC,
> I agree - looking at their needs / structures strikes me as an important
> part of the process of developing a standard
>>> A journey into the sea of legal citations ... Perhaps it's age but
>>> setting out in a small boat
> I love the sailing analogy...
>>> PS: I can suggest some formal charter language if that would be helpful.
> Please do - that would help focus the discussion.
> On Wed, Oct 30, 2013 at 11:26 AM, Patrick Durusau <firstname.lastname@example.org>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> One post spawns another! ;-)
>> While writing about the need to hold the metadata separate from a
>> citation in a text, it occurred to me that there are already databases
>> in existence now that hold such data.
>> Those would be in addition to the legal markup systems I asked about
>> yesterday, which are not mentioned as being candidates for mappings
>> between legalcite TC markup and their markup in the charter.
>> Another omission from the charter is discovery, reporting and mapping
>> between existing legal metadata database holdings.
>> It is unreasonable to think that existing metadata databases will
>> covert their legacy (from a legalcite viewpoint) data into the model
>> produced by the proposed TC, unless by some happy accident the TC
>> happens to duplicate their data model.
>> Additional items that should be explicitly included in the charter:
>> 1) Mapping (or Crosswalk) between legalcite TC markup and at a
>> minimum, the highly visible legal markup systems cited in the charter, and
>> 2) Mapping (or Crosswalk) between legalcite TC data model and existing
>> legal metadata data models, where available.
>> A journey into the sea of legal citations is more likely to end
>> pleasantly if we can build a large boat (induce many of the highly
>> visible systems to participate in the TC) and secure our boat to other
>> boats (mappings/crosswalks to other systems and metadata databases).
>> Perhaps it's age but setting out in a small boat, even with skilled
>> and adventurous colleagues, where a successful journey depends upon
>> others replacing their views with our own, isn't as attractive as it
>> might have been, once upon a time.
>> Please respond on list.
>> Hope everyone is having a great day!
>> PS: I can suggest some formal charter language if that would be helpful.
>> - --
>> Patrick Durusau
>> Technical Advisory Board, OASIS (TAB)
>> Former Chair, V1 - US TAG to JTC 1/SC 34
>> Convener, JTC 1/SC 34/WG 3 (Topic Maps)
>> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
>> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>> Another Word For It (blog): http://tm.durusau.net
>> Homepage: http://www.durusau.net
>> Twitter: patrickDurusau
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>> -----END PGP SIGNATURE-----
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> Chet Ensign
> Director of Standards Development and TC Administration
> OASIS: Advancing open standards for the information society
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393
> Check your work using the Support Request Submission Checklist at
> TC Administration information and support is available at
> Follow OASIS on:
> LinkedIn: http://linkd.in/OASISopen
> Twitter: http://twitter.com/OASISopen
> Facebook: http://facebook.com/oasis.open