Fair Use

Written by Richard Lowe

Continued from page 1

- Wholesale copying of pages from a website to your own website.

- Scanning photographs of Heather Locklear from Cosmopolitan for your fan site.

- Including dozens of sound clips fromrepparttar Simpsons series on your web site. It is still a copyright violation regardless of whether you "borrowed" them fromrepparttar 131980 official Simpsons site or you recorded them from your own VCR.

- You are annoyed because your favorite encyclopedia site now charges a monthly fee instead of being ad supported. You include several articles directly on your own site so people will not have to payrepparttar 131981 fee to seerepparttar 131982 articles.

These would not only violate copyright law, but they would also violate bandwidth stealing rules.

- Linking directly to a photo of Heather Locklear onrepparttar 131983 Cosmopolitan site. You could do this legally by (a) asking and receiving permission, or (b) creating a link torepparttar 131984 HTML document onrepparttar 131985 Cosmopolitan site which containsrepparttar 131986 picture.

- Linking directly to sound files fromrepparttar 131987 official Simpsons site. You could legally, however, link torepparttar 131988 HTML pages onrepparttar 131989 Simpsons site which containrepparttar 131990 WAV files.

- Linking directly to video clips fromrepparttar 131991 official Star Trek site. Again, you could link torepparttar 131992 pages containingrepparttar 131993 video clips.

IMPORTANT NOTE ABOUT LINKING Linking to pages within a web site besidesrepparttar 131994 entrance page is still being tested in court. To date it is considered acceptable practice - however,repparttar 131995 results of several recent court cases seem to indicate this is changing to "it's okay unless specifically excluded byrepparttar 131996 web site". My personal opinion is to link to HTML pages to your hearts content, but to never link directly to graphics, sound files, videos and other media.

One ofrepparttar 131997 critical issues with fair use isrepparttar 131998 definition itself. Many years ago a supreme court justice defined pornography simply as "I know it when I see it", and fair use is governed by a similar concept.

Another important consideration about fair use isrepparttar 131999 copyright owner does not need to be and should not be asked for permission. Why? Because fair use is one ofrepparttar 132000 most important pieces ofrepparttar 132001 copyright law puzzle. It allows students to write papers, critics to criticize, authors to quote and researchers to research. By asking permission you are not invoking fair use and in fact you are, in a small way, weakeningrepparttar 132002 law. You do haverepparttar 132003 right to make fair use of any work that exists (well, withrepparttar 132004 exception of classified government documents and things covered under trade secrets laws and non-disclosure agreements).

If you are an author you have a right to your copyrights, and you also have a right to use other's works fairly. Laws are funny things, they are just words unless they are actively and constantly used, tested and upheld. Rights are even more important - if you don't use them you lose them.

Of course (and this does not violate my point above about not asking), you always haverepparttar 132005 option of writing torepparttar 132006 copyright owner and directly asking for permission to use their works. You should do this if, in your own mind, you get some doubt about if you are usingrepparttar 132007 works fairly. More simply, when you find yourself doing more than including a few brief phrases, lines or a paragraph, then by all means ask.

The standard I like to use is simple. If I am using other's words to help illustrate or reinforce a point that I am making, then it's fair use. If, onrepparttar 132008 other hand, I am using other's words to makerepparttar 132009 point itself, well, then perhaps I need to ask permission. Illustration or reinforcement does not generally require many words - making a point often does.

Richard Lowe Jr. is the webmaster of Internet Tips And Secrets. This website includes over 1,000 free articles to improve your internet profits, enjoyment and knowledge. Web Site Address: http://www.internet-tips.net Weekly newsletter: http://www.internet-tips.net/joinlist.htm Daily Tips: mailto:internet-tips@GetResponse.com

Rules To Problem Solving

Written by Richard Lowe

Continued from page 1

Rule #9: Don't assume you don't have a problem either. Again, don't make assumptions. Base your conclusions upon what exists, not what you assume to exist.

Rule #10: Don't assumerepparttar problem isrepparttar 131979 same as an earlier problem. I manage a number of computer systems. One ofrepparttar 131980 functions of these systems is to fax several thousand purchase orders to venders over night. One day someone reported that they could not see any failures, and it's unheard of for no faxes to fail. I assumed. mistakenly, that this was a failure inrepparttar 131981 report, which had happened before. Thus I putrepparttar 131982 incorrect priority onrepparttar 131983 issue and didn't look at it untilrepparttar 131984 afternoon. When I looked, I discovered to my horror that ALL faxes had failed (which causedrepparttar 131985 failure list to fail also, as it made an assumption that at least ONE fax would work). This caused incredible grief which could have been avoided had I actually looked instead of making an assumption.

Rule #11: Don't assume it's a computer error. Not all problems are caused by machines. You could spend countless hours trying to fix something that was actually a data entry error or had some other human cause.

Rule #12: Don't assume it's not a computer error. By now you should thoroughly understand this. Don't make assumptions. Look and form your conclusions based uponrepparttar 131986 evidence that exists.

Rule #13: Don't trustrepparttar 131987 documentation. Use technical documentation as a resource, but do not assume it is correct. Programmers are notorious for allowing their documentation to slip into uselessness. That's justrepparttar 131988 wayrepparttar 131989 world is, so don't beat your head over it. Read any documents you can get your hands on, but also look atrepparttar 131990 code and anything else pertinent.

Rule #14: Don't assume it ever worked. Many years ago, I hadrepparttar 131991 assignment to convert a plotting package from one computer system to another. It appeared to be a simple project (I violated Rule #15) so we just movedrepparttar 131992 code torepparttar 131993 new machine and tried to run it. Several errors occurred (squares not square and triangles not triangular), and these did not occur onrepparttar 131994 original machine. We spent months (literally!) trying to figure out what we did wrong. As it turned out, we violated rule #14. The code was inrepparttar 131995 middle of being modified, andrepparttar 131996 programmer who was doingrepparttar 131997 modifications quit and didn't tell anyone. Thus,repparttar 131998 code we were using never worked, and thus, well, we didn't do anything wrong. Once we hadrepparttar 131999 proper code (from an old backup) it really was very simple.

Rule #15: Don't assume it's simple or complex. Just remember it is what it is. Some problems are simple and some are complex. Don't assume either until you have done your analysis.

Rule #16: Don't assume maliciousness. If you find a human error, don't assume it was malicious. Generally, human errors arerepparttar 132000 result of incompetence -repparttar 132001 person did not understand what he or she was doing. Start with training to correct human errors - you can move to harsher methods later if training doesn't work.

I hope these rules are of value to you in your problem solving endeavors.

Richard Lowe Jr. is the webmaster of Internet Tips And Secrets at http://www.internet-tips.net - Visit our website any time to read over 1,000 complete FREE articles about how to improve your internet profits, enjoyment and knowledge.

    <Back to Page 1
ImproveHomeLife.com © 2005
Terms of Use