https://ontologforum.com/index.php?action=history&feed=atom&title=OpenOntologyRepository_Architecture%2FGettingOrganized 2026-04-24T20:33:10Z Revision history for this page on the wiki MediaWiki 1.39.0 https://ontologforum.com/index.php?title=OpenOntologyRepository_Architecture/GettingOrganized&diff=2241&oldid=prev 2015-12-14T07:15:58Z

<p>Last updated at: 2011-03-02 08:16:30 By user: PeterYim</p> <p><b>New page</b></p><div>= [[OpenOntologyRepository_Architecture]] and API Organizing Plan =<br /> <br /> The organizing plan is to develop the specification in stages/phases, moving from the general to the specific as agreement is reached. <br /> <br /> 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. <br /> <br /> == Specification Development Process ==<br /> <br /> * A draft structure (for the particular phase or level) will be presented by the workshop chairs as a general overview. <br /> * The overall structure will be discussed and revised as needed. <br /> * 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). <br /> ** During this process the scribe records the justification for each change, deletion or revision (tedious but vital for capturing the rationale). <br /> ** All decisions will be consistent with the goals of the OOR, its architecture principles, and priorities. <br /> ** (English) Terminology will used that is most descriptive and consistent with the action, activity, or operation of the component or interface. <br /> * 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. <br /> * In the next meeting following the closure of the comment period all posted comments will be reviewed and voted on for inclusion or rejection. <br /> ** Each action will be supported by an explanation for the action, and recorded by the scribe. <br /> ** After all comments are acted upon, that stage of the specification will have become finalized (for the current version). <br /> <br /> == Specification Development Plan ==<br /> <br /> 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. <br /> <br /> Each sub-system will in turn be decomposed into its sub-systems or components. <br /> <br /> When needed, interfaces will be specified for the component or sub-system. <br /> <br /> The systems level view will include the major sub-systems and their<br /> interactions and dependencies. These sub-systems will represent the<br /> (representation language independent) capabilities of the OOR and be described<br /> in the language most descriptive of the activities the sub-system supports or<br /> provides. <br /> <br /> [[Category:OOR]]<br /> <br /> <br /> <br /> </div>

imported>PeterYim