A communication protocol is not an abstract concept but a very
concrete thing: e.g. when you receive "A" you must reply "B". Very
rigid and very concrete!
It is an abstract concept, since it is defined by thoughts. While a
written spec might a concrete instance and protected by copyright lows,
the concept might not be projectable. Since a protocol is quite likely
no algorithm, it additionally doesn't fall to software protection laws.
My english might be not good enough, but the this - regarding copyright
law - a significant difference.
I was under the impression that the same was true in the U.S. Short of being
granted a patent, I don't think a protocol can be protected. Again, look at
the WINE example. Or any of the .NET clones. (I believe there are several
now.)
Of course that wouldn't prevent a company from trying to protect it, the
deeper pockets theory.
Daniel L. Taylor
Taylor Design
Computer Consulting & Software Development
[EMAIL PROTECTED]
www.taylor-design.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
