In a recent post I mentioned comments by Sir Tim Berners-Lee concerning the overlap between enterprise information models and semantic web ontology supporting the concept of linked data. Sir Berners-Lee argued that overlap is already sufficient to have a transformative effect on mainstream IT. I think he is right, but also that we are not there yet. There are many obstacles to adoption, not the least of which is the inertia of enterprise IT. Disruptive approaches to software development typically require ten years or so to cross the chasm from visionary and early adopters to the mainstream. We are only a few years into this and the technology is not ready.
First, let’s establish that there is plenty of semantics available for reuse now. There are existing models, some of which are well-designed, mature, and widely used. Unfortunately, most of what exists has little apparent relevance to enterprises. There is little on this diagram that would draw the attention of an enterprise architect, for example.
Continue reading “Extended Enterprise Ontology”
James Taylor’s blog today on rules being core to BPM and SOA in which he discussed reuse had a particularly strong impact on me following a trip yesterday. During a meeting with the insurance and retail banking practice leaders at a large consulting firm, we looked for synnergies between applications related to investment and applications related to risk. Of course, during that conversation, we discussed whether operational rules could be usefully shared across these currently siloed areas, but we landed up discussing what they had in common in terms of business concepts, definitions, and fundamental truths or enterprise wide governance. It was clear to us that this was the most fruitful area to develop core, reusable knowledge assets.
In his post, James agrees with the Butler Group’s statement:
Possibly the most important aspect of a rules repository, certainly in respect of the stated promise of BPM, Service Oriented Architecture (SOA), and BRMS, is the ability for the developer to re-use rules within multiple process deployments.
I have several problems with this statement: Continue reading “Rules are not enough. Knowledge is core to reuse.”