This document presents schematic description of the requirements for a TUNES system architecture. This is a working draft, designed to provide precise technical feedback to TUNES project members as design issues are resolved. Implementation strategies are suggested, but not specified.
This document specifies the basic requirements required to satisfy the definition of a TUNES system as set out at the TUNES Project website http://www.tunes.org/. This is not a tutorial or an implementation guide, although suggestions may be made in order to illustrate and coordinate ideas.
The TUNES Project has existed for many years in an early planning and speculation stage. Several projects exist to advance its goals, but coordination was found to be necessary to help guide the project and solidify the goals.
Since this document is a reference, the order of presentation has not been layed out for introductory purposes.
This document's chapters are separated into levels of detail. Major sections of the system are explained in terms of their core types and operations on those types.
Unlike many standards, which delineate deviation in terms of disallowed behavior within the system under scrutiny, the nature of the TUNES project requires that conformance be tested by verifying that the implementation allows everything specified by the standard. Incompleteness is expressed in terms of possibilities that are not supported.
Specifically, if some element of the specification is not explicitly restricted in its scope, then it should be read as stating that there is no restriction of the scope. The simplest example of this is the type of an object within some role in an operation or other type.
This specification defines a standard subset in various sections which is considered suitable for bootstrapping. This subset may be altered to suit dynamic requirements as the initial construction and bootstrap process proceed.
This specification does not define any other subsets, but defines frameworks for publishing subsets.