Component 110431

SMW CindyKate Main

Facet

Facet Constituents

Items

[edit]

Facet type	Showcase
Domain	Component 607119

→ Show facet/graph

[edit]

is constituted by properties...	...having values

[edit]

The Showcase

Notice:

For the time being, it seems that Firefox is rendering mermaid graphs/charts reliably.

NASA's ISS FPIP

One of NASA's management artefacts is its ISS FPIP. Let's see how we can

1. manage the underlying data on a SMW and
2. visualize facets of that data in accordance to the existing ISS FPIP chart.

Draw ISS FPIP's ontology by hand

During a workshop with NASA representatives we came up with the following preliminary ontology covering some aspects of ISS FPIP.

Notice:

The tool used is mermaid's online graph editor.

<mermaid2> graph LR

CrewVehicleFlight -->|Has launch date|CrewVehicleFlightLaunchDate CrewVehicleFlight -->|Has return date|CrewVehicleFlightReturnDate CrewVehicleFlight -->|Has dock date|CrewVehicleFlightDockDate CrewVehicleFlight -->|Has undock date|CrewVehicleFlightUndockDate CrewVehicleFlight -->|Has vehicle type|VehicleType CrewVehicleFlight -->|Has docking location|DockingLocation

CrewVehicleFlightDockDate -->|Defines previous|ExpEndDate CrewVehicleFlightUndockDate -->|Defines next|ExpStartDate Expedition -->|Has end date|ExpEndDate Expedition -->|Has start date|ExpStartDate Expedition -->|Has commander|Astronaut Expedition -->|Has FE 1-6|Astronaut

CargoVehicleFlight -->|Has launch date|CargoVehicleFlightLaunchDate CargoVehicleFlight -->|Has return date|CargoVehicleFlightReturnDate CargoVehicleFlight -->|Has dock date|CargoVehicleFlightDockDate CargoVehicleFlight -->|Has undock date|CargoVehicleFlightUndockDate CargoVehicleFlight -->|Has vehicle type|VehicleType CargoVehicleFlight -->|Has docking location|DockingLocation

CrewVehicleFlight -->|Has commander|Astronaut CrewVehicleFlight -->|Has FE 1-2|Astronaut </mermaid2>

Based on these findings we trigger a bottom-up design process.

Assert some preliminary exemplary instances for each component type identified and implement the component types' metadata and instance templates

In this first column we factorize data about exemplary instances and group them in templates representing different abstraction levels.	In this second column we implement the templates on the abstraction level "component type" (domain ontology) using both SMW and Cargo for semantization and design the instances' data presentation as a page. Notice: You see that we semanticize data using both SMW and Cargo. The reason for this is explained further down. Also, the abstraction structure is not optimal yet, but remember Donald Knuth's Principle "Premature optimization is the root of all evil". :)	In this third column we implement the component types' metadata (top-level ontology).
↓	↓	↓

Type "Astronaut"

<wikitext2 page="Component 723086"/> → See all

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

<wikitext2 page="Component Type 431041"/>

Type "Expedition"

<wikitext2 page="Component 723080"/>→ See all

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

<wikitext2 page="Component Type 431047"/>

Type "Crew Vehicle Flight"

<wikitext2 page="Component 723082"/>→ See all

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

<wikitext2 page="Component Type 431042"/>

Type "Cargo Vehicle Flight"

<wikitext2 page="Component 723083"/>→ See all

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

<wikitext2 page="Component Type 431043"/>

Now that we have

1. asserted some preliminary exemplary instances for each component type identified,
2. implemented the component types' metadata and
3. implemented instance templates,

let's ask the SMW to give us an overview of what we've got.

View the instances asserted

Asserted astronauts

No results

Asserted expeditions

No results

Asserted crew vehicle flights

No results

Asserted cargo vehicle flights

No results

So far so good. More importantly and based on the declarations and assertions made hitherto, we can ask the SMW to "explain to us" NASA's ISS FPIP.

View ISS FPIP's ontology as it is derived from assertions

Define the ISS FPIP's ontology as a facet of type "Ontology"

How do we tell SMW what to explain to us? Well, by letting it know which triple patterns determine NASA's ISS FPIP.

Property...	...having values...	...constitutes facet
Has commander	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has FE 1	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has FE 2	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has FE 3	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has FE 4	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has FE 5	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has FE 6	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has end date	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has launch date	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has return date	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"
Has start date	Any value(s)	Ontology "NASA ISS FPIP (Flight Planning Integration Panel)"

This is why, in spite of using Cargo for semantization, we still need in order to reify the property and make assertions about it. For example:

<wikitext2 page="Property:Has FE 3"/>
This allows us to specify any facet and its visualization(s) in a YAML profile. In this example it's Ontology "NASA ISS FPIP (Flight Planning Integration Panel)".

Let SMW pan out the ISS FPIP ontology

Notice:

I am aware of the fact that the usefulnes of this kind of graph is debated, since it can get cluttered up quickly if many assertional, and even terminological triples, are involved. However, making sure that the facets visualized remain small and to the point, their visualization is priceless as a picture is worth a thousand words, as long as some knowledge and information management principles are heeded:

• Principle "Mutually Exclusive, Collectively Exhaustive (MECE)"
• Principle "A place for everything and everything in its place."
• Separation of concerns
• …

From an abstract/terminological point of view This is a tag extension call <mermaid2 profile="Component 160430" abstraction="typetype"/>. <mermaid2 profile="Component 160430" abstraction="typetype"/>

From a concrete/assertional point of view This is a tag extension call <mermaid2 profile="Component 160430" abstraction="instinst"/> <mermaid2 profile="Component 160430" abstraction="instinst"/>

Now, in the same way, we can finally let SMW create the Gantt charts, which represent the pursued goal of the entire effort in the first place. Note that the Gantt charts' underlying data and its visualization are again specified as YAML profiles, see Component 607119.

Constitute useful facets, i.e. charts and/or graphs, and run them against the asserted instances

Gantt Chart "ISS Flights and Expeditions by Astronaut"

This is a tag extension call <mermaid2 profile="Component 160437"/>.

<mermaid2 profile="Component 160437"/>

Gantt Chart "ISS Flights by Astronaut"

This is a tag extension call <mermaid2 profile="Component 160438"/>.

<mermaid2 profile="Component 160438"/>

Gantt Chart "ISS Expeditions by Astronaut"

This is a tag extension call <mermaid2 profile="Component 160439"/>.

<mermaid2 profile="Component 160439"/>