Task Ontology
The task ontology covers the problem domain at hand, i.e. the problems that SMW CindyKate is supposed to solve. It consists of the following task ontology component types.
Category:SMWCKMain Task Ontology Category
Task ontology auxiliary categories facilitate SMW interaction design, e.g. populating dropdown, token, combobox and list form inputs, as well as shortcut-like, explicit/direct "deep-links" to facets.
Category:SMWCKMain Task Ontology Auxiliary Category
Forms facilitate information input. Here you see task ontology forms. For domain ontology component type forms, see on the right.
Category:SMWCKMain Task Ontology Form
Partial Form Templates provide reusable form parts heeding "Don't repeat yourself, data, design or functionality (DRY)".
Category:SMWCKMain Task Ontology Partial Form Template
Data Mapping Templates separate what is presented to the user from what is stored by the system and therefore heed Principle "Separation of Data - Semantization - Design - Display - Interaction".
Category:SMWCKMain Task Ontology Data Mapping Template
Queries/Result Formats provide queries aggregating information as well as formatting the resulting aggregation.
Category:SMWCKMain Task Ontology Query
Query Result Templates format raw query results into purpose-optimized data visualizations and therefore heed Principle "Separation of Data - Semantization - Design - Display - Interaction".
Category:SMWCKMain Task Ontology Query Result Template
Display Designs Templates provide data designs heeding Principle "Separation of Data - Semantization - Design - Display - Interaction".
Category:SMWCKMain Task Ontology Display Design Template
Concepts reify facets for reuse in queries.
Category:SMWCKMain Task Ontology Concept
Properties
Category:SMWCKMain Task Ontology Property
|