PEAR = PHP Extension and ARCHITECTURE Repository?

Because it's Friday... trolling for (fairly pointless) debate. PEAR currently stands for PHP Extension and *Application* Repository. Now by some definitions there are four broad categories of class. Foundation domain: usually implemented by PHP itself e.g. the string functions (cf. Java String class) Architecture domain: seems to be where PEAR is actually focused. E.g. PEAR::HTTP_Client - in PHP you've got fsockopen and HTTP_Client builds on it Business domain: specific to a particular "business" problem scope. Perhaps PEAR::Science_Chemistry would fit here. Application domain: Used in a single application. In other words PEAR doesn't actually deliver applications (turn to hotscripts.com if you're looking for that) but rather architecural classes.