In this case, I am using the word association to mean a conceptual link.
I am following the HRL reference model terminology.
More explicitly (and still within this terminological framework), I mean to imply an association with an implicit behavior of replace.
Must be able to store persistently ASCII text files
That is, the application must be able to assign an identifier to a file (or determine the identifier so assigned by another entity), request that it be stored persistently in a store, and be able to retrieve at some later time the file using the previously assigned identifier.
Must persistently address associated words
That is, the application must be able to assign identifiers to the "endpoints" of the association (or determine the identifiers so assigned by another entity), request that they be stored persistently in a store, and be able to determine at some later time the endpoints using the previously assigned identifiers.
Must send "Build association between these persistent addresses" message to server
That is, the application (or a proxy) must indicate to the link server the endpoints selected by the author for the association in question.
Must send "Follow from given source" message to server
That is, the application (or a proxy) must be able to indicate that the author wishes to follow the association, and that furthermore, an endpoint has been specified as the source for this traversal.
Must process "Display given persistent address" message from server
That is, the application (or a proxy) must be able to display what semantically amounts to the destination of an association traversal.
Must process "Build association between these persistent addresses" message from client
That is, the link server must be able to receive two association endpoint identifiers from the application, and build an association between them.
Must process "Follow from given source" message from client
That is, the link server must be able to receive an association endpoint identifier from the application and determine the identifier of the "other side" of the association. It is assumed here that for any given endpoint identifier, there is exactly one associated endpoint.
Must send "Display given persistent address" message to client
That is, the link server, once determining the identifier of the "other side" of an association given one identifier (see above), must be able to send a message to the application indicating that this destination endpoint should be displayed.
Must persistently store ASCII text files for client
That is, an application must be able to request that a file be stored persistently with an associated identifier, and be able to retrieve at some later time the file using this identifier.
