This part of the User Experience Design Ontology defines environmental characteristics that can influence the quality of man-machine interaction.
Author(s): Coomans, Marc
Publisher: Agfa Healthcare
The URI of this ontology is: http://www.agfa.com/w3c/2009/uxd-1-0-environment/. In the remainder of this document, we will assume that you import this vocabulary in your own document by associating the prefex "ux-a" as follows: xmlns:ux-a="http://www.agfa.com/w3c/2009/uxd-1-0-environment#". The concepts of this vocabulary can then be referenced with CURIEs (compact URIs) of the form ux-a:{resource name}.
Base classes:
ux-a:ApplicationCharacteristic):
Window type
(ux-a:WindowType)
Note: Windows typically have a border that support window management tasks (moving, resizing, closing), and have on information content that support domain tasks. The information content of an application is typically organised in pages between which the user can navigate. Page characteristics are defined later in this document.
Window type values:
ux-a:Window)
ux-a:ApplicationWindow): A regular window that hosts the central GUI of the application.
ux-a:Dialog): A window launched from a parent window, typically smaller than that parent window, that enables reciprocal communication between the computer and its user about a specific event, command, or toolset.
ux-a:ModalDialog): A dialog that temporarily blocks interaction with other application parts until the dialog has been closed. (Note: One may further differentiate between application-modal dialogs, and document-modal dialogs.)
ux-a:ModelessDialog): A dialog that can remain open while working with other parts of the application.
In most productivity applications, the information content is organised in pages. The user can navigate from one page to another within the same or in different windows. Each page typically focuses on one specific user task, which represents the purpose of that page. The primary user task typically drives the choices for overall page organisation, layout and interaction. A page can additionally support multiple secondary tasks. Secondary tasks are typically given less visual attention.
ux-a:PagePrimaryPurpose): the primary user task that the page supports.
ux-a:PageSecondaryPurpose): secondary user task that the page supports.
Page purpose types:
ux-a:HubPage):
ux-a:CentralApplicationHub): The one central hub page from which all other application pages can be reached. The Central Application Hub is typically also the starting page of the application.
ux-a:HomePage): Synonym of ux-a:CentralApplicationHub.
ux-a:ListPage): A page that shows a list of things (i.e. domain objects, tasks) from which a selection can be made for detailed review, editing, or other kind of manipulation.
ux-a:ObjectDetailPage): A page that shows details of an object, and that may allow editing or other manipulations of that object.
ux-a:PropertyDialog)
ux-a:TaskPage): A page that supports the user performing a specific (domain) task.
ux-a:Wizard): A page that supports a specific (domain) task by guiding the user through a series of steps, displaying information for each step one by one.
Application Display Type
(ux-a:ApplicationDisplayType)
Application display type values:
ux-a:RegularWindowApplication): application that may be used in conjunction with other programs, and therfore runs inside window with visible borders.
ux-a:ImmersiveApplication): full screen application that isn't used in conjunction with other programs, such as media players, games, and kiosk applications