Hello LegalCiteM
Reviewing what we covered during the last calls, I was asking myself some questions/remarks that I am sending out to the group. Sorry if some are obvious or were already answered. I would be happy if we could spend a few minutes in the next call to cover these.
Cheers
Thomas
- We covered examples that showed that tokenizing the citation and assigning tokens to features in the source-frame requires advanced knowledge of the citation; for example knowing that "2014" in "Pensions Act 2014" cannot be assigned to the year of the document, but is part of the title. Or turning "215 Va. 338" into an "official number" feature with [Va.] first, then [215], then [338].
So, building the source frame requires already a lot of interpretation. And the same citation could lead to different source-frames depending on who/which software annotates it. LCMReferences on the wiki writes "the source frame represents in a machine-readable way the same information that is specified in the source" - it is actually not the same information, it adds quite a lot of information/structure.
- How will a reference data strucutre be associated/encoded within (XML) texts ? For example taking this XML excerpt from one of Catherine's example :
<Citation id="c00023" Class="EuropeanUnionDirective" URI="http://www.legislation.gov.uk/european/directive/2001/0083" Number="83" Year="2001">2001/83/<AcronymExpansion="European Community">EC</Acronym></Citation>
Assuming the (JSON ?) encoding of the citation was done (automatically or manually), where/how would it be associated with the corresponding piece of text ? is it out of scope of LegalCiteM ?
- What is the intended/expected usage for the JSON data-structure ? Who / which software will use it, and what are typical use-cases for it ? maybe documenting use-cases (if not done already) could be helpful.
- Is it in the scope of LegalCiteM to write specifications of a JSON-reference resolver ? (e..g a service that will take as an input a JSON reference, and return as an output a (list of ?) URL to actual documents)
- It was said that LegalCiteM should find an agreement on, and specify the (work-level) features of a citation. How will this specification be written ? in an ontology ?