TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Ability vs Capability From:"Dan Roberts" <droberts63 -at- earthlink -dot- net> To:"Nancy C Kendall" <Nancy -dot- C -dot- Kendall -at- aexp -dot- com>, "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 21 Jun 2000 18:48:21 -0400
I'm curious about why you need to make such a distinction, and what that
distinction is.
Why can't either word be used for both situations?
-----Original Message-----
>To me, the word "ability" should only be applied to a person, not to software
>or a piece of equipment. For example: With the right equipment, a skilled
>person has the ability to move mountains.
>
>OTOH, the word "capability" should be applied to software or equipment.
>For example: In the hands of a skilled operator, earth-moving equipment has
>the capability of moving mountains.
>
> I've checked Merriam-Webster's online dictionary and thesaurus and didn't see
>any reason why these words should (or should not) be used in this way.
