Tools/Solution/Operations/Implementation

Knowledge Architecture Tool Implementation Guidelines

  • Semantics:Knowledge Architecture Operations proposed here, integrate three logical paradigm layers, where building on a strong processing framework and a natural knowledge paradigm, a structuring modeling semantics layer supports the architecture and modeling operations. These semantics play a fundamental role in the modeling, projection, execution, integration, exchange, and governance operations
  • Internal Representation:Although existing operational prototypes use XML as a foundational internal representation, remain implementation-dependent and be left to implementors to decide and support. Accordingly, compliance should focus on functional, notational, and semantics support
  • Model Exchange:Circular Modeling, with flexible and extensible notation support, provide basic keys to model exchange. Common semantics and context rules, as well as compatible viewpoints, and perspectives are also key. Entitlement and sharing principles complete model exchange foundations
  • Context Rules:Context rules are fundamental to knowledge architecture, as well as to entitlement, orchestration, conditions, and execution. Their exchange and applicability rely on their effective representation. Current operational prototypes use primarily XPath2, but also support XQuery as well as SQL for relational database persistence rules. Ideally, they should probably be implementation-dependent but important compatibility issues may impose specification requirements. In any case, XPath2 has proved powerful, context-aware, flexible, and efficient.
  • Specifications:Knowledge architecture tools require effective standards and specifications. The work of thew OMG AESIG is notable and crucial. The AESIG may not, at this point yet, have the required mandate and resources to provide all the required specifications. Accordingly, the REMMS proposal recommends a separate specification set to more appropriately address knowledge and information sharing, entitlement, access control, security, privacy, rights, privileges, and responsibility related issues and specifications. Complementary to the AESIG REMMS proposal, a separate REMMS entitlement proposal is being presented to the OMG.