Stanford Robotics and the Law Conference call for papers

I'm late getting to this (my own fault, I missed an important email), but We: Robot, the Robotics and the Law Conference at Stanford Law School is still accepting papers until Jan 18. Last year's event was apparently smashing, and this year's CFP is quite enticing:

The following list is by no means exhaustive, but rather meant as an elaboration on conference themes:

* Legal and policy responses to likely effects of robotics on manufacturing or the environment
* Perspectives on the interplay between legal frameworks and robotic software and hardware
* Intellectual property issues raised by collaboration within robotics (or with robots)
* Perspectives on collaboration between legal and technical communities
* Tort law issues, including product liability, professional malpractice, and the calculation of damages
* Administrative law issues, including FDA or FAA approval
* Privacy law and privacy enhancing technologies
* Comparative/international perspectives on robotics law
* Issues of legal and economic policy, including tax, employment, and corporate governance

In addition to scholarly papers, we invite proposals for demos of cutting-edge commercial applications of robotics or recent technical research that speaks one way or another to the immediate commercial prospects of robots.

Call For Papers: Robotics and the Law Conference at Stanford Law School


  1. I’d love to see some discussion around legal policy with respect to self-driving cars. It’s clear that self-driving cars of the type that Google is developing could save thousands of lives and deliver amazing gains in energy efficiency. 

    However, as soon as a glitch contributes to a death, lawsuits will be flying. What company would want to commercialize this technology when it’s guaranteed to end up in court?

    If telephone companies can get immunity from lawsuits in the name of national security, then perhaps self-driving car manufacturers should be immune from lawsuits in the name of public safety.

Comments are closed.