OOR/ConferenceCall_2011_03_04
http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_03_04 (01)
OOR Architecture & API Specification Development Workshop (02)
Co-chairs: KenBaclawski & ToddSchneider (03)
The upcoming 4 March 2011 OOR Team conference call will be
the first of several meetings to produce the actual OOR
specification. It will be run as a workshop where a draft or
straw man proposal will be discussed, modified as needed and
decided upon. (04)
The organizing plan is to develop the specification in
stages/phases, moving from the general to the specific
as agreement is reached. (05)
The general operating paradigm is anticipated to include
the following steps for each stage/phase. The actors are
the workshop chair (or chairs), secretary (recorder) and
participants. (06)
Specification Development Process
---------------------------------
0) A draft structure (for the particular phase or level)
will be presented by the workshop chairs as a general
overview. (07)
1) The overall structure will be discussed and revised as
needed. (08)
2) 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). (09)
2.1) During this process the secretary records the
justification for each change, deletion or revision
(tedious but vital for capturing the rationale). (010)
2.2) All decisions will be consistent with the goals of the
OOR, its architecture principles, and priorities. (011)
2.3) (English) Terminology will used that is most
descriptive and consistent with the action, activity,
or operation of the component or interface. (012)
3) 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. (013)
4) In the next meeting following the closure of the comment
period all posted comments will be reviewed and voted on
for inclusion or rejection. (014)
4.1) Each action will be supported by an explanation for the
action, and recorded by the secretary. (015)
4.2) After all comments are acted upon, that stage of the
specification will have become finalized (for the
current version). (016)
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. (017)
Each sub-system will in turn be decomposed into its
sub-systems or components. (018)
When needed, interfaces will be specified for the component
or sub-system. (019)
OOR Specification Workshop I
------------------------------------------------------------
For the first workshop the draft systems level view will be
derived from the candidate material posted to the OOR Architecture
Wiki page (020)
http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Architecture
. (021)
We encourage all to up date your candidate contributions to
ensure your ideas are known and understood. (022)
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 language most
descriptive of the activities the sub-system supports or
provides. (023)
Note that the process and actual plan are subject to
change as we proceed (and learn more). (024)
Todd (025)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-dev/
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-dev/
Shared Files: http://ontolog.cim3.net/file/work/OOR/dev/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (026)
|