Suggested processes

From wiki.gpii
Jump to: navigation, search

Suggested processes for accepting new terms in the Preference Terms Dictionary (formerly known as "Common Terms Registry") — based on discussions in 24751 so far.

Terms that go into the registry

  • Registry contains any terms (words) that can be used in a statement of preference
    • Accessibility/Usability settings
    • Accessibility/Usability features
    • Context terms 
    • Operators  (AND, OR,  NOT,  IF,  WHEN  etc)
  • Each term has certain fields defined and required by the 24751
    • Unique ID  (in a lowerCaseCamelCase)
    • Value Space
    • Definition
    • Entry Date
    • Type (Standard, Alias etc see below)
    • Source(s)  ?????  (here or in next list?) 
  • Each term has other fields as determined by they editors and the host
    • Several Dates regarding processing
    • Processing Status
    • Used By  (who
    • Source(s)   (places where the term came from if other standards)
    • etc.
  • Terms can be of different TYPES   (defined by Editors and Host? — or maybe *’d ones would be defined by ISO 24751?)
      • Standard Terms 
      • Aliases  (same meaning and value space as Standard Term but different UniqueId (word or words))
      • Translations (same meaning and value space but in a different language )
    • *Transform Aliases (same meaning but different value space where the value space has transform(s) to and from a Standard Term
    • Application Unique Terms (Terms registered but which would only EVER having meaning in one application 
    • Other Terms (Terms used in the field by one or more entities that are not in any of the other categories above  (though they may or may not in the future)
    • [Enumerated value terms?]

How a term gets into the Registry

  1. Anyone can suggest words to go into the Registry.  
  2. Once submitted they are reviewed by an editor and cleaned up
    1. during this process only the submitter and other editors can see the entry
    2. only editors can see the editors comment fields
    3. however the submitter can make moderated changes to the entry
    4. during this process new terms as well as aliases, transform aliases etc are identified 
  3. Once an editor is satisfied that the entry is cleaned up, not spam, and not a duplicate it is classified as a CANDIDATE
    1. Candidates are viewable by editors and submitter - however submitter can no longer edit 
    2. Senior Editors review the Candidate entries - process them - and either send them back down or pass them into regular entries
  4. Once the entry is a regular entry
    1. it is viewable by all
    2. anyone can suggest an edit
      1. The edit goes back to stage 2 above - but the word stays in registry unless there is some serious problem
    3. Regular entries (any public entry) can be nominated to be a STANDARD TERM
  5. Standard Term Nominees are reviewed by a committee of senior editors chosen by the senior editors
    1. the committee is the only group empowered to make a new STANDARD TERM.   
    2. All other regular terms live in the Common Terms Registry.  But Standard Terms are the terms that people are encouraged (but not required) to use

How to handle New Term Conflicts

  • 1) New term that is = to a Certified Term Definition and Dimensions
    • handle with Alias
  • 2) New term that is = to a  Certified Term Definition but different Dimensions/Values
    • handle with Alias with transform
      • transform stored Solutions Registry (tentative solutions)
  • 3) OLD term -- but just new Enumerations
    • add them as new enumeration terms for that OLD TERM
      • start as new entries and be certified as enumerations for that term over time
  • 4) same as ii but there are new enumerations --  extension
    • handle with Alias and enumerations handled per (3)
  • 5) New term = Certified Term but  DIFFERENT DEFINITION (and maybe Dimensions)
    • HAVE to have a new UniqueID in the CT Registry - done by adding mfgr or product to the UNIQUEID (mfg chooses?)
    • IF THEY WANT to work with GPII beyond just saving the specific settings then they need to provide a MAP to the UNIQUE ID
      • MAP between product settings and the  CT Registry UNIQUEIDS
        • also the place where you identify Product Unique Terms
      • MAP (or rather UNIQUE IDs) are needed for
        • Matchmaker
        • Transformers
        • Preference Editors  (to show choices and results)
    • MAP stored in Solutions Registry

How does one get to be an editor or Senior Editor

  • New Editors are chosen by existing Editor pool  (meritocracy)
    • often it will be from among new term submitters that have proven themselves
    • but the the new editors could come from anywhere
  • New Senior Editors are chosen by existing Senior Editor pool
    • Usually it will be from among existing editors that have proven themselves