Approach

This page discusses assorted aspects of our development approach.

Integration

AxAp is able to import and integrate content from a wealth of local and remote sources. After performing any needed transformations (e.g., format conversion, indexing), it can make the content available to the user. Typically, the user interaction will involve a web browser and screen reader. However, AxAp can also route content to local output devices, including an audio channel, Braille display or embosser, etc.

There are many possible transformations; here are a few:

  • adding markup for structure and style
  • conversion of formats (e.g., LaTeX, PDF)
  • recognition of characters and images
  • generation of textual descriptions
  • ...

Portability

Because we want AxAp to be portable and free, we try to follow best practices in making our selections:

We are not opposed to making AxAp work with proprietary standards and/or software. However, the basic system will not have any proprietary requirements.

Standards

As xkcd 927: Standards points out, attempting to develop "one universal standard that covers everyone's use cases" may only add another competing standard to the mix. So, in general, AxAp doesn't compete with current standards and technologies; it merely integrates and augments them. For example, we expect to exploit:


This wiki page is maintained by Rich Morin, an independent consultant specializing in software design, development, and documentation. Please feel free to email comments, inquiries, suggestions, etc!

Topic revision: r8 - 02 Feb 2017, RichMorin
This site is powered by Foswiki Copyright © by the contributing authors. All material on this wiki is the property of the contributing authors.
Foswiki version v2.1.6, Release Foswiki-2.1.6, Plugin API version 2.4
Ideas, requests, problems regarding CFCL Wiki? Send us email