Ticket #253 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

[OWL2] Named datatype vocabulary not supported

Reported by: evren Owned by: evren
Priority: blocker Milestone: 2.1.0 Release
Component: pellet Version: 2.0.0-rc5
Keywords: Cc:
Time planned: 1d Time remaining: 1d
Time spent: 1d Estimated Number of Hours: 0.0
Add Hours to Ticket: 0 Billable?: yes
Total Hours:

Description

In the latest version of OWL 2 spec named datatypes are defined using owl:equivalentClass. This is currently not supported.

Change History

comment:1 Changed 3 years ago by evren

Jena loader neither prints a warning nor recognizes old-style named datatypes (uri used directly as a subject of onDatatype property).

comment:2 Changed 3 years ago by basebone

  • Owner changed from clark-parsia to basebone
  • Status changed from new to assigned

comment:3 Changed 3 years ago by basebone

  • Status changed from assigned to closed
  • Resolution set to fixed

(In [2263]) Jena loader now support datatype definitions using owl:equivalentClass. Node2term can now return datatypes when called with blank nodes. closes #253

comment:4 Changed 2 years ago by basebone

  • Status changed from closed to reopened
  • Resolution fixed deleted

Works with blank nodes and the Jena loader. Works with datatype branch and Jena loader. Does not work with owlapi anywhere.

comment:5 Changed 2 years ago by blazej

  • Status changed from reopened to new
  • Billable? set
  • Add Hours to Ticket set to 0
  • Milestone changed from No Release Event to 2.1.0 Release
  • Owner changed from basebone to evren
  • Estimated Number of Hours set to 0.0

comment:6 Changed 2 years ago by evren

(In [2624]) Support for datatype definition axioms in OWLAPI refs #253

comment:7 Changed 2 years ago by evren

  • Status changed from new to closed
  • Resolution set to fixed

(In [2651]) Add support for loading datatype definition axioms through Jena closes #253

comment:8 Changed 2 years ago by evren

(In [2652]) Updated data file for #253 refs #253

Note: See TracTickets for help on using tickets.