Eric Kavanagh (EK): OK, and Byron, let’s drill into the underpinnings of this stuff because we talked earlier about APIs and third party data, and so forth, and ideally with a mashup, again, you want to enable these end users to mix and match data sets very easily. So how do you deal with that marshalling area of data. Do you, for example, are you just exposing a range of data feeds, and is that in your product, or do you leverage another product? How does that work?
Byron Igoe (BI): So specifically in our product, it’s all homegrown technology. The common context, so to speak, is as Jim would say, at the metadata, always. So it doesn’t really matter where the data is coming from, whether a relational database or other sources. As long as they are compatible types, you can still combine them, and in terms of enterprise mashups being used inside a company, you don’t have to limit yourself to these global contexts like geography. Within a particular firm, everybody knows what a customer is, and so they can combine information about that customer from different departments and get a total view of where they stand with a particular customer, and that is just one example. Products and many other subject areas are also common contexts for people to combine information.