Next in thread →
Next in month →
Re: [legalcite-markup-discuss] "visible text of the citation undisturbed"
It is there to really make explicitly clear the intent to make it possible for the language of the document to remain undisturbed. I agree that your wording says it implicitly - in my experience though it is a sufficiently touchy subject to warrant stating it as clearly as possible. In fact, I think someone made the suggestion. /chet On Wed, Oct 30, 2013 at 1:09 PM, Patrick Durusau <> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chet, On 10/30/2013 11:19 AM, Chet Ensign wrote: > Well, how the model is constructed and used in tagging a citation > will be part of the work the TC works out. What I'm trying to say > is that if, looking at the displayed document, the reader sees "843 > A. 2d, at 527" before tagging, they can still see "843 A. 2d, at > 527" after tagging - even if it was supposed to be "834" but > somebody was typing too fast! > OK, but that sounds like an odd case to be in "scope." Why not: ***** Enables legal citations to be richly annotated using markup. ***** Neither annotation nor markup imply anything about display. Better to spell "cites" out and qualify as "legal" citations. Hope you are having a great day! Patrick > The key point being that whatever the visible citation looks like, > it will not be necessary to fix it, normalize it, tidy it up, etc. > in order to be able to drive functionality off it. *Can* fix it of > course if that's desirable but won't be required to. > > I may have mentioned this before, but I once mediated an argument > between a programmer who wanted to 'fix' a citation in a Federal > court opinion and a managing editor who explained, quite patiently, > that whether or not the citation contained a typo, it was now the > documented law of the land so the programmer had better figure out > an alternative way to work with it. > > /chet > > > On Wed, Oct 30, 2013 at 10:48 AM, Patrick Durusau > <>wrote: > > Greetings! > > The first list item under scope in the proposed charter reads: > > ***** Enables cites to be richly tagged while leaving the visible > text of the citation undisturbed. ***** > > I have been puzzling over the "leaving the visible text of the > citation undisturbed" language here and elsewhere in these > discussions. > > It occurred to me this morning that one possible meaning is that > the "visible text of the citation" means a tradition citation, > like: > > Marbury v. Madison, 5 U.S. 137 > > is an opaque text string, no intervening markup. > > And, annotation comes from either: > > <annotation + attributes>Marbury v. Madison, 5 U.S. > 137</annotation> > > or by a pointer to the text string: Marbury v. Madison, 5 U.S. > 137. > > But in either case, the "visible" citation is not encoded with > markup to support the annotation. > > That would make the annotation scheme independent of whatever > print citation style is in use, although better systems will > probably construct a replica of the print citation from the encoded > metadata. > > Close? Far away? > > Please respond to the list. > > Hope everyone is having a great day! > > Patrick > >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: >> For >> additional commands, e-mail: >> >> >> > > - -- 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/ iQIcBAEBAgAGBQJScT09AAoJEAudyeI2QFGoNzAP/ieSL17XmKsl6NZ5VHW4UUrH gOyGFz2agQem2USZEt4P3jmQ6jbSGgKFZwaEDmg1cHohDtWgxQn1vLsndyU3KINv rDEbxs9SE6MAS7/xXMrb9YXFi5tkue+J/YgPVinPFOIwCIOL6daV1E79Fr4QrquL VnqxkH8iMyqj81AkWcEEFrvYS3wJMLeVVFLI1NXotR4Ks3IMRpr8BcAPnt9/opkI wM/HP5OY7ta24CDGquEH33Cj21WqzuJfsAh/+91oG99rfFcFdfFmdvT58XDbXNwp 6PqQe/2fbY4rF8wFoBYy7wACnRIX5VeCYINzV0yCRSTzVBadi59S93VUZD96MNwR 2bSXOZ0caUmMvX03QQ/W4yugFycssEW6K3fdO38PV40xt7HPJvqV9FIDneA+hpMd xtGTysb95W8qf3EsVoAx3jT18YfG2cjLtwRboIpEmapNRLeaqdZI9CLdzqYt+v+/ 8S57Vv01hCJsnyN/ddIyIXsZb9Ki0qA2QfmN5bI1GIUdpP9CajnVdl5J2YKiLWtO 0Pnv3z8ND9HmkBklUq667SNNnFRsXwOv/03irRscFC/01yBWkE3qlG1OHgJENhUA /bwt0f6ZJFMhj6J49HhgoTozYlFaPFAvbZI/Y8+E+NJZZI6PwLvaJptZvzzTHW1R 19A/5BCsdW1ESjaylXed =wL9Y -----END PGP SIGNATURE----- -- /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
Next in thread →
Next in month →