Differences

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

--- project:case_law_as_a_service_claas [2013/09/19 21:32] – polto
+++ 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 |Overview of the Project Plan}} Many decisions on the national and international levels are available, but not accessible. Information is stored in opaque formats, without adequate metadata and can only be accessed with poor search tools. The aim of the challenge was to create a framework for case law as a service (CLaaS), that is, an infrastructure that allows users and any kind of applications easy access to case law.
+{{:project:claas_plan_v0-1.png?400|Overview of the Project Plan}}
-CLaaS is at the same 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.
+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.
-CLaaS will integrate into social media to include comments, preferences, recommendations, personal bookmarking and reputation.
-==== Mockup Design ====
+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.
+The following design sketches were done to provide an idea for possible interfaces to the system.
 {{: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|}}
-==== Crawler ====
+==== Demonstrations ====
-For the Swiss Federal Supreme Court, Alexander has built a crawler, which can be accessed here: http://46.20.244.65:8090/
+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:
-==== linked data ====
+  - **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]]
-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:
+==== Visualisations ====
- * [[http://beta.fusepool.com:8080/firstswim]]
- * [[http://beta.fusepool.com:8080/sparql/form]]
-Further information: [[project:case_law_ld|Case Law Linked Data]]
-==== Visualisation ====
-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. Hence, there is an obvious need for visualisation.
+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:
-These visualisations we found to be useful:
+  - **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 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 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}}
-. 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.
-{{:project:casegraph.png?200 }}3. Visualise the connection between cases: Cases often cite each other. This can be displayed in graphs that also convey further information (metadata).
-{{ :project:map_okcon_echr_caselaw.jpg?200}} 4. 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, but it can be much more than that: by tracking cases over time it can actually be an analysis tool. The project is [[project:echr_caselaw_visualization|European Court of Human Rights CaseLaw Visualization]].
 ===== What's ahead =====
- * Use the data to prototype the platform further
+  * Use the data to prototype the platform further
+  * Combine different data sources
+  * Develop an effective social integration
- * Combine different data sources
- * Develop an effective social integration
 ===== Team =====
@@ Line 56: / Line 43: @@
   * Oleg Burlaca, Ketse
   * Friedhelm Weinberg, HURIDOCS "Make available and accessible human rights case law around the world"
+  * Franziska Nyffeler (Des)
-and others - please 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 legal needs:dev needs:design needs:data needs:expert}}