Current Command Summary
The text box above and all like it pass Idealized English commands to the context in memory. Before you use it, please read this INTRODUCTION Commands in planning are marked red.or blue. Those available to try out are bolded. Please email me problems or suggestions. Thanks.
A. Finding a Topic - click its link in any displayed chart, or enter as a Request...
- any Term - shows its Subject(s) - each will be an Aspect, Group or Example
- Definite NP - THE Qualifiers Group - finds most recently used qualifying example
- Pronouns - (like A.2, but the form is lexicalized - held in a word's definition)
- THIS = denotes the topic whose web page chart was last displayed
- IT = denotes the topic last created or modified by the interpreter
- ?? = many more English examples will be defined as time permits
B. Finding its Aspects - look at the chart (and notice those scoped to a theme)
- SCOPE -themesList- the listed (Term) args define a name space for aspects
- Conceptually, any scoped data is deemed valid only in its name space
- the latest themes all become scopes for data added in part-D forms
- the active user (_thisUser) is included by default in every -themesList-
- queries below ignore data scoped by any topic not in latest -themesList-
- Role-Player lookup - Aspect OF Subject - returns Role Player or their Group
- Occurrence lookup - Aspect OF Subject - special form aiding B.4 and D.1-4
- Defaults - THE Aspect OF Subject - if unknown, inferred using Subject's Group
Patterns above have read-only effects. Those below may change a context, but such
effects vanish with the web session until commands in F and G get released.
C. Creating a new Topic - each gets a symbol (given Root Term or just an ID)
- Example - Determiner Qualifiers Group - much like an indefinite noun phrase
- AKO as first item creates a class - an uncountable subgroup of Group
- ASO as first item creates a subset - a countable subgroup of Group
- ISA (or A, AN) as first item creates an instance - a member of Group
- the Group indicated will get used in B.4 for Default Aspect inheritance
- Definition - Term + Example - if Term has a similar meaning, it is reused
- Add a Qualifier - Subject IS Qualifier(s) - a handy special case IS form
- Add a Name - Subject HAS NameType Value - a special case of D.1
- Grouping - Subject INGROUP Group - constrained by rules under C.1
- simple primitive form ensuring that Subject belongs to a Group
- no scoping; not tracked; helps link Subjects to our upper ontology
D. Characterizing any Subject - each Aspect added is Scoped per rules in B.1
- Add dataTypes - Subject HAS Occurrence Value - a constrained String format
- A special Occurrence like :sid or :uri has a value like a locator (e.g, URL)
- Others have string values: like an XSD data type or OWL DataProperty
- Nothing new gets stored if prior data already records it - a general rule
- Associate Topics - Subject HAS Property Value - under OWL-like constraints
- The Property type models comparative English modifiers - see E.6
- Value can be a scalar measure OR an equivalent descriptive Topic
- Specify a Part - Subject HAS Element Part - the Element constrains the Part topic
- Assigning any Part to a Subject expands its structural part-whole model
- Properly managing such collections of Parts can structure entire contexts
- Intrinsic situations - Subject HAS Role Player - a Role-constrained Player-topic
- Events, relationships, and processes decompose into standard case roles
- Declaring a Role and Player may imply the Subject is in known situation
- Implications - A new Component may cause Composite's Group to RUN a script
E. Special Primitives for Modeling Triples and Other Grammar Forms
- Simple Triple - ASSERT Subject Relation Object - unconstrained
- A scoped, binary Association is created, typed by given Relation
- Uses default role-types -:subject & object; The Subject becomes IT
- Modeled Triple - REIFY Subject Relation Object - may be constrained
- like E.1, but a 3-way Association with the same type gets built here
- A Relation instance gets used as the third (_Composite) role Player
- This reification lets D.1-4 type aspects be applied to the whole Triple
- Drop all arguments and the association last displayed gets assumed .
- Extrinsic Relations - like E-1/E-2, bur a D-3/D-4 Composite is also implied
- Here, neither Subject nor Object is a part or attribute of the other)
- The Relation-type MUST lexicalize (internally spec) its Composite
- Prep'nal Phrase - Subject IS Prep Object(s) - lexicalized abstract relations
- Clause - Subject IS Gerund Comps(s) - like E.4; but lexicalized case frames
- Adjective Phrase - Subject IS Modifier - like D.2 with implied quantification
F. Drop/Accept - requires special CMS rights outside your own scope
- Drop any Aspect - DROP Subject Aspect - restores its default, if any
- Drop Occurrence - DROP Subject Occurrence Val - like F.1 if only Val
- Drop RolePlayer - DROP Subject Role Player - like F.1 if only Player
- Drop a Subject - DROP Subject - (drops every known Aspect in turn)
- Approval - OKAY Scope - drops Pending status from scoped changes
G. Special Forms treated as new Commands - indirectly a very open set...
- Run a script - RUN filename - it must exist in a special web app folder
- Useful way to repetitively trigger any set of forms defined on this page
- Nesting of expressions, conditional forms, scripts from scripts, etc.
- Import commands enabling graceful merges of new RDF or XTM files
- Term-driven controls - Subject AKA Topic - limited equivalence;
- Explicit merge maps and controls - mostly ontology dependent-
- Export commands for partially dumping a context into RDF or XTM files,
- Scripted queries and filters can limit output to specific types of data
- With G.2, context can enable round-trip RDF <-> XTM conversions
- Macro modules - - ?pattern TDB? - support from new TM engines, interpreters
- Optional converter modules can expand Context using any file format
- Optional reporters offer special web pages, reports, data validation
- Frameworks, Prolog-like queries, and merging controls ease coding
- Modules depend on available manpower and tools for driving TMAPI
- Your own Commands - ?pattern TDB? - use RUN to test its logic; publish it
- Similar to RUN, but uses a script that you pre-define, name, install
- Installation it demands the Command be documented in a topic map
- Running it demands that such documentation be available in memory
- Some optional macros might be similarly documented and managed