OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalcite-markup-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [legalcite-markup-discuss] "visible text of the citation undisturbed"


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! 

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 <patrick@durusau.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

- --
Patrick Durusau
patrick@durusau.net
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/

iQIcBAEBAgAGBQJScRwzAAoJEAudyeI2QFGo/MUQAIMcY50QYvbe26z6v5jHni/o
yzhwL+BjHogNCTSvVn0iSLnWLdbWNNX3sJZKusBpwMVSXj+0zh7QpsYvsmkOxeqa
YfBJbfmfJCbZ+ML5QyJZRoUNTIcMV6Ewk9JzmpXSbPWI3pBJM99kQzH0qXDO2fMT
jZPvhVV6GYkp78nrTURdPrenaO2DNBFWmrz/YHTN09qA6CYV4FcZiQKqGyK1ghfa
c7ow07StVqF2K2k96FHlV3dDOOlaFueq0HsGtecZd1Iu3EJKn1mGWqvYZUizno1l
D/NZ0spG0cbjA33G6TgRgiv310zqD/+mS9Z6zWOln0T/bqRIgRLC1KKmRimYHAbj
ZpTe+FaQFaLt6bZ3ocXZkEK5HvnjFCvS94MpZwASUXMhTEVrrd7UhtKKWXx8d2KW
3p+FJxS3bGF5IhYSH3KtBUU+IBu1w6aMnhpvs7W6zi7vUxsC+2gbzPTPbOM2SlG0
kDC4ikBJiJJEAF7ZT8u8MpQvAkPlkb8xzxSkXKwrQ11j/pUORFuCRqqsx1ZJUIWE
66aDSZaF3kWAsYHGRMedjjJp2A/kbXYS+gbRuDuk3P9wku3IpNwBPpO9ns3piqzz
PKhWbfAz4Aq+qLjRH6HTpuC3BVFdG+e68R9f0R/qGNukqHPR9Yp0mhdZ85hoy6oX
cXY+Dm0Y8kiX0FFUi3CY
=1NVW
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: legalcite-markup-discuss-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: legalcite-markup-discuss-help@lists.oasis-open.org




--

/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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]