- Accessing credible or trustworthy data has been a problem for the insurance industry for many years. If this problem is not resolved how can any mashup help? How will a mashup help?
- Is there a seamless sign-on?
- As users create mashups, can this be difficult for IT to manage? Errors occur, changes do too. In a mashup, how does IT know who consumes the mashups and alert them?
- In a certain way, you are turning the user base into a global IT development unit.
- Do you interface with UDDI directories?
- If services require passing parameters (example: department_id), can your GUI tool allow passing parameter?
- Does your security model supports RBAC and ABAC authorization?
- How do build a feedback loop to IT?
- Users will out! Mashups are an evolutionary extension of the mainframe-vs-PC wars of 1970-80s. IT must manage rather than control user and department level business automation extensions (my definition of mashup). Back then our greatest concern was not to impede such evolution but finding new ways of managing and sharing it. Are these Mashup Patterns focused toward the business-level development, IT management, or both?
- Are Mashups Stateless or Stateful applications?
- How critical is it that the organization has a cross Biz Unit Enterprise Architecture body to enable (publish) access to a data silo(s), as well as publish mashups for reuse?
- Given that enterprise mashups are created by everyday users, are there any user interface (UI) related best practices or guidelines for building these mashups?
- How is this different from what we could do from a ESB or EAI framework?
- How do you mashup services that have access controls in place such as userid and password? Can JackBe pass userid and password to systems for the user or prompt the user for the information?
- Is JackBe an internationalized application to support localization? Does it have LOCALE support for Jackbe Services/Wires/Admin etc?
