Re: [SpecGL] Formal vs Prose Good practice wording

I think that it may not be appropriate for every technology or 
specification to express requirements using a formal
language.  For example, requirements for authoring tools are currently 
expressed in terms of necessary behaviors/actions
  and capabilities of said tools, which may not lend themselves to 
description using a formal language.
Furthermore, there is a large variety of authoring tools, and assessment of 
some requirements may involve
humans (which may preclude use of a formal language?).

Thus, are any techniques needed under "5. Good Practice E:" to cover 
situations such as previously mentioned,
for which there is no appropriate formal language that can be used for 
specification requirements?

Just a thought..

Thanks and best wishes..

Tim Boland NIST