Welcome to www.minisinbox.com

Copyright infringement case Learning Copyright Law through Copyright Infringement Cases Copyright infringement cases can be both costly and time consuming. Considering copyright infringement is something that isn’t as easily defined as theft or speeding, there are numerous copyright infringement cases that are changing the way copyright law is viewed in the United States of America. By reviewing a few of these copyright infringement cases, you’ll be able to get a better idea of what is, and is not, acceptable use of copyrighted works. As a forward, however, you’ll need to know a little bit about copyright law. Most copyright lawsuits are brought to the courts because a copyright owner has found their copyright is being used outside the copyright laws. This usually means that the copyright holder hadn’t been asked for permission to use the work, or if they had, that the work is not being used in an agreed-upon context or they have not been paid royalties. The copyright infringement cases, listed below, give a sampling of what goes to the Supreme Court in copyright infringement. Feist Publications v. Rural Telephone Service Co (6th Cir. 1996) This copyright infringement case was brought upon the Supreme Court in 1996 regarding the copyright of a database. The supreme court, in this instance, decided that compilations of data (such as in a database) are only protected by copyright when they are “arranged and selected in an original manner.” Although the level of originality needed to make the database copyright-able is not very high, the pages of a directory such as a phone book are not protect-able because the data contained therein is arranged geographically, then alphabetically. Because of this, the data was not original enough to warrant a copyright infringement charge, and the competing telephone company was allowed to tap into their competitors’ database and use that data in their own work without liability. Princeton University Press v. Michigan Document Services, Inc (6th Cir 1996) This case has to do with the ‘fair use’ law, which is defined in the Copyright Act of 1976, 17 U.S.C. § 107. In this case, a photocopying service was sued for copyright infringement for making ‘course packs’ for the University of Michigan. In this case, a course pack was a group of reading materials assigned by a professor – then the course pack was bound together by a professional copy shop. In the fair use system, there is a system available for payment of copyright fees to publishers whose works are used in course materials, the printing shop owner refused to pay the copyright cost. When it went to the Supreme Court, they analyzed the fair use code and found that it was NOT fair use, and the printing shop had to pay the copyright costs. As you can see, copyright infringement cases are cases in which someone violates the rights of a copyright owner, as provided by 17 USC §106, or of the author as provided in §106A. These copyright infringement cases can be taken to either criminal or civil court, and can carry with it a hefty fine. Copyright infringement cases are brought upon people who violate copyrights every day. In recent times, you’ll find many copyright cases in relation to electronic copyrights – such as those you’d find on a website or PDF file, as well as other digital media such as music and audio files. It’s probable that you’ve seen copyright cases brought against the common person – such as a child or family – for downloading digital music in the form of MP3s. In the current internet age we’re in, it’s not surprising to see so many music and video copyright cases brought to us because of peer to peer file sharing made possible by the internet. You can be certain that until people know the rules of copyright, and downloading copyrighted material from the internet that we’ll see many more copyright cases.

Software copyright statement A Software Copyright Statement Protects Current and Future Works If you have a site that is dedicated to the sharing and distribution of open source software it is a great idea to have a software copyright statement that explains the limits of use for your software as well as the limits of your responsibility for those uses. I also recommend getting an attorney to look over the statement before posting it just to be sure there are no legal issues that you may be unaware of. A software copyright statement doesn't have to be a 10 page booklet on the law or the protections that copyright offers, it should be a simple short paragraph stating the basics and hopefully covering your rear from litigation and/or responsibility should someone use the software you are allowing them to use for something insanely stupid or frighteningly criminal while establishing your ownership of the material and expectations of those you are allowing to use your creation. This for some is a no brainer because they've done it before and know the ropes. There are new software developers born and made each and every day and this type of software copyright statement may serve to save them a little grief of their own some day. If you are being kind enough to freely share the software you created with others, you'd like to think that they would at least return the favor of using it within the letter of the law or the manner in which it was intended. This, however, is rarely the case so protecting yourself, your copyright, and your future interests by posting a software copyright statement on your website is really the best way to go in a situation such as this. Trust me I'm not trying to talk anyone out of sharing his or her software with the world. I rather like open source software and admit to using it freely (no pun intended). I love saving money almost as much as I love playing around with new technology. Software allows me to do that and find likes and dislikes about all kinds of programs. Issuing a software copyright statement is one way of protecting your investment of time, effort, energy, and sheer brilliance in the making and design of your technological masterpiece. Hopefully that flattery will keep you going a bit longer at any rate. It is important to know that a software copyright statement is only part of the process required to protect your software but for the most part poses a significant deterrent to those that would abuse your copyright and/or your kindness in allowing the distribution of your software. Even if you are charging people for the use of your software (we are a nation of capitalists after all) you still need to protect the labor you have put into making not only the software but the distribution method, the website, the payment method and the thousands of other things that are part and parcel of the business model for your software distribution. Your software copyright statement is a very small protection for your software don't expect it to be the brunt of your protection. Most of the software developers, coders, and programmers (and any other name you wish to call them) that I know aren't as concerned nearly as much about associating their name with the products they create as they are with protecting future potential income from both the products they are currently designing and the future, improvements they will make to the software and the much improved finished product that comes later. By protecting all your work with a software copyright statement you are not only protecting current works but future works as well.

Web Hosting - Sharing A Server Things To Think About You can often get a substantial discount off web hosting fees by sharing a server with other sites. Or, you may have multiple sites of your own on the same system. But, just as sharing a house can have benefits and drawbacks, so too with a server. The first consideration is availability. Shared servers get re-booted more often than stand alone systems. That can happen for multiple reasons. Another site's software may produce a problem or make a change that requires a re-boot. While that's less common on Unix-based systems than on Windows, it still happens. Be prepared for more scheduled and unplanned outages when you share a server. Load is the next, and more obvious, issue. A single pickup truck can only haul so much weight. If the truck is already half-loaded with someone else's rocks, it will not haul yours as easily. Most websites are fairly static. A reader hits a page, then spends some time skimming it before loading another. During that time, the server has capacity to satisfy other requests without affecting you. All the shared resources - CPU, memory, disks, network and other components - can easily handle multiple users (up to a point). But all servers have inherent capacity limitations. The component that processes software instructions (the CPU) can only do so much. Most large servers will have more than one (some as many as 16), but there are still limits to what they can do. The more requests they receive, the busier they are. At a certain point, your software request (such as accessing a website page) has to wait a bit. Memory on a server functions in a similar way. It's a shared resource on the server and there is only so much of it. As it gets used up, the system lets one process use some, then another, in turn. But sharing that resource causes delays. The more requests there are, the longer the delays. You may experience that as waiting for a page to appear in the browser or a file to download. Bottlenecks can appear in other places outside, but connected to, the server itself. Network components get shared among multiple users along with everything else. And, as with those others, the more requests there are (and the longer they tie them up) the longer the delays you notice. The only way to get an objective look at whether a server and the connected network have enough capacity is to measure and test. All systems are capable of reporting how much of what is being used. Most can compile that information into some form of statistical report. Reviewing that data allows for a rational assessment of how much capacity is being used and how much is still available. It also allows a knowledgeable person to make projections of how much more sharing is possible with what level of impact. Request that information and, if necessary, get help in interpreting it. Then you can make a cost-benefit decision based on fact.