language en

The EKG/UX Component Ontology

Authors:
http://orcid.org/0000-0003-2309-5068
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://insertlicenseURIhere.org
Visualization:
Visualize with WebVowl
Evaluation:
Evaluate with OOPS!
Cite as:
http://orcid.org/0000-0003-2309-5068. The EKG/UX Component Ontology.
Provenance of this page
Ontology Specification Draft

Abstract

The core concept in the EKG/UX Component Ontology is the class Component which represents the information that is needed for a given user interface (or report) component. These Components form a tree-like structure where a parent Component can hold multiple child Components that are assumed to be shown by a user interface or report generator in the space -- or "screen real estate" -- occupied by the parent Component. Many of the names of the various components are inspired by Google's Material Design concepts: https://material.io/components However, although many Components as they exist in the EKG will have a one-on-one relationship with a gisible component on the screen (or on a report), this does not always have to be the case. Some Components in the user interface will have many more sub-components, there is no hard requirement that they all have to be defined in the EKG as well. This is meant to be a flexible structure. In theory, a legacy React application for instance may be represented as just one top level Component in the EKG, in that sense it woud be a "black box" from the EKG's perspective.

Introduction back to ToC

This is a place holder text for the introduction. The introduction should briefly describe the ontology, its motivation, state of the art and goals.

Namespace declarations

Table 1: Namespaces used in the document
https://ekgf.github.io/o-ux/component#<https://ekgf.github.io/o-ux/component#>
components<https://material.io/components>
owl<http://www.w3.org/2002/07/owl>
android<https://material.io/components/tabs/android>
wiki<https://en.wikipedia.org/wiki>
xsd<http://www.w3.org/2001/XMLSchema>
rdfs<http://www.w3.org/2000/01/rdf-schema>
orcid-org<http://orcid.org>
o-ux<https://ekgf.github.io/o-ux>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns>
terms<http://purl.org/dc/terms>
sheets-side<https://material.io/components/sheets-side>
vann<http://purl.org/vocab/vann>
default namespace<https://ekgf.github.io/o-ux/component>
dc<http://purl.org/dc/elements/1.1>

The EKG/UX Component Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

The EKG/UX Component Ontology: Description back to ToC

This is a placeholder text for the description of your ontology. The description should include an explanation and a diagram explaining how the classes are related, examples of usage, etc.

Cross reference for The EKG/UX Component Ontology classes, properties and dataproperties back to ToC

This section provides details for each class and property defined by The EKG/UX Component Ontology.

Classes

Anonymous Userc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#AnonymousUser

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
User c
is disjoint with
Named User c

App Barc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#AppBar

The top app bar displays information and actions relating to the current screen. A bottom app bar displays navigation and key actions at the bottom of mobile screens.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c
has sub-classes
Bottom App Bar c, Top App Bar c

App Navigatorc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#AppNavigator

A generic component that allows a user to navigator to other Apps or primary destinations in the existing App supporting: - NavigationDrawer - BottomNavigationBar (for up to 3 destinations) - NavigationRail (for up to 7 destinations)
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Navigation Component c
is disjoint with
Bottom Navigation Bar c, Navigation Drawer c, Navigation Rail c

Backdropc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Backdrop

A backdrop appears behind all other surfaces in an app, displaying contextual and actionable content.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

Bottom App Barc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#BottomAppBar

A bottom app bar displays navigation and key actions at the bottom of mobile screens. Bottom app bars provide access to a bottom navigation drawer and up to four actions, including the floating action button.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
App Bar c
is disjoint with
Top App Bar c

Bottom Navigation Barc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#BottomNavigationBar

Bottom navigation bars allow movement between primary destinations in an app. Bottom navigation bars display three to five destinations at the bottom of a screen. Each destination is represented by an icon and an optional text label. When a bottom navigation icon is tapped, the user is taken to the top-level navigation destination associated with that icon.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Navigation Component c
is disjoint with
App Navigator c, Navigation Drawer c, Navigation Rail c

Bottom Sheetc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#BottomSheet

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

Buttonc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Button

Buttons allow users to take actions, and make choices, with a single tap.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Element c

Canvasc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Canvas

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

Cardc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Card

