Phoneme Object Properties

The IMDI and SRGS attributes should for the base for Phoneme object properties.

W3C may wish to offer an RFC for phoneme properties.

hub server

one of these days set up the hub... darpa can have credit for developing mitre's galaxy into an operating system for the communicator algorithm.. but notice it isn't finished yet...

why multicast?

because there are groups of U.S. Marines as well as groups of U.S. Army soldiers for whom the Air Force needs locations. Multicast groups can be formed of groups of smaller groups. GPS data can be shared by multicast. All group members are provided data for that multicast.

Multicast groups can be formed according to need and dissolved when usefulness is finished.

If perhaps a group of teenagers wished to share their real-time GPS upon a shared map, multicast provides the solution.

open source Phoneme object

please consider posting comments regarding the properties needed for software object to represent basic linguistic audio frequency data.

you don't have to post here: Sphinx and Communicator have good opensource resources at SourceForge. These are probably the best places to send comments, until w3c drafts an RFC.

i repeat the request for a property denoting the cepstral dynamic model transition vector for an agreed upon standard transition identity matrix. the identity matrix should be evolved upon the simplest possible lines, such as perhaps representing the delta, double delta, and nth order differentials on the diagonal.

Hub script algorithm: roughest draft

AIML Charlix style context based reasoning
SRGS markup of cepstral dynamic transistion vector language model
recognizer using weighted object-relational trees upon language model
dictionary of human distress cepstra
Multicast routing of GPS data for social networks
mapping of group GPS
privacy option defaulted to private for GPS data
GPS optionally set to public
E911 mapping of distress GPS and public GPS