Concept "Top-Level-Ontology"

From SMW CindyKate by dataspects
Component 601318
Jump to navigation Jump to search
[edit]
Keywords/Contexts

Ontology

Annotations
{{#compound_query:Component 601318Property "-Has subobject" has a restricted application area and cannot be used as annotation property by a user.UseCaseMotivation;?HasDirection;?IsMotivating;?IsMotivatedBy;?HasReasoning
Property "-Has subobject" has a restricted application area and cannot be used as annotation property by a user.Concept "Top-Level-Ontology";?HasDirection;?IsMotivating;?IsMotivatedBy;?HasReasoning Property "-Has subobject" has a restricted application area and cannot be used as annotation property by a user.Concept "Top-Level-Ontology";?HasDirection;?IsMotivating;?IsMotivatedBy;?HasReasoning
name=MotivationsDeclaredOnThisPageResultItem|link=none}}
Motivations
Lua error in Module:Motivations at line 23: attempt to concatenate field 'hasReasoning' (a nil value).
[edit]

Content


Ultimate Goal

Keep domain knowledge consolidated, coherent, accessible and clean

If a domain specialist adds something to the domain, then…

  1. …how should it be called/named/labeled?
  2. …how should it be integrated/linked?

Fundamental Goal "Separate abstract components from concrete components"

What's the assumed difference between abstract and concrete components?

If someone asks you to point out X, can you point your finger at something and say "This is X."?

If no, then X is something abstract.
If yes, then X is something concrete.
Notice:

For example, the Aspect "Safety" of a car cannot be instantiated like "This is safety A and that is safety B.". But the Aspect "Safety" enfolds the instantiations Seatbelt "Model 24" and Airbag "RT45".

What are abstract components?

An abstract component is of component type "Facet" whose own facet type can designated a facet (by default), or more specifically an aspect, a topic, a system, a context, a scope, a showcase, a domain, a concept or a group, which is

  • constituted by properties (having any or specific subject and/or object value(s))Component 601318 Footnote {{#counter:footnotes}}Property "CiteRef" (as page type) with input value "Component 601318 Footnote {{#counter:footnotes}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.{{#scite:Component 601318 Footnote {{#counter:footnotes}}|type=footnote|citation text=See Organization Pattern "Three-Structure-Grades-Method"}}

and

  • consists of implicit groups of components (and their interrelations)

and

  • can be reified, e.g. the Aspect "Safety" can have the properties "Has priority::Top" and "Is assigned to::Mark".

Facet "Facet Types"

Facet TypeFacet
FacetFacet
FacetFacet "Fully Automatic Verified Backup-Restore Loop Setup"
FacetFacet "SMWCK IT System"
FacetFacet "Testing"
FacetFacet "Component Types"

What are concrete components?

A concrete component is of any single component type (other than "Facet"), and that single component type is in accordance with domain-agnostic general common-sense understanding as it would be used if “met-on-the-floor”.

Fundamental Goal "Separate what's domain-agnostic from what's domain-specific"

About component types

Components instantiate a single domain-agnostic component type. A type can have multiple synonymous designations.

Here's the list of component types asserted on SMW CindyKate:

Type "SMW System Profile", Type "Facet/Interface", Type "Publication", Type "Illustration/Graph/Diagram/Mind Map"

Notice:

There is more explanation on this in Component 153600 Use Case.

About component roles

Components can assume domain-specific roles. A role can have multiple synonymous designations.

Here's the list of component roles asserted on SMW CindyKate:


An example comparing component types to component roles

The following diagram depicts that a woman…

  • …can, without context, be identified as a person. So "person" is a context-independent generic type.
  • …can, by considering a context, be identified as a mother. So "mother" is a context-dependent role.

Component 571934.png

Facet "Role Assumptions"

Here's the list of role assumptions asserted on SMW CindyKate:

Role… …is assumed by… …in context… …characterized by…

Fundamental Goal "Component titles that read naturally"

Because it supports quick understanding, it is natural for people to prepend something they refer to by that thing's type or role.

So, instead of just saying

SMW's three-ontologies-method,

it is more useful to state

SMW's Organization Pattern "Three-Ontologies-Method".

Fundamental Goal "Account for synonyms"

See Make it easier for your employees to get used to your organization's vocabulary for beackground reasoning.

Here's the technical setup for component type title synonyms:

<wikitext2 page="Template:Component Type"/>

<wikitext2 page="Template:Synonym"/>

Asserting things

How is a component type asserted/instantiated?

<wikitext2 page="Component Type 431042"/> <wikitext2 page="Template:Synonym"/>

<wikitext2 page="Template:Component Type"/>

How is a component asserted/instantiated?

<wikitext2 page="Component 723082"/>


As you can see, this storage consists of 3 things:

  1. an instantiation of Template:Component
  2. an instantiation of Template:Component Type 431042
  3. free text

In Template:Component on the right, we query the Component Type's synonymous titles.

<wikitext2 page="Template:Component"/> <wikitext2 page="Template:Component Type 431042"/>