Cards contain content and actions about a single subject. Cards are surfaces that display content and actions on a single topic. They should be easy to scan for relevant and actionable information. Elements, like text and images, should be placed on them in a way that clearly indicates hierarchy.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

Checkboxc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Checkbox

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Element c

Chipc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Chip

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Element c

Componentc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Component

Authors:
http://orcid.org/0000-0003-2309-5068
has sub-classes
Model Component c, View Component c

Data Tablec back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#DataTable

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

datapoint menuc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#DatapointMenu

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Menu c
is disjoint with
story menu c

Dialogc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Dialog

Dialogs inform users about a task and can contain critical information, require decisions, or involve multiple tasks. A dialog is a type of modal window that appears in front of app content to provide critical information or ask for a decision. Dialogs disable all app functionality when they appear, and remain on screen until confirmed, dismissed, or a required action has been taken. Dialogs are purposefully interruptive, so they should be used sparingly. Dialogs should be used for: - Errors that block an app’s normal operation - Critical information that requires a specific user task, decision, or acknowledgement
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

Elementc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Element

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
View Component c
has sub-classes
Button c, Checkbox c, Chip c, Image List c, List c, Tab c, Text Field c
is disjoint with
Surface c

Image Listc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#ImageList

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Element c

Landing Thingc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#LandingThing

The LandingThing is the object -- or Thing -- that the user landed on, its EKG/IRI is the current browser IRI. Other components may query the LandingThing-component for additional information such as its types (rdf:type). For instance, the UseCases-component may use these types to query the EKG for all use cases supported for the given user and the given LandingThing.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Model Component c

Listc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#List

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Element c

Model Componentc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#ModelComponent

A ModelComponent is an active component that manages a data structure in the browser (or a reporting engine) to be used by ViewComponents.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Component c
has sub-classes
Landing Thing c, Navigation Destinations c, Session c, Use Cases c, User c
is disjoint with
View Component c

Named Userc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#NamedUser

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
User c
is disjoint with
Anonymous User c

Progress Indicatorc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#ProgressIndicator

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Temporary Service c

Sessionc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Session

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Model Component c

Side Sheetc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#SideSheet

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

Snackbarc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#SnackBar

Snackbars provide brief messages about app processes at the bottom of the screen.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Temporary Service c

story menuc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#StoryMenu

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Menu c
is disjoint with
datapoint menu c

Surfacec back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Surface

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
View Component c
has sub-classes
App Bar c, Backdrop c, Bottom Sheet c, Canvas c, Card c, Data Table c, Dialog c, Navigation Component c, Side Sheet c, Tab Layout c, Temporary Service c
is disjoint with
Element c

Tabc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#Tab

Authors:
http://orcid.org/0000-0003-2309-5068
Is defined by
https://ekgf.github.io/o-ux/component#
has super-classes
Element c

Tab Layoutc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#TabLayout

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c

Temporary Servicec back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#TemporarySurface

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Surface c
has sub-classes
Banner c, Menu c, Progress Indicator c, Snackbar c

Text Fieldc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#TextField

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Element c

Top App Barc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#TopAppBar

The top app bar displays information and actions relating to the current screen. The top app bar provides content and actions related to the current screen. It’s used for branding, screen titles, navigation, and actions. It can transform into a contextual action bar.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
App Bar c
is disjoint with
Bottom App Bar c

Use Casesc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#UseCases

The UseCases component collects all current use cases from the EKG that the current User could have access to given the current LandingThing. For each supported Use Case it knows the EKG/IRI, its label and the Personas that the current user has. Other components can ask the UseCases-component for more details about whether a given Story in a given UseCase is supported for the given Persona. That information could then be used to show or not show certain elements in the user interface that may or may not be available to the current user.
Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Model Component c

Userc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#User

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Model Component c
has sub-classes
Anonymous User c, Named User c

View Componentc back to ToC or Class ToC

IRI: https://ekgf.github.io/o-ux/component#ViewComponent

Authors:
http://orcid.org/0000-0003-2309-5068
has super-classes
Component c
has sub-classes
Element c, Surface c
is disjoint with
Model Component c

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties
ni: Named Individuals

References back to ToC

Add your references here. It is recommended to have them as a list.

Acknowledgements back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.