Differences

This shows you the differences between two versions of the page.

--- project:case_law_as_a_service_claas [2013/09/19 14:14] – [Case Law as a Service (CLaaS)] jhmorin
+++ project:case_law_as_a_service_claas [2013/09/24 15:29] – polto
@@ Line 1: / Line 1: @@
 ===== Case Law as a Service (CLaaS) =====
-{{:project:claas_plan_v0-1.png?200 |}} There are lots of court cases around that are not easily accessible. We should create an infrastructure to facilitate spreading of cases and assoiciated metadata.
+{{:project:claas_plan_v0-1.png?400|Overview of the Project Plan}}
-CLaaS Case Law as a Service is an approach to give any kind of applications easy access to case law.
-CLaaS is at the sampe time an API for accessing cases, a software to manage cases and a universe with Appstore to manage a basic application with added views and features on top of it.
-CLaaS will integrate into social media to include comments, preferences, remommandations, personal collections and social ranking.
-{{:project:claas_website-homepage_v0-1.png?200|}} {{:project:claas_website_result-page_v0-1.png?200|}}
+Many legal decisions, or case results, on national and international levels are available online - but are not accessible enough. The information is stored in opaque formats, with inadequate metadata and frustrating search tools. The aim of this project was to create a framework for Case Law as a Service (CLaaS), that is, a platform architecture that allows users and diverse applications easy access to case law.
-Collecting a large number of cases has often to be done by crawlers. Alexander has built a crawler prototype for that: ... link to that project ...
+CLaaS is at the same time an API for accessing cases, software to manage such cases, and an app ecosystem with a store to manage basic applications with added views and functionality on top of it. CLaaS will integrate into social media to include collaboration features like comments, preferences, recommendations, personal bookmarking and reputation.
-Cases should be part of the semantic web. Reto and Jörn have built a translation into linked data (RDF). Tools based on linked data can immediately be used to search and interact on that data: ... link to that project ...
+The following design sketches were done to provide an idea for possible interfaces to the system.
-Collecting a large number of cases will however make it even more difficult to find the right cases. Currently most systems will present cases and list of cases in pure text format. The advantages of graphics (one image says more than one thousand words) are not used.
-What kind of visualizations can be useful:
+{{:project:claas_website-homepage_v0-1.png?200|Mockup of the Search|}} {{:project:claas_website_result-page_v0-1.png?200|Mockup of Search Results|}}
-. Visualize one case: Cases are often long (10-30 pages or even more) and it is time consuming to identify rules and reasonings of the court. Cases can be annotaded with Icons and the reasoning can be displayed in a structured manner (Case matrix) (Christian and Franziska are preparing an example case preparation for that) This is listed as a seperate project [[project:case_law_ld|Case Law Linked Data]]
+==== Demonstrations ====
-. Visualize a list of cases: Hitlists and other lists of cases can be annotated with easily accessible information by icons indicating case outcome, type of case, type of reasoning, area/region of the court etc.
+In order to illustrate the potential of such a system, the components of which are not all available or open today, our team has worked on a number of prototype sub-projects:
-. Visualize the connection between cases: Cases often cite each other. This can be displayed in graphs that also convey further information (metadata).
+  - **Online case history crawler**: based on data of the [[http://www.bger.ch/|Swiss Federal Supreme Court]], Alexander has built a custom search engine which can be accessed here: [[http://yacy.free-it-foundation.org:8090/|Demo server]]. For further information see: [[project:legal:swiss_supremecourt|Swiss Supreme Court]]
+  - **Linked Data**: cases should be linked on the Semantic Web. Reto and Jörn have built a translation into linked data (RDF). Tools based on linked data can immediately be used to search and interact with information. Check out the [[http://beta.fusepool.com:8080/firstswim|Demo server]] and [[http://beta.fusepool.com:8080/sparql/form|SPARQL query API]] for advanced users. Further background here: [[project:case_law_ld|Case Law Linked Data]]
+==== Visualisations ====
+Collecting a large number of cases will however make it even more difficult to find the right cases - there is a definite danger that many cases will simply end up being massive walls of text and lists. The following types of visualization should prove to be useful:
-. Geographic visualization of a large number of cases: When a search retrieves a large number of cases (1000 or more) it is impossible to even glimpse over this list of cases. Facets help there but are not easily comprehensible because they just consist out of text and many numbers. A graphical visualization could help there. Oleg will present an interactive display of cases on a world or regional map together with a timeline. This display can also be animated to show how the searched topic evolved during time. We can imagine many other statistical presentations of the data. Oleg did a really nice prototype for that. It is listed as a seperate project ...
+  - **Visualise one case:** Cases are often long (10-30 pages or even more) and it is time consuming to identify rules and reasonings of the court. Cases can be annotaded with Icons and the reasoning can be displayed in a structured manner (Case matrix) (Christian and Franziska are preparing an example case preparation for that) This is listed as a seperate project [[project:case_law_ld|Case Law Linked Data]]
+  - **Visualise a list of cases:** Hitlists and other lists of cases can be annotated with easily accessible information by icons indicating case outcome, type of case, type of reasoning, area/region of the court etc.
+  - **Visualise the connection between cases:** Cases often cite each other. This can be displayed in graphs that also convey further information (metadata).\\ {{:project:casegraph.png?200}}
+  - **Geographic visualisation of a large number of cases:** When a search retrieves a large number of cases (1000 or more) it is impossible to even glimpse over this list of cases. Facets help there but are not easily comprehensible because they just consist out of text and many numbers. A graphical visualisation helps, and by tracking cases over time it can actually be an analysis tool. The project is documented here:  [[project:echr_caselaw_visualization|European Court of Human Rights Case Law Visualization]]. \\ {{:project:map_okcon_echr_caselaw.jpg?200}}
-Include links to your demo and/or source code.
+===== What's ahead =====
-===== Data =====
- * 5000 cases of the Swiss federal court
+  * Use the data to prototype the platform further
+  * Combine different data sources
- * access to Swisslex and sample data and metadata from Swisslex
+  * Develop an effective social integration
- * access to UN Human Rights Cases
- * access to ECHR Cases
 ===== Team =====
@@ Line 42: / Line 39: @@
   * Christian Laux, Laux Lawyers "IT Law is our passion" (Idea)
   * Alexander Poltorak, Free IT Foundation "Open Hardware & Free SW" (Idea)
+  * Lionel Lourdin, Free IT Foundation "Open Hardware & Free SW" (Idea+Des)
   * Florian Ducommun, HDC Lawfirm, CC "Please copy & share my work"
+  * Oleg Burlaca, Ketse
   * Friedhelm Weinberg, HURIDOCS "Make available and accessible human rights case law around the world"
+  * Franziska Nyffeler (Des)
-and others - please fill add yourself and add your contact details
 ===== Licenses =====
   * CC BY-SA
   * AGPL
-===== Links =====
-  * Relevant documentation ...
-  * Blog or forum posts ...
-  * Tools you used ...
-{{tag>status:concept needs:dev needs:design needs:data needs:expert}}
+{{tag>status:concept legal needs:dev needs:design needs:data needs:expert}}