Journal of Cross-disciplinary Research in Computational Law <p>The <strong><em>Journal of Cross-disciplinary Research in Computational Law</em></strong><strong> (CRCL)</strong> invites excellence in law, computer science and other relevant disciplines with a focus on two types of ‘legal technologies’: (1) <strong>data-driven</strong> (e.g. predictive analytics, ‘intelligent’ search) and (2) <strong>code-driven</strong> (e.g. smart contracts, algorithmic decision-making (ADM), legal expert systems), and (3) their hybrids (e.g. <strong>code-driven decision-making based on data-driven research</strong>).</p> <p>Legal practice is where computational law will be resisted, used or even fostered. CRCL wishes to raise questions as to (1) when the introduction of legal technologies should be resisted and on what grounds, (2) how and under what conditions they can be integrated into the practice of law and legal research and (3) how their integration may inform, erode or enhance legal protection and the rule of law.</p> <p>Please <strong><a href="">subscribe</a></strong> for updates on upcoming articles and issues.</p> <p><a href="">About CRCL</a> ◉ <a href="">Editorial team</a> ◉ <a href="">Submissions</a></p> Vrije Universiteit Brussel and Radboud University en-US Journal of Cross-disciplinary Research in Computational Law 2736-4321 The Structure and Legal Interpretation of Computer Programs <p class="Abstracttext">This is an essay about the relationship between legal interpretation and software interpretation, and in particular about what we gain by thinking about computers and programmers as interpreters in the same way that lawyers and judges are interpreters. I wish to propose that there is something to be gained by treating software as another type of law-like text, one that has its own interpretive rules, and that can be analysed using the conceptual tools we typically apply to legal interpretation. In particular, we can usefully distinguish three types of meaning that a program can have. The first is <em>naive functional meaning</em>: the effects that a program has when executed on a specific computer on a specific occasion. The second is <em>literal functional meaning</em>: the effects that a program would have if executed on a correctly functioning computer. The third is <em>ordinary functional meaning</em>: the effects that a program would have if executed correctly and was free of bugs. The punchline is that literal and ordinary functional meaning are inescapably social. The notions of what makes a computer ‘correctly functioning’ and what makes a program ‘bug free’ depend on the conventions of a particular technical community. We cannot reduce the meaning and effects of software to purely technical questions, because although meaning in programming languages is conventional in a different way than meaning in natural languages, it is conventional all the same.</p> <p class="Abstracttext"><strong>Reply by <a href="" target="_blank" rel="noopener">Marieke Huisman</a></strong>, University of Twente.</p> James Grimmelmann Copyright (c) 2023 James Grimmelmann 2023-05-11 2023-05-11 1 3 Rules, judgment and mechanisation <p>This paper is a philosophical exploration of the notion of judgment, a mode of reasoning that has a central role in legal practice as it currently stands. The first part considers the distinction proposed by Kant, and recently explored historically by Lorraine Daston, between the capacity to follow and execute rules and the capacity to determine whether a general rule applies to a particular situation (that is, judgment). This characterisation of judgment is compared with one proposed by Brian Cantwell Smith, as part of an argument that current AI technologies do not have judgment. The second part of the paper asks whether digital computers could in principle have judgment and concludes with a negative answer.</p> <p><strong>Reply by <a href="">William Lucy</a></strong>, University of Durham.</p> Mazviita Chirimuuta Copyright (c) 2023 Mazviita Chirimuuta 2023-02-09 2023-02-09 1 3