Seattle Method

A subject matter expert (SME) and a software application agree on a common representation of knowledge, a conceptualization , using global open standard technical formats such as XBRL, RDF+OWL+SHACL, or GQL. That means that rather than embedding subject matter logic within the code of a software application; that logic can be separated from the software application.  This makes both that common representation of knowledge more useful and modifications to the software easier. This distinction (i.e. separating knowledge and code) makes knowledge based systems very different from typical software applications. The architecture of a knowledge based system explicitly separates knowledge from software code. This is done by representing knowledge declaratively rather than as part of procedural code. This separation of knowledge and code and representing that knowledge declaratively also makes that knowledge more broadly usable. This types of systems have been referred to as "expert syst...

Conceptualization is the process of identifying, abstracting, and organizing a coherent set of concepts and relationships that represent the essential important elements, relationships, and possible states of affairs within a given subject domain (a.k.a. area of knowledge , field, universe of discourse). It transforms the complexity of reality into structured ideas that can be shared, discussed, analyzed, and modeled. A conceptualization is intended to be understandable by humans (the community of subject domain stakeholders) but can also be represented in machine interpretable form. Conceptualizations are social artifacts, sociotechnical tools. A conceptualization serves as a shared understanding among domain stakeholders, enabling them to articulate and reason about the subject domain in consistent, meaningful, and useful ways. It captures not only what exists, but also what could possibly exist by defining the admissible configurations, constraints, mechanics, and dynamics of that...