Architected Futures™

Tools and strategies ... for boiling the ocean

Content Architecture

Content Architecture

Every item in the EATS knowledgebase is defined as an Element, including relationships. Content, utilimately, is a large set of element specifications, each with a GUID and a Type, where the type is an element with its own GUID. And the types each have a specification in the knowledgebase. Core processes within EATS "understand" the semantics of core types.

The diagram above depicts the EATS infrastructure's fundamental concept of how different element types are related to form models of more complex types by "reading" and applying semantics between elements. Currently, relational semantics are viewed in three categories:

  1. The relationship defines how one element is associated with another as a property or characteristic aspect. 
  2. The relationship defines a fundamental, semantic association between two elements.
  3. The relationship defines how the element participates as a component in a more complex element set.

Relationship Schemes

Relationships are defined as predicates, with predicate types used to interpret relationships between other elements, rules and instance (model) specifications for the nature of the model defined by the relationship.

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.