I'd look at what "official" interfaces the vendor exposes, meaning what documented, publicly-usable and vendor-supported mechanisms does the application expose. If the interface exposes coarse-grained services using OAGIS standards for the messages, that's great.
Is it "the way forward?" Well, it's probably one of several ways forward that you'll need to address throughout your enterprise and for each of the apps in your portfolio. -Rob --- In [email protected], Teresa Jones <[EMAIL PROTECTED]> wrote: > > However, I think that the point that Todd raised was important - if > an application vendor can say "yes, we have all these services > available in our application, and you can use them directly if you > wish" it could be a valuable consideration if a potential buyer > wanted to be able to pick and choose the services that they > actually wanted to use. But how could a vendor actually claim this? > I know that at least one apps vendor is now looking at > things like the OAGIS standards for 'business objects' and starting > to use these. Is this the way forward?
