Cory and Brand, (01)
I have some sympathy with both of your views, but I'd like to go
a bit further. (02)
Cory:
> My bias is that we have to capture the semantics of the domain in as
> technology neutral and user friendly way as possible. Everything you
> mentioned (as well as OWL) is optimized for other purposes, generally
> supporting a reasoner. (03)
I strongly agree with that point, and there is good R & D going in that
direction. But more work is needed to develop it further. See the
following article for more about the issues: (04)
http://www.jfsowa.com/pubs/futures.pdf
Future directions for semantic systems (05)
Brand:
> I think the right environment exists in a production software -
> http://semanticommunity.info/Build_SEMIC.EU_in_the_Cloud/Be_Informed_Video (06)
I agree with the following point from the web site:
> Public Sector processes are very much rule-driven. Most of the software,
> developed originally to support commercial enterprise, is not rule-driven,
> or is not capable of handling 10,000s of rules in a coherent way. (07)
But I am not as impressed with the video because it puts too much
of a burden on the people who have to develop the rules. A lot more
can be done with automated and semi-automated methods. That is the
primary theme of the futures.pdf article. (08)
On the other hand, I'll admit that the Be-Informed software can be
useful for many applications today. But if I were the developer,
I'd want to use much more automated methods. And if I were required
to maintain a rule-based system that somebody else had developed
using that tool, I would quit and look for another job. (09)
John (010)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J (011)
|