Page History

...

• recently made improvements to startup time after the first-time startup (saving approximately 20 seconds)
• modularity improvements
  • search indexing (VIVO-869 being the parent issue)
  • reasoner (VIVO-778)
  • triple store (RDFService) (VIVO-225)
• VIVO-909 and VIVO-907 – if change one of the ontology files, the entire reasoning has to be re-done – the TBox reasoning that takes 20 seconds triggers a full ABox re-inferencing
  • pointed out by Eliza in testing with Virtuoso
  • a maxCardinality property was being specified as a non-negative integer but was stored as an integer, so on startup the TBox reasoner interpreted an ontology change
    • saw the same thing in Virtuoso and TDB, but doesn't show the problem with SDB
      • got around it with a kluge to the Virtuoso driver – would like to distribute with that patch if can't get around it
    • worth a couple more hours to pursue – may be an issue in the general RDFService code, that is not used for SDB
  • steps to address this may also shave more time off the startup time
• We will also need to distribute a patch for a SPARQL query syntax that Virtuoso doesn't accept
• Reasoner improvements
  • Open questions – is LGPL an acceptable license to DuraSpace? – the Lesser release removes the copyleft provision provided you don't modify the code itself
  • Can now try alternate reasoners in a matter of a couple of hours – given the refactoring
  • So far is comparing output to what Pellet did, without full confidence in which of those types of reasoning actually influence VIVO behavior and hence are required for a reasoner used by VIVO
  • We still have to determine the best alternative reasoner to Pellet to use
  • All of the SimpleReasoner unit tests still make reference to a Pellet class
• Updating the VCard ontology
  • We will swap in the updated 5/14 W3C VCard ontology and test in VIVO
  • The most likely cause of problems will be in determining the primary email address and primary contact

VIVO application code

...