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

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalcitem message

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


Subject: Template for use cases with some examples


LegalCiteM members, 

A bit later than promised however, attached, please find a sample use case template for review and discussion. We roughed this out last week and I think it strikes a balance between simplicity on one hand - not driving down into too much detail - and sufficiency on the other - each can clearly spell out a business or technical need in enough detail for us to (a) decide whether the output produced by the TC should enable the use case to satisfied and (b) determine whether or not proposed solutions actually do. 

The fields of the use cases are: 

1. Title - a short, descriptive name for the use case 

2. Description / user story - the broad description of what someone wants to accomplish 

3. Example - a specific example of the user story in practice 

4. Goal - what the result of the application of a legal citation standard to the user story would produce 

5. Actors - the participants in the user story 

6. Dependencies - essentially the bits that would have to be in place in order to enable the user story to be satisfied 

7. Assumptions - any assumptions about how the world works that underlies the user story 

Perhaps we can discuss this template and the examples at tomorrow's meeting? 

Best, 

/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
Sample use cases for legal citations 

1) Use case title: Refer to a specific representation of a judicial opinion 

Description / user story: A legal editor at a commercial publisher is working on a marking up citations to judicial opinions in a legal document. She wants to markup a citation so that if readers of her company's publications follow the citation, they will be taken to the company's proprietary version of the opinion. 

Example: The editor wants to mark up Thomson Reuters’ (West) rendition of Roe v. Wade. The full citation to the Westlaw reporter is: Roe v. Wade, 93 S.Ct. 705 (1973). Some elements that must be accommodated are:

  - Case name: Roe v. Wade (or parties: Roe, Wade)
  - Reporter title: Supreme Court Reporter
  - Publisher: West
  - Volume: 93
  - Page: 705
  - Year of decision: 1973
  - PURL of decision: [TBD by the legal editor]

Goal / desired outcome: Markup in the document with sufficient information to retrieve the publisher's own content. 

Actors: Legal editor (human), content editing program (software)

Dependencies: The content editing program is capable of adding the markup to the document. The content editing program is capable of capturing or exposing to the editor all the metadata or structure needed to construct the embedded markup. The legal editor has access to information defining the resource that the citation should reference. The markup is capable of containing all the necessary metadata. 

Assumptions: The editor knows which opinion to reference. The opinion is available in the publisher's content collection. The editor has the means to access the required metadata. 

 
2) Use case title: Extract citations from documents  

Description / user story: A legal scholar wants to use software to scan a collection of legal content and extract citation metadata and keep it associated with the specific document from which it was harvested for further legal study.

Example: 

Goal / desired outcome: A simple database of sources and the citation metadata contained within each document. 

Actors: Legal scholar (human), content scanning program (software)

Dependencies: The collection must have sufficient metadata to identify each document and each citation within it. The content scanning program must have access to the collection. 

Assumptions: Citation markup exists in the corpus of content. 


3) Use case title: Disambiguate identically codified statutes   

Description / user story: A legal editor is working on a product that cites to a state's statutory code. The code contains multiple instances of bills having resulted in multiple sections with identical citations but different content (e.g. multiple paragraphs labelled TX Code Ann. Tit. 5, Sec. 92.021). The legal editor wants to cite to the appropriate instance.  

Goal / desired outcome: A tagged citation in the product that can resolve to / retrieve the proper text from the code. 

Example: 

Actors: Legal editor (human), content editing program (software)

Dependencies: The editor has some means for locating the correct text portion to cite to.  

Assumptions: ??There is sufficient data either explicit or implied in the citation as it is originally typed in the text that an accurate metadata record can be derived.


4) Use case title: Insert metadata into a document that contains citations to court decisions to facilitate links to instances of the cited court decision

Description / user story: A publisher of court decisions receives court decisions in plain text or some variation thereof which has no markup or metadata of any kind.  They wish to identify citations to other court decisions and insert metadata at those points which can be resolved to instances of the cited document.

Example: A publisher is presented with a plain text document, or a reasonable equivalent thereof, which contains the citations:  Warphin v. Yaya, 23 Ohio 456 (2012), and R. v. Ali, [2014] EWCA Crim 140  para.27.  She wishes to insert metadata at those points which can resolve to instances of the cited documents.

Goal / desired outcome: A tagged citation in the product that can resolve to / retrieve the cited document.

Actors: Publisher (humaniod), court citation identification and metadata insertion program  (software).

Assumptions: There is sufficient data either explicit or implied in the citation as it is originally typed in the text that an accurate metadata record can be derived.



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