I would like to use the text i/o portion of the OOC library as the API.
This library would use the file prefix "OOC" to distinguish its modules
and identify its heritage.

Module OOCChannel
-define the abstract types Channel, Reader, Writer

Module OOCFiles
-define the abstract classes File, Reader, and Writer that are extensions
of their counterparts in OOCChannel
-define hidden concrete extensions of File, Reader, and Writer for the
following types of files:
-ASCII text files. ie. native OS text files
-text documents of the target Oberon system. For instance,
V4 Text files, BlackBox .ODC files, etc.
(Implementation would use the highest level classes available
in the target Oberon system. eg Texts in V4, etc)
-locator procedures would create a File object appropriate to the
type of file being accessed.

Module OOCTexts
-define the abstract classes for accessing plaintext in the Text
object of the target Oberon system. eg. TextModels in BlackBox,
Text in V4, etc
-these classes (Text, Reader, and Writer) would be concrete extensions
of their counterparts in Channel
-locators will be available to "open" the current frame, or the selected
text, etc

Modules OOCTextRider and OOCBinaryRider
-define mapper classes that can connect to any OOCChannel
-should be usable with only minor changes from OOC library version

Module OOCProgramArgs and OOCStdChannels
-I'm not sure if these notions exist in most Oberon system?

Module OOCLogs
-support writing to the Log via a OOCChannel