You make a good point; I need to be careful with the terminology to make this clear.  The more correct form of my earlier question would be: Will BSG be providing an enterprise mashup tool as part of the SaaS offering, overseen by the Apps team, and integrated with the other SaaS offerings?  (One of the menu items, to borrow a term from Steve's presentation.)

I asked Tony Gonzalez for a list of useful mashup tools the list he provided at that time was:

http://www.jackbe.com/

http://www.kapowtech.com/

http://pipes.yahoo.com/pipes/

Where JackBe and Kapow are the two enterprise mashup tools.  I have also seen IBM Shareable Code discussed in conversations:

http://services.alphaworks.ibm.com/isc/

From what I have seen in JackBe's Presto introduction, that tool seems to be like what I had in mind.

I could see one of our clients using an enterprise mashup to construct a particular view of data and sending a link (entry point) back to a conversation in e.laborate to discuss the findings in the mashup. 

My goal may be easiest to understand in the context of a hypothetical example.  In this example we have an airline as a client who needs to analyze the effects of various fuel loading configurations.  We would like to do this through Simulation on Demand.

Assuming we have a mashup tool available, this could be implemented as two services.  One would be a mashlet (GUI component) that is fed a map reference and flight data.  It would render the flights and allow the user to view the system from various perspectives.  The second would be a transformation which would be fed flight data and some parameters and produce modeled flight data altered by the parameters.

The client could then use these services in a mashup.  So if they wanted to compare the flights on last Tuesday with what Tuesday would have been like with extra fuel loading, they could build a mashup to do that.  To see what the unaltered data looked like, they could map their company's flight data into the mashlet directly.  Then they could route that same flight data through the model service and map the output into another instance of the mashlet.  These two GUIs could be synchronized and presented on the same screen.

Now we have a standard visualizer mashlet for any airline client that can be reused.  In additon, if we have other visualizers available, the could map the data into those as well to dynamically create a new view of the same data.

If the results of last Tuesday with the modified parameters are interesting enough, they could link it into e.laborate and allow their coworkers to comment on the findings or run their own mashups to further investigate.

Does this make sense and sound reasonable?