On Tue, 1 Apr 2008, Dana H. Myers wrote:
> Stacey Jonathan Marshall - Solaris RPE wrote:
> > The common usage below suggests that beer is a consumable and a format, as
> > such should it be beer(4)?
> > Does this make sense, beer(4) me does! How about beer(4) you?
> >
> > Randy Fishel wrote:
> > > I am sponsoring this fasttrack on behalf of myself. The timer is set
> > > to 04/01/2008.
> > >
> > >
> > > Overview
> > > ========
> > > This case describes the proper usage model for the common zymological
> > > beverage, beer(1). Though the beverage 'wine(1)' has similar processes
> > > and has similar results, the density and concentrations are different,
> > > so this case will not include 'wine(1)'. This case will also not
> > > include common compression techniques (warming and cooling), but will
> > > reference them.
> > >
> [...]
> > >
> > > Exporting Interfaces
> > > ====================
> > > Name Stability
> > > ===========================================
> > > Urethra Standard (and important after using beer(1))
> This section is missing the other, less commonly-used, exporting interface
>
> Esophagus Standard (usually associated with one of the keg
> packages)
This is only used for overflow, though. And because it isn't a
pretty sight, I choose to omit it (especially since it is often used
by users that don't have the 'public.beer.legal-age' authorization).
However, if ARC members see that this as more common, I will include
it as well (I just try not to use it).
---- Randy
>
>
> Dana
>
