Path: utzoo!attcan!utgpu!watserv1!watdragon!watdragon.waterloo.edu!tbray
From: tbray@watdragon.waterloo.edu (Tim Bray)
Newsgroups: comp.windows.x.motif
Subject: What does compliance mean?
Message-ID: <1990Dec17.135351.5769@watdragon.waterloo.edu>
Date: 17 Dec 90 13:53:51 GMT
Sender: tbray@watdragon.waterloo.edu (Tim Bray)
Organization: University of Waterloo
Lines: 16

Perusing my way bck and forth through the motif docs, I haven't run
across any discussion of what "motif-compliant" means.  Since we are
about to begin commercializing a product that was developed with motif,
and would like to leverage a bit off the "Motif" and "OSF" names, this
question is important.  We could call up OSF and ask, but I would think
the answer is of general import to readers here.

Specifically: does OSF have an application compliance validation service?  If
not, am I free to go ahead and advertise the thing as "Motif-based"?  Suppose
I do and there turn out to be some departures from "must"* clauses in the
Style Guide?  If these departures are honest oversights?  If the departures
are because I didn't even read the Style Guide?  If the departures are
well-known but deliberately left in, after serious agonizing, because the
unusual requirements of the application seem to mandate it?

Tim Bray, tbray@watsol.waterloo.edu