OSIDs are an architectural tool. These specifications are meant to be applied to solve integration problems. OSIDs lay down the tracks to
guide analysis and development of new systems. They do not optimize, or even address for that matter, tools and development environments to which programmers are accustomed. They also do not directly speak to business users who will trip over the service factoring and not understand the broad and often tongue-in-cheek terminology.
OSIDs need to be applied to business problems. Applications need to be mapped to service operations and data. Implementations needs to be designed. This is the job of a service architect. Don't throw OSIDs into a project and expect magic to happen. OSIDs didn't graduate from Hogwarts.