TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Web Legal Issues From:Barbara Karst-Sabin <barbara -at- QUOTE -dot- COM> Date:Thu, 7 Jan 1999 13:30:24 -0800
What Bob says is, of course, true. One of the way most web designers or
web document producers has learned their trade is by following other
people's examples. It's an efficient way to operate.
However, having said that, I can tell you that I have seen pages that
did something I liked, so I tried to view the source code. Well, the
code is there, alright, but it was just a matter of calling up a series
of files. The whole code for a fairly complex and "active" page was a
matter of about 12 lines!!! If you really don't want people to see how
you did something, you can always do that. But I'd be more likely to be
pleased that someone thought they could learn from me.
BJ
Robert Maxey wrote:
>
> >><snip>
> >>When I created my Web pages, I did not create the browser that allows
> >>anyone to look at source code. Having the ability to look at source code
> >>does not give you the right to lift it and use it as your own.
> Netscape's
> >>browser design does not supercede federal copyright law.
> <snip>
>
> The above is an example of a big problem with the Web. If you look at any
> of the hundreds of books written about the Web, the idea of looking at the
> HTML to see how others did something, and then using the same structure and
> ideas is stressed quite a bit.
