Concept "Top-Level-Ontology"

From SMW CindyKate - Main
Component 601318
Jump to: navigation, search

Content


Ultimate Goal

Procure understanding by facets

Semantic webs must procure domain understanding by presenting explanatory facets of the domain's components.

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

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
ContextContext "Marketing"
FacetFacet "Component Types"
FacetFacet "SMWCK Main"
FacetFacet "Learn how working with SMW heeds fundamental knowledge and information management principles"
FacetFacet "Fully Automatic Verified Backup-Restore Loop Setup"
FacetFacet "Flaws"
FacetFacet "BlueSpice Testing"
FacetFacet "SMWCK IT System"
FacetFacet "Testing"
FacetFacet "HRMR Graduates for second round"
FacetFacet "Print PDF example"
FacetFacet "HRMR HRM Recruitment"
Gantt ChartGantt Chart "ISS Flights by Astronaut"
Gantt ChartGantt Chart "ISS Expeditions by Astronaut"
Gantt ChartGantt Chart "ISS Flights and Expeditions by Astronaut"
GroupGroup "Crew Vehicle Flights"
InterfaceInterface "Notices"
InterfaceInterface "Someone is doing something somewhere"
InterfaceInterface "Frequently Asked Questions (FAQ)"
InterfaceInterface "Use Cases"
InterfaceInterface "Floating Properties"
OntologyOntology "NASA ISS FPIP (Flight Planning Integration Panel)"
OntologyOntology "Field of Application NASA"
ShowcaseShowcase "Using Cargo and mermaid to derive NASA's FPIP from SMW-managed semantic data"
SystemSystem "KIM/SMW Academy Syllabus"
Discuss UseCase "Manage MediaWiki-centric enterprise knowledge management"Topic "Semantic MediaWiki Browser Testing"
Wikitext PosterWikitext Poster "Ontologization"
Wikitext PosterWikitext Poster "Top-Level-Ontology"

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 "Computer/Server/Workstation", Type "Content Module", Type "Cucumber Playbook", Type "Data Location", Type "Domain/Scope/Group", Type "Facet/Interface", Type "File Set", Type "Illustration/Graph/Diagram/Mind Map", Type "Organization Pattern", Type "Practice Pattern/Workflow/Maintenance", Type "Publication", Type "Repository/Building Block", Type "SMW Facet Profile", Type "SMW System Profile", Type "Test Script/Use Case/Manual/Action", Type "Utility Template", Type "Web Service"

Notice:

There is more explanation on this in Discuss UseCase "Manage MediaWiki-centric enterprise knowledge management" 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:

Template:Component Type (edit)
{{Template:{{{Component Domain}}}}}
<i class="fa {{{FA Icon|fa-circle}}} fa-3x"></i>

<i class="fa fa-info-circle fa-3x"></i> [short description::{{{Component Type Short Description|}}}]

{{#ifeq:{{{Component Type Show Default Components List|True}}}|True|
= Instantiations/Components =

{{{!}}class="sortable wikitable smwtable jquery-tablesorter" width=100%
!Component
![703543|Keywords]
{{#ask: [component type::{{PAGENAME}}]Has release status::Released
|mainlabel=
|?Is content type
|?Has semantic display title
|?Has keyword
|format=template
|template=Component Type Instantiations Results Template
|sort=Has semantic display title
}}
{{!}}}
|}}

= Profile =

{|class=lcc_structured_data_table
![703543|Keywords]
|{{#arraymap:{{{Component Type Keywords|}}}|;|@@@@|[keyword::@@@@]|,&#32;}}
|-
!Domain
|[[{{{Component Domain}}}]]
|-
!Synonymous Titles
|{{{Component Type Title Synonyms}}}
|-
!Related Files
|
* [[Form:{{PAGENAME}}]]
* [[Template:{{PAGENAME}}]]
|-
|colspan=2|<div class="lcc_structured_data_table mw-collapsible mw-collapsed">
'''[385402|Floating Properties]'''
<div class="mw-collapsible-content">
{|class="sortable wikitable smwtable jquery-tablesorter" width=100%
!Name
!Value(s)
{{#ask: [floating property context::{{PAGENAME}}]
|?Has floating property name
|?Has floating property value
|format=template
|template=List Floating Properties Table Row 2
|link=none
}}
|}
</div>
</div>
|}

{{#ifeq:{{{Component Type Show Default Components List|True}}}|True|
<headertabs />
|}}

{{#vardefine:semantic_title|{{#ask: [subobject::{{PAGENAME}}] Is subobject type::Component Type Title Synonym
|?Has component type title synonym
|format=list
|template=Inspect Synonym
|link=none
|sep=/
}}}}

