|
Authored by: Anonymous on Tuesday, May 08 2012 @ 11:09 AM EDT |
By its legal definition in US copyright law, SSO is non-literal. The term was
coined to represent the non-literal elements of a "computer program" -
procedural code at the time.
It's not the names - those are literal elements, and aren't protected by
copyright anyway. It's the principles of organization: what you choose to
abstract and where you draw the lines for your classes. Examples would include
things like: whether you abstract the loading of a class into a ClassLoader or
include the functionality to load a class in Class object or an Object object,
or what you include in an object that represents the System vs. what you make
available in more specialized units of abstraction (Errors, for example).
This is what makes is a difficult concept to grasp, and also makes it fairly
obvious that it's not something that should be protected in an API.[ Reply to This | Parent | # ]
|
|
|
|
|