« Pushing tin: the slashdot effect, web services and web infrastructure. | Main | On the Pepys »

OWL classloading: a language smell?

Semantic Web Research Group

More Java workarounds. This is a great example of using OWL to do get something useful done - runtime plugins (bonus points for not being applied AI). Even better example of why server-sided development today strongly favours using languages who have reflection as a first class feature and not an API -I'm pretty sure a reflection ontology isn't neccessary in Python, Javascript or S#.

January 6, 2003 10:40 AM


Mats Henricson
(January 6, 2003 07:57 PM #)

What do you mean? Like how Java is ignored as a server language?

Bill de hra
(January 6, 2003 10:57 PM #)

No. I meant that server sided programming leans toward having a facility to interpret code dynamically at runtime rather than a compile step. Java was not desgined to do that. The reflection API was bolted on after the need was identified, when Java was starting to become popular as a server-sided language. Language designers sometimes call what Java doesn't have, a meta-circular evaluator. Languages like Lisp, Javascript and Python come with such evaluators inbuilt (Lisp's evaluator is actually written in Lisp). So, since Javscript can run other Javascript, an ontology in OWL isn't required to describe what needs to be dynamically loaded.

Trackback Pings

TrackBack URL for this entry: