O

``It's a fragrance system named O, not a system named O Fragrances'' - Jim Futon

The O Consortium, headed by Bob Scheffelera, was formed to control the definition and development of the O Fragrancing System. The O protocol defines a cross-platform, vendor neutral, client-server, buzzword-compliant transport mechanism for the description of fragrances. The first full public release, O Version 11, Release 7 (O11R7) will be available the 1st of April, 1997.

The O Consortium has several current products:

the O Protocol Specification

a sample O11 server

sample libraries, including

Olib - the O protocol library
Ot - the O Toolkit library
Ow - the O widgets
Omy - stuff that doesn't really fit anywhere else

Oroadmap, a simple, ASCII-based odor definition description

support for most vendor's emanators

various sample clients, including

oclock - an odor-based clock
ocalc - for calculating the attraction or repulsion of various odor combinations
oroadmap - a simple odor manipulation program for odors implemented with the Oroadmap specification
oterm - an odor interaction program
osmellsel - an interactive odor picker
oemainfo - gives information on available emanators
onostrils - a pair of nostrils that follow the odor cursor [by default, a skunks tail] around the emanator
oman - whine about an odor
omessage - send an odor to send a message
ofm - O fragrance manager
tfm - Tom's fragrance manager

This release will include both server-side and client-side odormaps, the Fetid security system, OEM (the Odor Emanation Manager), and a host of general protocol and security enhancements to replace the last set of general protocol and security enhancements, mostly compatible with the last release.

FTP sites include:

Further information is available at http://www.o.org/ .