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.
I've worked in a lot of companies that sold code.
To some, an API was developed "ready to use" and an SDK had
to be compiled on the user-dev's machine. To some, an SDK
was specifically meant to extend another commercial application
(like an SDK for Word so you could develop RoboHelp) and
everything else was an API. To some, each individual method
is an API (eww, I hate this one) and SDK never even enters
the vocabulary. This "documentation magically turns an API
into an SDK" definition is a new one on me, but that doesn't
mean it isn't valid *somewhere*. <g>
Whether it's called an API or an SDK, the task is essentially
the same -- helping the user-dev integrate the supplied
code into an application.
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.