Wednesday, April 12, 2006
Anticipatory Web discussionà [home]
Anticipatory Web Challenge Problem à [link]
Community Centric Service Methodology Glass Bead Games
Pragmatics is about those things in the moment that uniquely characterize that moment. The foundational argument between first school and second is that the first school wishes to assert that knowledge engineers can design “semantics”, all of “semantics” at design time. None of the semantics can be left to execute time.
But this assertion goes in the face of normal business (non-IT business) activity, as well as normal experience in day to day living.
Example, a business agreement where there are specific issues related to the moment. These issues have to be addressed as conditions negotiated by the parties. The pragmatic axis is often seen when there are reconciliation of terminological differences. But we also see large pragmatic issues in responses to crisis, such as Katrina response. There are good reasons to suggest that a certain type of dysfunction of IT systems in these cases is because of first school thinking about “semantics” and not thinking about “pragmatics”. [1]
The OASIS draft BCM specification begins to make it clear how a number of contract blueprints can be developed using ontology, yes, but also allowing a choice between technology enabled contracts.
[1] There is no real benefit to this error, if it is an error, so one would expect that the second school viewpoint will replace the first school viewpoint. However, the first school viewpoint is so powerful today that there will still be an historical footnote.