Tool Component Requirements

• Meta-data:Knowledge Architecture tools should support modeled resource and modeling component meta-data as modeled resources also. Knowledge Architecture tools should support meta-data modeling as well as the use of that meta-data when modeling resources constrained by that meta-data
• Components:Knowledge Architecture tools should support that modeling components are defined and modeled as resources. Their specification and standardization should also specify their extendability (eg: color, image, assets), as well as support non standard components (just as new words can be added to natural languages, with the clear understanding that its universal recognition is not guarantied). While Knowledge Architecture tools define and control a common vocabulary (e.g. core) and its extension, they must also support extensions, integrating new ones to the core as required and agreed
• Rules:Knowledge Architecture tools should support declarative rules and rule modeling for the rules assigned to modeled resources and modeling components. Rules should also be modeled as other modeling components
• Indicators:Knowledge Architecture tools should support key indicators so that, for example, one can attach a key dynamic indicator to a modeling component (e.g. class, object, actor, relation, use case, process, service, etc), or resource, so that the indicator can dynamically report some context statistics for that component/resource
• Relations:Knowledge Architecture tools should provide built-in support for complex relations like entitlement, responsibility, origin (e.g. source, provenance), access, etc., for all modeled resources and modeling components. These relations are indispensable, for example, for sharing models, especially in open (e.g. Web, LOD, multi/inter-organization) type environments
• Roles:Knowledge Architecture tools should support that roles are fundamental and apply to resource contributions to relations. Consequently, roles are associated with expected behaviors (e.g. action sequences), for example, as in the common case of actors which are roles, fulfilled by resources in use case relations, with associated behaviors (e.g. use case action sets, and conditions)
• Identification:Knowledge Architecture tools should provide identification and identification namespace support for each and every modeled resource and modeling components, from the simplest to the most complex resources, as otherwise managing it is an issue
• Classification:Knowledge Architecture tools should support that classification is a relation to meta-data, and meta-data, as noted before, is a modeled resource. Knowledge Architecture tools specify the core assets (e.g. meta-data, classification) as well as meta-data and classification extensibility, for modeled resources and modeling components