RE: SCO's infringing files list

["David Schwartz" <davids@webmaster.com>]

	These files seem to mostly include information from standards documents and
most likely contain insufficient original creative content to justify
copyright protection. The particular order in which one lists the defines or
the numbers one assigns to them don't seem to be protectable to me, there's
no expression in them.

	I had a similar issue in a code review. In this case, the relevant RFC
actually named the constants and gave their numerical values. The numerical
values are used in the protocol and it's logical for multiple independent
groups to both choose to use the same names used in the RFC. So our code had
one header file -- a list of '#define's with the same names and numbers as
someone else's code (and the same as the RFC, of course). And guess what, we
both put them in numerical order too!

	Not bothering to look at the RFC, the code reviewer concluded that the
identical symbol names must have meant one of us took code from the other.
Duh.

	DS