OpenOntologyRepository Architecture/GettingOrganized

= OpenOntologyRepository_Architecture and API Organizing Plan =

The organizing plan is to develop the specification in stages/phases, moving from the general to the specific as agreement is reached.

The general operating paradigm is anticipated to include the following steps for each stage/phase. The actors are the workshop chair (or co-chairs), scribe (recorder) and participants.

Specification Development Process

 * A draft structure (for the particular phase or level) will be presented by the workshop chairs as a general overview.
 * The overall structure will be discussed and revised as needed.
 * Then piece by piece, the individual components, their interactions and dependencies will be discussed, revising, adding to, or deleting until there is initial consensus (of the meeting participants).
 * During this process the scribe records the justification for each change, deletion or revision (tedious but vital for capturing the rationale).
 * All decisions will be consistent with the goals of the OOR, its architecture principles, and priorities.
 * (English) Terminology will used that is most descriptive and consistent with the action, activity, or operation of the component or interface.
 * When the revisions to an entire stage or level are completed, which may take more than one workshop to complete, the final/revised draft will be posted for a comment period of no more than 2 weeks.
 * In the next meeting following the closure of the comment period all posted comments will be reviewed and voted on for inclusion or rejection.
 * Each action will be supported by an explanation for the action, and recorded by the scribe.
 * After all comments are acted upon, that stage of the specification will have become finalized (for the current version).

Specification Development Plan
The first of the OOR specification workshops will focus on the system view. At this stage, or level of granularity, the major components or sub-systems that will comprise OOR will be identified along with their interactions and dependencies.

Each sub-system will in turn be decomposed into its sub-systems or components.

When needed, interfaces will be specified for the component or sub-system.

The systems level view will include the major sub-systems and their interactions and dependencies. These sub-systems will represent the (representation language independent) capabilities of the OOR and be described in the language most descriptive of the activities the sub-system supports or provides.