Emacs, Etude (MIT LCS), and perhaps
Interleaf all suggest an n-tuple model
for function, invocation and help.
Specifically, each function (methos or
object/style implementation should
support the n-tuple:

 - object/style/function/method (one
   thing, each) *name* & API (Some
   things such as sorting and
   alphabetization and capitalization
   should be methods (operations) and
   not [or, as well as] objects or
   object properties.)
 - help blurb and corresponding point in
   multi-dimensional help space
 - associated effect, on invocation, in
   the document file representation
 - associated effect, on invocation, in
   the on-screen WYSIWYG representation
 - keyboard invocation sequence
 - ability to remap the keyboard
   invocation sequence

Implementing the above should not
interfere with an object oriented (oo)
implementation of styles. The oo
properties should be part of the user
model and should allow users to define
objects (styles) as aggregation of sub-
objects (e.g., Section is composed of
chapters; chapter is composed of title,
number and body, ...) which, in whole or
in part, can be defined by the user with
features such as inheritance.