GLOSSARY WORKSPACE

From wiki.gpii
Revision as of 14:21, 30 October 2015 by CStrobbe (talk | contribs) (Types of Registry Terms: gpii.org -> gpii.net)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introdcution

This is a workspace where we are working on a revamp of our terminology.

Parts of the PREFERENCES AND SETTINGS ECOSYSTEM

Preferences vs Settings and Commands

There is some confusion about when something is a setting and when it is a preference. The following is offered as a consistent way for us to think about these things.

  • Preferences - are settings or commands that are stored (or on their way to storage).
    • They have conditions under which they are to be applied
    • no conditions case means that they should be applied by default unless overridden by some other conditional preference
    • Preferences can take different forms
      • they can be settings that should be applied (for those conditions)
        • (e.g. speech rate should be 250, or voicepitch for words in all capital letters should be medium high )
      • they can be a command that should be given (under certain conditions)
        • (e.g. launch or kill or send or ....)
      • they can be configuration commands or settings to part of the GPII itself
        • (e.g. Matchmaker should not send me messages suggesting changes in my settings)
  • Settings - are parameters for programs, features, etc.
    • They include turning a feature on or off
  • Commands - can be any type of command.
    • It differs from a setting in that you do not set this - but you do it. [the distinction between Settings and Commands may not need to be displayed to the user]
  • Preference Sets - Sets of preference statements
    • User may have many different preference sets
    • Sometimes they will just manually choose the one they want to apply at any given point
    • Sometimes the set will be attached to a condition that would trigger its use
    • Sets can overlap and are applied in a cascading fashion
      • by order of invocation
      • by rules in the preference sets
      • by other factors (fill in your ideas)
  • Preset:


In general

  • preferences flow
    • up toward the Prefence Server
    • or down to the matchmaker
  • settings flow
    • down to the settings handlers
    • or up from below to the matchmaker (or whatever) when the settings will be used to build some preference(s).

Preferences and Settings User Activity Spaces

  1. First discovery
    • discovering what a person who has never had access - needs in order to get access to ICT (Web and other)
  2. Explore (hopefully in a playful manner) with option to store
    • someone who has access trying out different things to see what exists and what they might like or need for different situations
  3. Choose for the moment (and not store)
    • someone who is using access features (AT or built-in) and wants to change a setting for the present situation
    • Examples: turn off the captions or move them so theyI can see underneath, slow down reading for a difficult passage, raise the speech synth volume (but not the computer volume) so they can hear it over the computer audio, zoom larger for a bit so they can read some fine print, etc)
  4. Adjust Preferences and Save
    • someone who wants to quickly change a particular setting and then store it for use later (new default setting, or just when in this place, or just with the program etc.)
    • Examples:
      • User chooses a different scan speed scanning keyboard and saves it for use when they are out of their wheelchair, or later in the day, and slower with their switch.
      • User feels the font size is always too small and makes it larger and wants this to be the new starting size
  5. Manage your stored preferences (PMT)
    • User opens a tool that gives them access to their settings and allows them to change them
    • Often will include an explore function so they can see what they are doing as they do it
    • Many different tools for this will exist from very simple to very complex depending on what the user can handle and what they user feels the need for the moment or task at hand.
    • User can 'lend' his/her set to another user who is just getting started
    • User is on a library catalogue or a university college registration kiosk and wants to see what materials match his/her preferences, in order to make a decision. 'Their' tool allows the user to compare 'our' stored preferences with available materials, or even request an alternate version with the preferred features.
    • User can have a dialogue with other users whose sets are similar in some way; share recommendations.
    • This acivity can be done with simple/limited tool (Mini-PMT) or comprehensive toos (PMT) or anything in between.

Parts of the AUTHORING ECOSYSTEM

This is a separate activity from Cloud4all -- but relates to both Preferences for Global Access work and the new Prosperity4All project.

So here are some initial notes.

Authoring CHAIN

Authoring has many different levels and players. Some or all of them may be involved with a material or product or service before a user experiences it.

  • Some Parts of an Author Chain
    1. Basic content creation(s)
      • create the basic content
      • EXAMPLES: writers, editors
    2. Original Document/Material/Service compilation/creation
      • Creation of the actual item to be disseminated
      • EXAMPLES: Creation of a PDF from all of the source materials, creation of an online web page, implementation of a service from a wireframe, creating a movie from source materials and timings
    3. Formatting and Presentation feature adds, including accessibility additions
      • EXAMPLES: adding accessibility tags to a PDF document, adding captions to the final movie
    4. Disseminators/ Posters
      • Releasing the information to the audience
      • EXAMPLES: Publishing the web page, releasing the video, posting materials to a distribution point
    5. 3rd Party Modification
      • After-the-fact changes are made to a material by someone or something other than the author or publisher
      • (this has copyright implications)
      • EXAMPLES:
        • Adding captions to a movie for someone -- or reposting it with captions (Ditto for audio descriptions)
        • Taking a print document, creating an audio reading of it, and packaging the two of them together for redistribution
        • An automatic service intercepting a document on the way to a person and automatically changing it to be more accessible (adding audio, changing it to braille, etc)
    6. 3rd Party Supplementation
      • After-the-fact supplements are made (by someone or something other than the author or publisher) that are to be used along with the product/service to make them more accessible
      • EXAMPLES:
        • Posting caption file to a site that can then be played in parallel with a movie.
        • Creating an audio description for something to be played before or during presentation
    7. User Participation
      • Users can recommend or comment on content or supplements to other users or to others in the authoring chain
      • EXAMPLES:
        • A user complains about an error in a caption, asking the captioner to correct it
        • A user rates some accessible content highly, recommending it to other users
        • A user contacts a content author and requests an alternative version

Cloud4all Semantic Infrastructure

  • Cloud4all Semantic Infrastructure
    • Semantic Ontological Framework
      • 201.2 Ontological Framework
      • 201.3 Metadata for Business Rules and IPR
    • Metadata Tools in 202
      • Automated Metadata
      • Semantic Alignment tool
      • Manual Metadata Tool

Unified Listing Semantics

Types of Registry Terms

Adapted from an e-mail to the GPII Architecture list on 3 December 2013:

common term
name for a setting or preference that would apply across many applications or devices and for which the name (unique ID), data type, value space and definition are defined in the Registry. This type of term should be stable and not change much (if at all). In the current Cloud4all implementation, these terms belong in the namespace http://registry.gpii.net/common/.
application-specific term
name for a setting or preference that applies to a specific device or application, that has a name, data type and value space that are determined by the device or application for which the term was defined. This type of term represents settings that can only be applied to other devices or applications after translation or transformation because those other devices or applications use a different name, a different data type, a different value space (or even a combination of multiple settings) to represent the same thing. In the current Cloud4all implementation, these terms belong in the namespace http://registry.gpii.net/applications/.
application-unique term
name for a setting or preference that applies to a specific device or application, that has a name, data type and value space that are determined by the device or application for which the term was defined. This type of term only makes sense in the context of the device or application for which it was defined; it cannot be translated to anything else.

See Also