Knowledge Architect/Basics/Structure/Classification


In addition to the general public-class segment of the “primary key” type identifier, resources typically have as many classification and typing qualities, simple and/or compound, as required.

While classification is a grouping criteria definition process, and as structural similarity (e.g. type) association is common and useful, classification/typing qualities are often associated with meta-data resources that typically define common qualified structures, including system, required, recommended, optional, and annotational qualities, reference and range bindings, defaults, constraints, rules, conditions, documentation, etc.

Flexible classification and qualified mete-date also provide support for archetypes, which are key for generalizing resource processing, transformation, management, and sharing.

Unlike many still popular environments (ex:. OO) that require “compile time” meta-data definitions and bindings, knowledge architecture rather requires dynamic “run-time” resource typing/classification, where, under adequate entitlement (See Entitlement, below) resources can be dynamically assigned single or multiple types and classes, and where the associated meta-data is defined in meta-data resources that can also be processed and transformed, as required, dynamically, at “run-time”, under appropriate entitlement.