I have all editions of the KE7X manuals (K3 and KX3) since the beginning -- 
these are not hyperlinked.  No, that is not anywhere close to what I am 
suggesting.

Let me describe a few features of how such a thing is put together or at least 
this is the kind of thing I have worked with in the past.

--- The document is presented both in forward form (just like reading the paper 
document for example) and inverted form.
--- Inverted means that the document is fully 100 percent indexed.
--- Indexed entries (remember, every single token/word is indexed are given 
attributes, some are automatically created.
--- Automatic attributes include the tagging of words as being regular English 
parts of speech such as articles, verbs, etc.
--- A database is created that contains all text (note, this is done 
differently for different kinds of documents).
--- Part of this database are support of connections.  For example, connected 
topics together into a hierarchical network.
--- Connections are usually manually done so take time and a degree of subject 
knowledge and creativity.
--- There are also external connections to other information of a related type.
--- There are a variety of lookup and reading features such as keyword or topic 
and so on.  Remember, most things are
     linked.

I have used a variety of technology as the server side support for such 
hyperlinked documents.  For example, both xml based data structures and 
relational database technology is used.

The idea of this approach (from my experience) grew out of an analysis method 
called "requirements tracing".  There are some very good (and, very expensive) 
requirements tracing applications available.  It takes a document (say, a 
defense department RFP) and generates the database, indexes, keywords, and so 
on.  Some requirements are identified and tagged where as others need to be 
manually identified.  Tracing means linking requirements together in a manner 
that allows extensions and back tracing.  Back tracing is started from some 
deep and derived requirement statement to find the full ancestry of other 
requirements leading to this requirement.


73, phil


On Jan 7, 2014, at 10:56 AM, Rose <elecraftcov...@gmail.com> wrote:

> Phil,
> 
> Google "KE7X manuals" - I think you'll find just what you're looking for.
> 
> 73!
> K0PP
> 

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Reply via email to