[Sigia-l] Binary data > Information > Content > Copyright
Listera
listera at rcn.com
Sun Mar 26 22:52:09 EST 2006
What happens to digital bits (data) when they are interpreted to become
"information" is a perennial topic of debate here.
For those interested in this subject (and I know there are a few here)
here's a pretty fascinating article/experiment exploring what happens to
binary data, its analog representation, transitional states between
analog/digital, the legal concept of copyright, our general perception of
"copying", etc:
Monolith is a simple tool that takes two arbitrary binary files (called a
Basis file and an Element file) and "munges" them together to produce a Mono
binary file (with a .mono extension). Monolith can also reconstruct an
Element file from a Basis file and a Mono file.
In most cases, the resulting Mono file will not be statistically related to
either file. If you compare the Mono file to the Element file, the Mono file
will contain none of the information present in the Element file. In other
words, the Mono file by itself tells you nothing at all about the data in
the Element file. Only when combined with the Basis file will the Mono file
provide information about the Element file.
Monolith can be used for exploring the boundaries of digital copyright, and
the rest of this website is devoted to such an exploration. The core
questions: What happens when we use Monolith to munge copyright files?
<http://monolith.sourceforge.net/>
----
Ziya
"If you can't feed a team with two pizzas, the size of the team is too
large."
More information about the Sigia-l
mailing list