Recordings from Authority version 5.

The following show Authority being used

Unfortunately, the videos were slowed where they suffered from the introduction of some flicker as a result of conversion to MP4 format.

• The definition of an 'entity' as a kind of an event
  including the noun 'event' and a relation between an event and a point in time and how to reference each of these in English.
• The drafting of "if an event begins at a time then scream"
  including the definition of "a time" as a synonym for "an instant" and the definition of the action to "scream" and the resulting understanding of the sentence.
• The drafting of "if an event begins at a specific point in time that occurs on a date then print the date"
  including the definition of the action to "print a date" and the resulting understanding of the sentence.
• The drafting of "print the date on which an event begins"
  including the definition of the predicate whether "an event begins on a date" and the resulting understanding of the sentence.
• Statements understood and not
  including that Authority supports their capture and administration and how Authority identifies what is not understood and what can be understood at any point
• The definition of "a unit of speed"
  including Authority's support for mass nouns and composition of units

The following review the top-down functionality of Authority

• The Authority menu bar and its drop-down menus
  1. File menu
     1. new/open/close knowledge base
     2. print (reports)
     3. export (e.g., examples and test cases, conceptual role model (CRM), dictionary, modules & statements
     4. import (e.g., .NET or Java object models, XSD, modules & statements
  2. Edit menu (cut/copy/past, find/replace)
  3. View menu (toolbar, status bar, expand/collapse, etc.), especially:
     1. module explorer tab
     2. modules & statements tab
     3. concepts (ontology) tab
     4. relations & procedures tab
     5. dictionary tab (i.e., vocabulary management & CRM mappings)
     6. examples, test cases, & regression testing tab
     7. implementation details tab (e.g., mappings from CRM to Java/.NET/XSD)
     and XML reports with various XSLT stylesheets for reporting on the conceptual role model (CRM), dictionary, and modules & statements
  4. Object menu (e.g., add relative(s), properties, etc.)
  5. Tools menu (plug-ins, custom fields (i.e., metadata), etc.), especially:
     1. backup of knowledge base
     2. security (i.e., object/user/group management, permissions & privileges)
     3. session administration (i.e., provenance management, work unit definition & documentation)
     4. change management [under session history] (e.g., version control, including rollback & commitment)
     5. deployment (i.e., of rules in the ART/CLIPS/Eclipse syntax) for [dynamic] (re)loading
  6. Window management (e.g. tile/cascade, arrange, find/select, etc.)
  7. Help (e.g. help/contents, documents, examples, license, web site, etc.)
• The Options Dialog & its tabs available from Tools menu of The Authority menu bar
  1. Open/Close tab (i.e., how to authenticate and what to open and how when starting)
  2. What information to show in the knowledge-base explorer
     1. modules & statements
     2. concepts (i.e., a taxonomic organization of the ontology/CRM)
     3. relations & procedures (i.e., logical predicates, functions & actions and the concepts that play roles in them)
     4. the dictionary (i.e., nouns, verbs, adjectives, etc. and their mappings to concepts & relations in the ontology/CRM)
     5. tests & cases (i.e., examples composed into test cases and regression tests with results & comparisons over time)
     6. implementation details (i.e., mappings between the ontology/CRM and Java or .NET data types or classes and method signatures or XSD elements)
  3. Concepts (i.e., whether to present instances, phrases, and sentences using concepts as descendants under concepts)
  4. Dictionary (i.e., whether to present concepts, instances, or phrasings referenced by or using words in the dictionary)
  5. Modules & statements (i.e., whether and in what order to present their text, id, and labels)
  6. Implementation details (i.e., whether to show the concepts & relations referenced by classes, methods, and XML)
  7. Testing (how to test and what to track and how to present the results of testing)
  8. Deployment (how and where to generate code, predominantly Eclipse/ART/CLIPS/JESS syntax rules)
  9. Default permissions (by group per type of object)
  10. Default behavior (e.g., answers to questions and whether to ask them again)
  11. Grammar (how much expressivity to allow in understanding English)
• Authority's initial dictionary
  1. adjectives, adverbs, nouns, prepositions, and verbs
  2. shown with phrasings that use the vocabulary (phrasings shown under concepts)
• Authority's initial vocabulary another simpler view of Authority's initial dictionary
• Authority's initial concepts
  1. entities, quantities, time (in general), units, data types & values
  2. shown with phrasings in which the concepts play roles
• Authority's built-in facts in the context of Authority's initial concept taxonomy
• Authority's initial relations and functions
  1. quantitative, lexical, and temporal comparisons & mathematics
  2. predicates and functions and roles of their arguments (parameters or results)