- From: Rob McCool <robm@robm.com>
- Date: Mon, 11 Aug 2003 13:32:44 -0700
- To: "Richard H. McCullough" <rhm@cdepot.net>
- Cc: public-rdf-tap@w3.org, KR-language <KR-language@YahooGroups.com>
> I think there are two unresolved issues. > > 1. The results are different. If this is due to some bugs in the > SuperClass/SubClass processing on the "old" tap server, > which no longer occur on the "new" panic server, you may > just want to ignore the differences. Likewise, if the differences > are due to "missing" type & subClassOf links on the "old" > tap server which have been added on the "new" panic server, > you may want to ignore them. I think the best thing would be for me to upgrade tap.stanford.edu; it's overdue. > 2. The "Property" crash on the panic server appears to be > a bug caused by trying to process a nonexistent "PropertyType" > class. You may want to add some error recovery for this > situation. I just reran this case to double check what's happening. > Here are the results. > ke$ PropertyType isg ?; > # INFO: GetData: kbdata = http://panic.stanford.edu/data/ > # INFO: GetData: subject = http://tap.stanford.edu/data/PropertyType > # INFO: GetData: predicate = subClassOf > # INFO: GetData: flags = > inverse=yes,includeSubClasses=yes,includeSuperClasses=y > es > Exception in thread "main" java.lang.OutOfMemoryError > ke$ ? has name = PropertyType; > # INFO: GetResource: kbdata = http://panic.stanford.edu/data/ > # INFO: GetResource: genus = Resource > # INFO: GetResource: value = PropertyType > # INFO: GetResource: count = 0 > ke$ Hmm. Okay, I'll take a look.
Received on Monday, 11 August 2003 16:32:53 UTC