I read your explanation, understood that it's a kind of external javascript combining machine to limit http requests and size, while increasing reliability.
I then went to your site to check out the demo and found a page with lots and lots of external javascript requests, and something about a microformat.
I'm working on a second post about the microformat side of things. But here goes:
Suppose you accept that idea that instead of having 10 different web analytics tags on your page it would be better to have one tag (let's assume it's jsHub), then you can move up a level.
Rather than have each vendor define the metadata they want from the page, it's better to have a single set of metadata that all the vendors can use. So the point of the microformats is that they'll simplify even more the art of page tagging.
If vendors agreed to mark up the page name, or the products shown on the page, using a microformat then a single tag could read them and then fan the data out to various vendors. That way there's no ambiguity about what's being gathered.
I have a private web spider that's been following the top 1,000 web sites by traffic (plus the Fortune 1000) and the problem is that for the big ones they've got many, many tags like this per page.
"jsHub is a single piece of JavaScript (a "tag") that can handle reading different sorts of page information and then send them to many different vendors' products. One piece of code to send to Google Analytics, Omniture SiteCatalyst, WebTrends and Mixpanel."
I think his point is the same thing I'm having a problem understanding. I went to the demo site and saw 17 scripts loaded on the page using firebug; I assumed from the description there would be only one.
Microformats aside, I'm trying to understand the solution to the hub part because that sounds like a problem many people would be interested in fixing.
The problem jsHub is trying to solve is not "only ever load one piece of JavaScript in a page" it's "only have one piece of JavaScript for tracking, ad-serving, behavioural targetting, ...".
The reasons to do that are laid out in my blog post but the most important is consistency. If one piece of JavaScript gathers the data once and passes it to various vendors, then you know that the same data was sent, and was actually sent.
You'll probably find that most of the requests you saw in Firebug are for the Inspector tool (built using YUI2).
The jshub.js file is the only 'tag' needed on a website (+ jquery if not already in use) and is designed to provide a 'hub' API for each vendors plug-in to query the data collected and send it on its way to a receiving server so only one file need be maintained as vendors come and go.
I then went to your site to check out the demo and found a page with lots and lots of external javascript requests, and something about a microformat.
I'm still confused.