luap42 soon at gpn24Apr 6

Introducing the #JDF Data Set (jdf.luap42.de), a standard classifying objects involved in judicial proceedings, such as

- case types (lawsuit, appeal, petition for injunctive relief, etc.)
- document types (petition, reply, judgements, etc.)
- entity types (court officials, private entities, attorneys, etc.)

by mapping such objects to short, unique codes allowing language- and legal system-independet referencing.

>>> https://jdf.luap42.de <<<

JDF Data Browser | jdf-viewer

Show threadluap42 soon at gpn24

The idea is to have a set of enumerations that can be used in data bases or for annotating documents/etc, which is independent of

- the specific application and its naming convention
- the language used for the application
- the nuances of the legal system where the application is used

thus allowing

- semantic annotations of documents and stuff
- more generalized applications
- more interconnection between applications.

#JDF #JDFDataSet

Apr 6 at 11:29amWeb
Show threadluap42 soon at gpn24Apr 6
This is only a first, rough draft of the #JDF #JDFDataSet, but please  and, even more importantly,  with feedback or questions so that we can perfect this standard together.
Show threadKennyApr 8
@luap42 Will these just be tags that are meant to be added to categorize stuff or will this be a machine-readable format that will support text values as well? I‘m thinking of date of ruling, case number, adjudicating court, etc.
Show threadluap42 soon at gpn24Apr 8
@weizenspreu JDF will be a machine-readable (HTML-/XML-based) format for all types of documents relating to judicial proceedings (motions, briefs, decisions), these data sets are just enumerations which will be used for some data fields in that format, but they can of course also be used as annotations or as keys inside a program or whatever
Show threadKennyApr 8
@luap42 Too bad. So the relevant information required for searching need to be handled differently.
Show threadluap42 soon at gpn24Apr 8
@weizenspreu wdym?
Show threadKennyApr 8
@luap42 I‘ll just wait and see what it‘ll look like. Could be nice to have well-formed metadata when collecting a literature corpus for a legal paper.
Show threadluap42 soon at gpn24Apr 8
@weizenspreu Fair, just err.. don't forget to ask me again in 10 years lmao
Show threadluap42 soon at gpn24Apr 8
@weizenspreu So basically JDF per se will be an XML file containing a meta data header (e. g. for case types, numbers, dates, involved and responsible entities) and then a body field containing a (possibly restricted) XHTML block with the text of the document
Show threadluap42 soon at gpn24Apr 8
@weizenspreu All of this is however part of my broader eCuria vision, which would include drastic changes to how filing and stuff works and these data sets would also become relevant in the case management software and stuff, it's just that the planned JDF standard is like where the enums come from