Ron Alford

Show:

What's happening?

  • RDFXML Parser drops space from literal

    Parsing a property assertion like gives the empty string literal.

    2009-12-30 19:22:15 UTC in OWL API

  • Turtle parser throws exception on labeled bnodes

    java.lang.RuntimeException: Prefix not registered for prefix name: _: at org.semanticweb.owlapi.util.DefaultPrefixManager.getIRI(DefaultPrefixManager.java:154) at uk.ac.manchester.cs.owl.owlapi.turtle.parser.TurtleParser.getIRIFromQName(TurtleParser.java:70) at uk.ac.manchester.cs.owl.owlapi.turtle.parser.TurtleParser.parseNodeID(TurtleParser.java:245) at...

    2009-12-30 19:07:13 UTC in OWL API

  • getImportsClosure cache inconsistency

    Calling getImportsClosure after manually adding an ontology import but before calling manager.handleImportRequest causes an inconsistency between getImports() and getImportsClosure(). Example attached.

    2009-12-22 16:13:19 UTC in OWL API

  • SWRL roundHalfToEven has an optional 3rd argument

    In api/src/main/java/org/semanticweb/owlapi/vocab/SWRLBuiltInsVocabulary.java, ROUND_HALF_TO_EVEN("roundHalfToEven", 2), specifies that roundHalfToEven only takes two arguments, when it can take an optional integer argument for precision. There are probably more that have the same issue. This causes the Manchester syntax parser to fail. Maybe the vocab class needs a min and max arity?.

    2009-11-02 16:31:48 UTC in OWL API

  • Comment: Definition tracker does not recognize builtins

    Two issues: Why does isDefined not just call isBuiltin() just like the version of this class in OWL API v2? Also, RDFS:Literal is not showing up as a built-in, and I'm not sure how to patch it into OWLDatatypeVocabulary or OWL2Datatype. Specifically, I'm not sure which category tag it gets.

    2009-10-05 15:56:54 UTC in OWL API

  • Definition tracker does not recognize builtins

    com.clarkparsia.owlapi.explanation.util.DefinitionTracker.isDefined(OWLEntity entity) should return true on built-in datatypes.

    2009-09-30 18:33:17 UTC in OWL API

  • Add OWLOntologyInputSource mapping

    Perhaps change OWLOntologyIRIMapper.getPhysicalURI(IRI ontologyIRI) to .getOWLOntologySource(IRI ontologyIRI). This would make for a more flexible load system. In particular, this would help with OWLWG-Test, where the ontologies are embedded as literals within an rdf document.

    2009-09-14 19:53:04 UTC in OWL API

  • Comment: Namespace conflict (OWL API v2 vs v3)

    modularity has the same issue (fixed in my sources, too).

    2009-09-09 14:51:44 UTC in OWL API

  • Comment: Namespace conflict (OWL API v2 vs v3)

    I have a patch ready to change the package in v3 to be com.clarkparsia.owlapi.explanation. Should I commit?.

    2009-09-09 14:15:01 UTC in OWL API

  • Namespace conflict (OWL API v2 vs v3)

    In the debugging package, both OWL API v2 and v3 have a com.clarkparsia.explanation, meaning there is a conflict when trying to use both OWL APIs.

    2009-09-09 13:15:51 UTC in OWL API

About Me

  • 2001-03-24 (9 years ago)
  • 180962
  • ronwalf (My Site)
  • Ron Alford

  • C Common Lisp Java Perl Object Oriented Networking

Send me a message