Knowledge Architect/Baseline/Standards


Knowledge resource sharing cannot happen in isolation. Sharing requires compatibility, at many levels, including:

  • data (e.g. content, knowledge, information, representation)
  • meta-data (authorization, classification, identification, cryptography, document structure, etc)
  • platform (ex: SOA, J2EE, .NET, Web)
  • environment (ex: network, protocol, interfaces)

While, at some of these levels, some standards support some effective compatibility, at other levels, especially at the meta-data level, there is much left to do to support a knowledge economy, where a universal knowledge resource entitlement, modeling, management, and sharing platform is required.

To effectively achieve such a platform, compatibility is required across vendors, infrastructures, computing platforms, applications, legal (ex: jurisdictions) and political structures (ex: countries), as well as organization and departmental walls, which can only be enabled by appropriate structured standards.

Ensuring standards specifications coherence and completeness is a sophisticated process that, especially in this case, requires clear and deep understanding of knowledge architecture and its fundamental structuring principles, as well as of related software, application, and technical requirements.

DNAOS and REEMS related work, as provided insightful support to help define and introduce an integrated set of standards specification proposals (e.g. REMMS), initially presented to a few different standards bodies, starting with the OMG (Object Management Group).

In summary, IT majors have been slow to accept the concept of deep, yet enabling, changes to their current offerings, especially to achieve standards-based leveled playing fields.

Seemingly taking recommendations from IT majors, and despite their costs and responsibilities, governments have not yet actively moved forward.

On the other hand, individual and organizational users, as well as the overall world economy are paying a high price for not yet having a common universal collaboration and knowledge sharing platform, typically, often without even fully realizing so.

Accordingly, it now seems crucial to open debate and awareness, as well as to require and demand adequate standards specifications. This is part of the purpose of this document.

While standards proposals cannot be considered here, as a quick reference, some of the main REMMS standardization proposal aspects include:

  • Context-aware rule language (ex: XQuery/XPath)
  • Time-Period Representation (ex: ISO8601)
  • Integrated Spacial Location References
  • Integrated Time-Space Referencing
  • Qualification and Resource Archetype Schema
  • Resource and Identification Schema
  • Classification, Typing, and Meta-data Schema
  • Relational and Entitlement Qualities Schema
  • Capabilities, Behavior, and Orchestration Schema
  • Integrated Authorization Schema
  • Knowledge Resource Exchange and Control Protocol
  • Selective Cryptography and Key Management
  • Modeling and Semantics Framework
  • Smart Layout Template Schema
  • Virtual Profile Schema
  • REMMS Namespaces
  • Tracking schema
  • Document Schema