Don't confuse the capability to do inference with the response to the knowledge inferred.
For example, if you own the both system which holds the insurance info and the system that holds the user info, you could use the information to reject entering the inconsistent data in the first place. What you do with it is almost beside the point. The value of having this capability in a way which still allows your systems to be loosely coupled should be fairly obvious.
Drupal Government Days: Drupal and the semantic web
Posted Apr 21, 2011 18:10 UTC (Thu) by Tara_Li (subscriber, #26706)
[Link]
Only as long as long as someone actually does it. It's like the wonderful world of tagging - great, as long as someone actually *enters* all of the tags on the data, rationalizes and fixes typos, links synonyms in some manner. What people *WILL* do seldom matches what they *should* do.
This "semantic web" stuff is well and good - I just don't think it's really "all that". After all, someone has to actually get around to asking the computer, in the example provided, to check age against length of time holding the policy.
Drupal Government Days: Drupal and the semantic web
Posted Apr 21, 2011 18:30 UTC (Thu) by vonbrand (subscriber, #4458)
[Link]
Exactly. The big advantage Google had over Altavista and other early search engines was that they didn't rely on human-entered data descriptions, just raw computer power (and let the user sort it out). Still mostly the same, AFAICS.
Drupal Government Days: Drupal and the semantic web
Posted Apr 22, 2011 3:16 UTC (Fri) by raven667 (subscriber, #5198)
[Link]
Judging myself from some of the example it seems organizations like Google are the primary consumers of this data, they retrieve it, index it, store it and answer questions using it. They have the data and the raw compute power to do interesting things with it should they find a market for the answers.