Workflow Perspectives on the Open Semantic Framework AI3:::Adaptive Information.

Advances in How to Transfer Semantic Technologies to Enterprise Users

For some time, our mantra atStructured Dynamics has been, “We’re successful when we are not needed.[1]“

In support of this vision, we have been key developers of an entire stack of semantic technologies useful to the enterprise, theopen semantic framework (OSF); we have formulated and contributed significant open source deployment guidance to the MIKE2.0 methodology for semantic technologies in the enterprise calledOpen SEAS; we have developed usefulstructured data standards and ontologies; and we have made massive numbers of free how-to documents and images available for download on ourTechWiki. Today, we add further to these contributions with our workflows guidance. All of these pieces contribute to what we call thetotal open solution.

Prior documentation has described the overallarchitecture orlayered approach of theopen semantic framework (OSF). Those documents are useful, but lack a practical understanding of how the pieces fit together or how an OSF instance is developed and maintained.

This new summary overviews a series of seven different workflows for various aspects of developing and maintaining an OSF (based on Drupal)[2]. In addition, each workflow section also cross-references other key documentation on theTechWiki, as well as points topossible tools that might be used for conducting each specific workflow.

Overview

Seven different workflows are described, as shown in the diagram below. Each of the workflows iscolor-coded and related to the other workflows. The basic interaction with an OSF instance tends to occur from left-to-right in the diagram, though the individual parts are not absolutely sequential. As each of the seven specific workflows is described below, it is keyed by the same color-coded portion of the overall workflow.

Each of the component workflows is itself described as a series of inter-relating activities or tasks.

Continues @http://www.mkbergman.com