From the original case for the fault manager, the command line options for fmdadm(1M) were classified as evolving and the output, unstable. It seems straightforward to map evolving to committed for the command line options. What is not so clear is the commitment level of the output. The new interface taxonomy suggests that such output is not an interface at all and should be classified as 'Not-an-interface':
"In the course of reviewing or documenting interfaces, the situation often occurs that an attribute will be present which may be inferred to be an interface, but actually is not. A couple of common examples of this are output from CLIs intended only for human consumption and the exact layout of a GUI." The project team is happy to adjust the classification level to what is appropriate and customary. Please advise. Cindi Joseph Kowalski wrote: > Gary Winiger wrote: >>> 4.4. Interfaces: >>> fmadm command-line options are Evolving, human-readable output is >>> Unstable. >>> >> >> Hummm, how about Committed and Not-an-Interface respectively? >> > Not clear... Maybe they intended this to be Unstable/Uncommitted. Guys? > > - jek3 >
