From: "Roy Roebuck at OWIS" <email@example.com>
I'm unsure what caused my other email client to send encrypted text, so I've used a second client.
I agree that a globally scalable DKR, and thus a design for this DKR is a high priority of the UnRev. In conjunction with the DKR, we also need a DKR-based capability to manage dynamic improvements at the scale ranging from the individual to the species. As part of this, we need a PKI-based mechanism to managed identities, associations, and the changes to them.
The following concepts and designs are further explored at my site (http://one-world-is.com/rer/owis/). I recommend that an object management system (e.g., my General Enterprise Dynamic Object - GEDO) underlying the DKR provide the ability to manage named objects in a hierarchical namespace, manage associations between the namespace entries, and manage changes in entries and associations, to provide "context engine" capability for specific and universal knowledge domains (as in a UnRev Networked Improvement Community and MetaNIC). See http://www.one-world-is.com/rer/owis/dem/slides/sld033.htm. Over the past 17 years I've refered to the underlying data structures of my GEDO as a "hierarchy/association/change" or "tree/star/arrow" model of abstracted knowledge. It is now most commonly recognizable as a generalized object model, which I apply to achieve what I call "Context Management" to enable "relevant situational awareness" for organizations, groups, and individual persons and mechanisms. "Relevant situ
ational awareness" has also been half-jokingly referred to as "relevant omniscience".
In the same way that the ISO/IEC 13250:1999 TopicMap standard corresponds to a subset of my GEDO, it could provide a partial foundation for colloquium or general purpose DKR (see http://www.infoloom.com/ and http://www.topicmaps.com/), as could the general object model of the OpenGroup and Object Managment Group's (http://omg.org) Distributed Management Task Force's (DMTF) Common Information Model's (CIM) metaschema (http://www.dmtf.org/spec/cim_spec_v22/#_Toc453584954); the LDAP Object Model (http://www.ldapcentral.com/); XML/XLL/XSL and XMI (http://www.w3.org/XML/); InfoMap Multicentric Information Map (http://www.multicentric.com/); a Natrificial Brain (http://www.thebrain.com); a MindMan MindMap (www.mindmanager.com)? Another group I'm affiliated with (http://www.ms.lt/) is seeking to define an interchange method between some of the various knowledge tools/stores using XML.
The General Enterprise Management (GEM) tree underlying GEDO represents a hierarchy for namespace and categorization management using a root schema of my design (http://one-world-is.com/rer/owis/dem/slides/img034.gif) (i.e., a superset variation of LDAP V3's schema), with freeform and inherited attributes for each hierarchy class or instance entry, now enabled by XML. A useful analogy for the namespace tree of an enterprise is a book's Table of Contents.
The star represents freeform associations (e.g., sequentiality =predecessor/successor, containment =distribution/composition) between entries in the hierarchy, and freeform attributes describing the associations. This would include quantitative and chronological attributes to support general purpose and specialized "resource management" and "requirement management" functions, with TopicMaps, XPath, and XPointer providing the enabling technology. A link to a "system of record", document, or other data source would provide a "snowflake" view of information around an object's tree entry or star/profile. The snowflake corresponds to the Topicmap "occurence". A useful analogy for the namespace entry associations of an enterprise is a book's Concordance (e.g., simple and categorized alphabetical index, word/phrase context mapping, etc.) or a plan/budget requirement specification.
The arrow represents the "change management" function of the tree and star, whereby one could track the history of the tree and star for analytical purposes, project future tree and star changes for program/budget and strategic planning, or project situational changes for simulations and contingencies. XSLT technology would provide the filtering/sorting functionality necessary to view selective portions of the information products in the required order. A useful analogy for the namespace entry and association change funciton of an enterprise is a book's "Version Control" system, or a plan/budget schedule or projection.
I attach a generalized enterprise strategic management application of my design, reverse engineered from a highly benchmarked manual process (http://one-world-is.com/rer/owis/bei/slides/sld010.htm), to provide a dynamic strategic management capability. See http://one-world-is.com/rer/owis/bei/slides/sld012.htm. The GEDO also serves as a multidimensional datawarehouse that provides operational data for integrating and migrating functional information systems. See http://one-world-is.com/rer/owis/dem/slides/img077.gif
I refer to the information that the above products and methods are intended to manage as "multidimensional information". See http://www.one-world-is.com/rer/owis/dem/slides/sld090.htm. I also describe the archtype information products as structured, semistructured, and unstructured. Raw and unstyled text is unstuctured, as are images and sound without tags/indeces. Tagged information products are semistructured (as in XML without a DTD or DCD, in HTML, text with assigned styles, and images/audio with tags/indexing). Structured information products are tagged products (with the product "container" being the top or root tag and having some positive number of other internal tags) with a defined organization (as in a DTD/DCD, XML-Schema, or a database or directory schema).
One World Information System
Manager, DoD Electronic Business/Electronic Commerce Next Generation Architecture and Infrastructure Task Order
Community email addresses:
Post message: unrev-II@onelist.com
List owner: unrev-IIfirstname.lastname@example.org
Shortcut URL to this page:
This archive was generated by hypermail 2.0.0 : Tue Aug 21 2001 - 18:56:39 PDT