Hi, Had a few thoughts on potential add-ons. (with business usecases in mind).
These definitely fall outside the basic spec and may not be as technically sound, and that's why i would appreciate some critique. 1. Can Hubs be engineered to understand the message-content they handle? If hubs are made content-aware (atleast through meta- information/tags if not the entire content, keeping in mind security constraints), they could double up as yellow-pages. This would enable them to project themselves on their "reach" to other hubs in a distributed topology, or to publishers so that publishers put their best foot forward, offerings-wise, before linking with a given hub. Subscribers could further state their interest in topic-categories on Hubs and this would give further useful information to potential publishers to adapt their business offerings accordingly. 2. Is there any activity in the pipeline to evolve a standard set of objects per business, now that there are (widely used)Hubs? Are Hubs a nice place to enforce standards in business objects that pass through them? (having a series of "superset" business objects, with standardized field definitions per business, would reduce so much effort in basic data-mapping, later in the ESBs.) 3. Is there a directory to discover Hubs? Alternately, instead of having exclusive directories, why not place a mini-directory inside each hub/select hubs pointing to local hubs? This is analogous to asking around for directions on the way to a place and leaving a trail of knowledge on the way, rather than reaching a centralized board displaying directions. If there were knowledge-based Hubs, the knowledge-bank of each hub would keep increasing this way. The gist is -- can one add a business dimension to this? Regards, Niranjan
