Sample Uses for Charts

1. Charts that CODERS Create at Web App Build Time

Why maintain multiple APIs for data resources when one will do?  One can build Topic Maps off line by hand, or post a result set from any data base query. The resulting XTM file is an ISO-standard format, easily loaded into small open-source engines needing only RAM to store and query many useful kinds of code-support files:

• resource bundles - easily localized by scoping topics' base names
• semantic site maps - each topic can get links, subtopics, annotation
• document base indicies - scoped links to files can flag recent modifications
• on-line HELP text - each user's context stack can be saved in a session
• event modeling - charts of their types and meanings can aid all subscribers
• configuration data  - semantic models of what fields mean helps everyone
• semantic lexicons - define vocabulary for any project, product, spec

2.  Charts that USERS Modify at Web App Run Time

Admin staff or customers with web forms and permission can securely post their own identity, interests, preferences, etc, or remotely adjust any other context file by using our change management system.  Semantic constraints on topic characteristics help keep data bugs from creeping in, and will educate end-users on what is expected:

• administration files - all those in part 1, with change-tracking added
  
• a user data registry - securely modify charts that model oneself or others
• group collaboration - remote communities can modify plans, specs, etc.
• shared bookmarks - a group adds and models them in a server-side chart
• multi-user games - charts can model the players, props, current situations
• groupware sites - each group models itself, its interests in a shared chart
• periodic reports - groups update chart data; agents assemble the reports
• a base of facts - semantic models are the key to all knowledge engineering
• business rules - a chart of scripts run on event types can semi-automate IT

3. Charts that AGENTS Modify at Web App Run Time

External programs of many types can also use a charting web app to store on-line data in a disciplined, easily searched  way, or to read it, both via HTTP requests.  They can post data with simple web requests, and the semantic net can absorb it.  If internal constraints and inferencing rules are added, the Topic Map being used becomes a complex predicate that handles or rejects changes or additions per high level tests, or inherits data along aspect-specific paths like a frame system.  This is model-driven decision making, a core foundation for human and artificial intelligence, remarkably easy to implement with topics scripted in the WORDS language.  Use it to enable:

• smart data feeds - they can report all data changes since you last asked
  
• situational awareness - tracking events & status in a group or enterprise
• processing reports - charts used like log files give agents semantic output
• blackboard models - the same charts can give other agents semantic input
• English phrase I/O - situational charts lets most-likely meanings be tested
• customer support - email or phone inputs can be classified automatically
• discourse models - a chart can record the topics discussed by all speakers
• message exchange - agents can use charts to communicate with each other
• merging data exports - ontology-aware agents can convert them as needed