...
In the abstract classes, most non-OSID methods including its constructors are protected. You should have the ability to encapsulate whatever logic you like or override or constrain any behavior. A concrete class decides what will be visible outside the package.
Yes, Java Has
...
an Import Statement
But it gets bloody confusing between the OSID Java interfaces, implementations classes, other Java interfaces in this framework, and external tools. As it turns out, there's useful information in the package name (not all of it) and it's important to always know where the OSID is.
...
It happens. Within a functional area in Jamocha, OSID Java interfaces are often used compositionally or as decorators in lieu of defining a custom interface that does the same thing only more specific to our implementation (as opposed to consuming OSIDs through the OSID Runtime in which case they are OSID Adapters). OSIDs exceptions don't always apply in certain cases where it is known that it either can't happen or it doesn't matter.
Implement Statements Repeated Up
...
the Class Hierarchies
Wanted to make it clear what OSID Java interface was being implemented.
...