{{#set:Belongs to domain={{{Component Domain}}}}}
{{#set:Has semantic display title=Type "{{#replace:{{#replace:{{#var:semantic_title}}|SMW::on|}}|SMW::off|}}"}}
{{#set:Has fa icon={{{FA Icon|fa-circle}}}}}
<includeonly>
{{#if:{{{Component Type Category|}}}|[[Category:{{{Component Type Category}}}]]|[[Category:Component Type]]|}}</includeonly>
<noinclude>[[Category:3OM-TopLevelOntology‎-Template]][[Category:ClassTemplate]]</noinclude>
Template:Synonym (edit)
{{{Synonym Title}}}
{{#subobject:
|Is subobject type=Component Type Title Synonym
|Has component type title synonym={{{Synonym Title}}}
}}

Asserting things

How is a component type asserted/instantiated?

Template:Synonym (edit)
{{{Synonym Title}}}
{{#subobject:
|Is subobject type=Component Type Title Synonym
|Has component type title synonym={{{Synonym Title}}}
}}
Template:Component Type (edit)
{{Template:{{{Component Domain}}}}}
<i class="fa {{{FA Icon|fa-circle}}} fa-3x"></i>

<i class="fa fa-info-circle fa-3x"></i> [short description::{{{Component Type Short Description|}}}]

{{#ifeq:{{{Component Type Show Default Components List|True}}}|True|
= Instantiations/Components =

{{{!}}class="sortable wikitable smwtable jquery-tablesorter" width=100%
!Component
![703543|Keywords]
{{#ask: [component type::{{PAGENAME}}]Has release status::Released
|mainlabel=
|?Is content type
|?Has semantic display title
|?Has keyword
|format=template
|template=Component Type Instantiations Results Template
|sort=Has semantic display title
}}
{{!}}}
|}}

= Profile =

{|class=lcc_structured_data_table
![703543|Keywords]
|{{#arraymap:{{{Component Type Keywords|}}}|;|@@@@|[keyword::@@@@]|,&#32;}}
|-
!Domain
|[[{{{Component Domain}}}]]
|-
!Synonymous Titles
|{{{Component Type Title Synonyms}}}
|-
!Related Files
|
* [[Form:{{PAGENAME}}]]
* [[Template:{{PAGENAME}}]]
|-
|colspan=2|<div class="lcc_structured_data_table mw-collapsible mw-collapsed">
'''[385402|Floating Properties]'''
<div class="mw-collapsible-content">
{|class="sortable wikitable smwtable jquery-tablesorter" width=100%
!Name
!Value(s)
{{#ask: [floating property context::{{PAGENAME}}]
|?Has floating property name
|?Has floating property value
|format=template
|template=List Floating Properties Table Row 2
|link=none
}}
|}
</div>
</div>
|}

{{#ifeq:{{{Component Type Show Default Components List|True}}}|True|
<headertabs />
|}}

{{#vardefine:semantic_title|{{#ask: [subobject::{{PAGENAME}}] Is subobject type::Component Type Title Synonym
|?Has component type title synonym
|format=list
|template=Inspect Synonym
|link=none
|sep=/
}}}}

{{#set:Belongs to domain={{{Component Domain}}}}}
{{#set:Has semantic display title=Type "{{#replace:{{#replace:{{#var:semantic_title}}|SMW::on|}}|SMW::off|}}"}}
{{#set:Has fa icon={{{FA Icon|fa-circle}}}}}
<includeonly>
{{#if:{{{Component Type Category|}}}|[[Category:{{{Component Type Category}}}]]|[[Category:Component Type]]|}}</includeonly>
<noinclude>[[Category:3OM-TopLevelOntology‎-Template]][[Category:ClassTemplate]]</noinclude>

How is a component asserted/instantiated?


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

  1. an instantiation of Template:Component
  2. an instantiation of Discuss UseCase "Manage MediaWiki-centric enterprise knowledge management"
  3. free text

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

Template:Component (edit)
{{#vardefine:domain|{{#show:{{{Component Type}}}|?Belongs to domain|link=none}}}}
{{#ifeq:{{{Component Type}}}|Component Type 558984|{{Template:{{PAGENAME}}}}|{{Template:{{#var:domain}}}}}}
<!--i class="fa {{{FA Icon|fa-circle}}} fa-3x"></i-->

<i class="fa fa-info-circle fa-3x"></i> {{{Component Short Description|}}}

<!--
= Profile =

{|class=lcc_structured_data_table
!width=20%|[703543|Keywords]
|width=30%|{{#arraymap:{{{Component Keywords|}}}|;|@@@@|[[@@@@]]|,&#32;}}
!width=20%|Domain
|width=30%|{{#ifeq:{{#var:domain}}|n/a|n/a|[[{{#var:domain}}]]}} ({{{Component Release Status|Released}}})
|-
!Heeds KIM Principles
|
{{#arraymap:{{{Heeds KIM Principles|}}}|;|@@@@|*[KIM principle::@@@@]|\n}}
!Type
|{{#ask: [subobject::{{{Component Type}}}] Is subobject type::Component Type Title Synonym
|?Has component type title synonym
|format=list
|template=Inspect Synonym 2
|link=none
|sep=/
}}
|}
-->
<!--
= Floating Properties =

{|class="sortable wikitable smwtable jquery-tablesorter" width=100%
!Name
!Value(s)
{{#ask: [floating property context::{{PAGENAME}}]
|?Has floating property name
|?Has floating property value
|format=template
|template=List Floating Properties Table Row 2
|link=none
}}
|}
-->
<!--
= What links here? =

{{Special:WhatLinksHere/{{PAGENAME}}}}

-->
<includeonly>
{{#arraymap:{{{Component Keywords|}}}|;|@@@@|{{#set:Has keyword[email protected]@@@}}|;}}
{{#ask: [subobject::{{{Component Type}}}] Is subobject type::Component Type Title Synonym
|?Has component type title synonym
|format=template
|template=Assign Component Type Synonym As Keyword
}}
{{#set:Belongs to domain={{#var:domain}}
  |Is component type={{{Component Type}}}
  |Has component title={{{Component Title}}}
  |Has semantic display title={{#show:{{FULLPAGENAME}}|?Has component title prefix}} "{{{Component Title}}}"
  |Has short description={{{Component Short Description|}}}
  |Has release status={{{Component Release Status|Released}}}
}}
{{#default_form:{{{Component Type}}}}}
{{#if:{{{Component Category|}}}|[[Category:{{{Component Category}}}]]|[[Category:Component]]|}}
</includeonly>
<noinclude>[[Category:3OM-TopLevelOntology‎-Template]][[Category:ClassTemplate]]</noinclude>

References

  1. ^ Component 601318 Footnote 1