Re: [legalcite-markup-discuss] Annotation of inline citations

Patrick, yes - good thoughts. I think this would start as one of the use cases to be collected by the TC before any decisions get made on design issues. 

/chet

On Wed, Oct 30, 2013 at 11:00 AM, Patrick Durusau <> wrote:

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1

Greetings!

Another question that occurred to me this morning, when writing about

the opaqueness of visible text, how citations are annotated is going

to make a real difference in the viability of the work product.

There may be other choices but the three I see are:

1) Inline annotation of the opaque text strings that are citations

where the metadata for each citation is also included with the

annotation.

2) Inline annotation of the opaque text strings that are citations

with a unique identifier that can be resolved to a resource outside

the document which holds all the metadata.

3) Pointing to the opaque text strings that are citations from an

outside resource that holds the metadata about the citation. (May well

display "inline" but that's an inclusion/display issue.)

I ask because with #1, if a citation occurs multiple times in a single

text (or with different opaque strings for the same citation), will

the metadata be replicated for each occurrence?

I suppose one way to avoid that issue would be to point back to the

first occurrence.

Although, inline metadata will raise the issue of how metadata is

updated and distributed, since electronic copies of legal materials

may reside in diverse locations.

I ask because in terms of the charter, I would be very interested in a

TC that plans to pursue #2 or #3, not so hot on a TC looking to do #1.

Please respond on list.

Hope everyone is having a great day!

Patrick

- --

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/

iQIcBAEBAgAGBQJScR8AAAoJEAudyeI2QFGoB/wP/jbOB3DcdMna3U9W1+zyOvWd

j7p8nz4/fhyCnMF2nZ+ntvT6U7V7hqcv0wxbq95eubq4n8j4B7BZXqd9m/lnFgP/

6752CdST5ll2qIIIuwjPwrnfZDrvJyjv2JwsV2+A36ZrZ1UuaxArYFd8E/gYvRQH

O6K2FuVdr8/rH6Ddoqt75bJPd8ee1DVOY/H4rLNsfLNfyeE94yN02LXQmipkgyrL

BRLirR+ajDrjPx+0IaL/0gtL9l6RgkaveNak4o0mvevgBpd++H4pg1WKVu0duk4h

uF/TSL43uCZryHGsNwVjyq/1pn683M+vdugZwYdT/cFuwr5xSuMvyFJvNWmDzR28

g6XI7xGXq3qfO5n8NO4zbXVuATJmSpUi2m0CtBwuvpjuIm716Yg/BiLAG1ruHIX+

5ErJJ0pc+nlYCwqIxLBlypgbAjgQU+Bn5mXH33c+3zn5jES1alLDbEz0dwi0fhHi

EFdLhpxr8r3OOeq9blPQTEsiC4pUcpGQus9KI0rm9I1XfO85MBmKXztTe87U4Rse

fHYBctfzH7Xaq2PdfdmJbmxB+b6OD0Qyi9SXt4FhDcsHfS/f770wlX8FYnW9EZq8

Mwh1s1On0b1eHmqgWPqJSWGMscDmuDBSbdLvzK5JxxNRz4KTtSKIa8H26hkVWDXZ

SwFiUWZdvgayc4d2qYJM

=SWgj

-----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