Toward a Restrictive View of Copyright Protection for Nonliteral Elements of Computer Programs: Recent Developments in the Federal Courts

1993 ◽  
Vol 79 (8) ◽  
pp. 2091
Author(s):  
W. H. Baird Garrett
2018 ◽  
Author(s):  
Maggie Gardner

92 New York University Law Review 390 (2017)When it comes to transnational litigation in the federal courts, it is time to retire the doctrine of forum non conveniens. The doctrine, which allows judges to decline jurisdiction in cases they believe would be better heard in foreign courts, is meant to promote international comity and protect defendant fairness. But it is not well-designed for the former purpose, and given recent developments at the Supreme Court, it is dangerously redundant when it comes to the latter. This Article seeks to demythologize forum non conveniens, to question its continuing relevance, and to encourage the courts and Congress to narrow its scope of application so that, when the time is right, it may be fully interred.


Author(s):  
Bruno de Vuyst

This chapter discusses legal and economic rationale in regards to open source software protection. Software programs are, under TRIPS1, protected by copyright (reference is made to the Berne Convention2). The issue with this protection is that, due to the dichotomy idea/expression that is typical for copyright protection, reverse engineering of software is not excluded, and copyright is hence found to be an insufficient protection. Hence, in the U.S., software makers have increasingly turned to patent protection. In Europe, there is an exclusion of computer programs in Article 52 (2) c) EPC (EPO, 1973), but this exclusion is increasingly narrowed and some call for abandoning the exclusion altogether. A proposal by the European Commission, made in 2002, called for a directive to allow national patent authorities to patent software in a broader way, so as to ensure further against reverse engineering; this proposal, however, was shelved in 2005 over active opposition within and outside the European parliament. In summary, open source software does not fit in any proprietary model; rather, it creates a freedom to operate. Ultimately, there is a need to rethink approaches to property law so as to allow for viable software packaging in both models.


2009 ◽  
pp. 2831-2842
Author(s):  
Bruno de Vuyst ◽  
Alea Fairchild

This chapter discusses legal and economic rationale in regards to open source software protection. Software programs are, under TRIPS1, protected by copyright (reference is made to the Berne Convention2). The issue with this protection is that, due to the dichotomy idea/expression that is typical for copyright protection, reverse engineering of software is not excluded, and copyright is hence found to be an insufficient protection. Hence, in the U.S., software makers have increasingly turned to patent protection. In Europe, there is an exclusion of computer programs in Article 52 (2) c) EPC (EPO, 1973), but this exclusion is increasingly narrowed and some call for abandoning the exclusion altogether. A proposal by the European Commission, made in 2002, called for a directive to allow national patent authorities to patent software in a broader way, so as to ensure further against reverse engineering; this proposal, however, was shelved in 2005 over active opposition within and outside the European parliament. In summary, open source software does not fit in any proprietary model; rather, it creates a freedom to operate. Ultimately, there is a need to rethink approaches to property law so as to allow for viable software packaging in both models.


Author(s):  
Hao-Yun Chen

Traditionally, software programmers write a series of hard-coded rules to instruct a machine, step by step. However, with the ubiquity of neural networks, instead of giving specific instructions, programmers can write a skeleton of code to build a neural network structure, and then feed the machine with data sets, in order to have the machine write code by itself. Software containing the code written in this manner changes and evolves over time as new data sets are input and processed. This characteristic distinguishes it markedly from traditional software, and is partly the reason why it is referred to as ‘software 2.0’. Yet the vagueness of the scope of such software might make it ineligible for protection by copyright law. To properly understand and address this issue, this chapter will first review the current scope of computer program protection under copyright laws, and point out the potential inherent issues arising from the application of copyright law to software 2.0. After identifying related copyright law issues, this chapter will then examine the possible justification for protecting computer programs in the context of software 2.0, aiming to explore whether new exclusivity should be granted or not under copyright law, and if not, what alternatives are available to provide protection for the investment in the creation and maintenance of software 2.0.


Sign in / Sign up

Export Citation Format

Share Document