W3C home > Mailing lists > Public > xproc-dev@w3.org > April 2011

Meanings of “Framework”, “Library”, “Toolkit”

From: Tony R. <tgoodchild@gmail.com>
Date: Fri, 25 Mar 2011 12:14:22 -0400
Message-Id: <8CB2B1F2-DFA9-4D1B-AAE3-1A1D9D7714DB@gonk.net>
To: XProc Dev <xproc-dev@w3.org>
Greetings!


XProc is for [insert term(s) here]…
	I was just thinking about the difference between the words “framework”, “library”, and “toolkit”.  (Other relevant terms, such as “module” or “component” might be included here too, if you like.)

Perhaps reiterating the differences between these terms might be useful.  For example: there’s obviously a difference between a “framework” and a “toolkit”.  They have different roles.  They fulfill different types of needs.  

Recent debates over the use or ab-use of XProc might benefit from revisiting these terms.  In other words, it might be useful to take a look at all the different kinds of software projects that exist—whether they are frameworks, libraries, or whatever else—and consider whether XProc is a capable tool for each of them.


Bonus points:
	In cases where XProc is unsuited for a particular task, propose another tool that fulfills the task well.  More concrete examples help contrast the differences between XProc and other tools, thereby helping clarify XProc’s role in the greater software ecosystem.  
	

More bonus points:
	In cases where XProc is unsuited for a particular task, AND other tools are also unsuited (or make an attempt but fail to pull it off), start a conversation / thread / wiki page.  Link us to it.  Let's start by identifying why the particular task is difficult to address.  Let's explore what to do about it! :) 


—Tony
Received on Monday, 4 April 2011 17:02:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 April 2011 17:02:34 GMT