Bill de hÓra: OWL classloading: a language smell?

Image Roll

www.flickr.com

Archives

July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
January 2000

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

OWL classloading: a language smell?

January 06, 2003 | co.comments icon co.mments

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

Comments

Mats Henricson

(January 6, 2003 07:57 PM #)

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

Bill de h�ra

(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:
http://www.dehora.net/mt/mt-tb.cgi/878