← Prev in month
← Prev in thread
Next in thread →
Next in month →
Re: [legalcite-markup-discuss] Cross-walks to existing database systems
Hi Frank, Re "'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 withsystems that handle records in that form" -- Do you mean how the markup would actually be designed? It is likely to early to say how that would look. What sorts of systems are you thinking about? Thanks for clarifying, /chet On Wed, Oct 30, 2013 at 6:00 PM, Frank Bennett <> wrote: On Thu, Oct 31, 2013 at 5:57 AM, Chet Ensign <> 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. > > /chet > > > > On Wed, Oct 30, 2013 at 11:26 AM, Patrick Durusau <> > wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Greetings! >> >> 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! >> >> Patrick >> >> 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/ >> >> iQIcBAEBAgAGBQJScSUyAAoJEAudyeI2QFGo1XsQAKd4zS+JlXPqxACIXNWk28Fv >> aVhcc0+B75PozCjcEsVHQ7WIJrDa1Noz1+sNjXHxiBja7XuOhLNbS0bbko0VhWXN >> fAfIKwAsypmTL6bfTZdh40UJErJ7uU1tS+osub2dUJOa/C2FvsAC3OjpyybUT7aA >> /zHpuQgSIt4LFzPc6JUKrRCDpU+n4rp1KG6/Z3EJUueJUMcey4ghkGgCjEdyv6nx >> 51MTFmMSwq8ZiwWIu1fok/SXnS8zy2eRF0KA76GL0dAI+CiRIcoUn4gMZpPuho92 >> tmAztAtJZpujUW76UotlZgnXVjDTGNZXQcB8VaMes8i7XaOj3dxc0aL5DFqwGiMB >> BDckCyHhUw/BZU1mjZF1JVHVhWFjnjsJSAlZsqYVvYxD/QXFqINrz/NX6VXlsmf5 >> QCMxnG3howoy3dXfJYwj+mOoho4ObVMa9VrzfWJMs+xk/eR95GqNSH6hVhHYPvjd >> r51mxfx1zYuQKNcrVtPnq5bAI1Ab4Xp7wl87VBj/MLMmLam+Ml2ljbu4Rto7b8Ec >> 55PxuQ6R1wWHgjXikQigrQ6QCkfwslCLOrpVl5q8H26WGXAd5h9+o4HPHki4eqzM >> 5EURKryFaCZAqrIpWCv3wN83Y6uwLbV3yylwBl67JnTvEgZz6Lb7oVyuDKowfFA9 >> oyh8XSyOWgw7oAPo3UwD >> =fz5C >> -----END PGP SIGNATURE----- >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: >> >> For additional commands, e-mail: >> >> > > > > -- > > /chet > ---------------- > Chet Ensign > Director of Standards Development and TC Administration > OASIS: Advancing open standards for the information society > http://www.oasis-open.org > > Primary: +1 973-996-2298 > Mobile: +1 201-341-1393 > > Check your work using the Support Request Submission Checklist at > http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html > > TC Administration information and support is available at > http://www.oasis-open.org/resources/tcadmin > > Follow OASIS on: > LinkedIn: http://linkd.in/OASISopen > Twitter: http://twitter.com/OASISopen > Facebook: http://facebook.com/oasis.open -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open
← Prev in month
← Prev in thread
Next in thread →
Next in month →