incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Reynolds (JIRA)" <>
Subject [jira] [Commented] (JENA-112) enhance schemagen to import ontologies for inference
Date Wed, 07 Sep 2011 14:02:09 GMT


Dave Reynolds commented on JENA-112:

In working with Data Cube one would normally explicitly specify the rdf:Property type in any
case (c.f. Payments ontology example). I don't object to Schemagen growing options for explicit
import processing but it only seems relevant to OWL Full ontologies and those tend to follow
this defensive if-in-doubt-make-it-explicit guideline.

> enhance schemagen to import ontologies for inference
> ----------------------------------------------------
>                 Key: JENA-112
>                 URL:
>             Project: Jena
>          Issue Type: Improvement
>          Components: Jena
>            Reporter: Brian McBride
>              Labels: inference, schemagen
> I have an ontology for publishing linked data that is based on the data cube ontology
[1].  It defines properties as AttributeProperties.  The data cube ontology defines AttributeProperties
to be a subclass of rdf:Property.  However, even with inference turned on, schemagen does
not recognise my AttributeProperties as properties, presumably because it has not loaded the
cube ontology and thus cannot infer that they are properties.  Instead it treats them as resources.
> e.g. for
> [[
> :using
> 		a					qb:AttributeProperty;
> 		rdfs:label			"using"@en;
> 		rdfs:comment		"An instrument used in making a measurement"@en;
> 		rdfs:isDefinedBy	<>;
> ]]
> schemagen produces
> [[
>     /** <p>An instrument used in making a measurement</p> */
>     public static final Resource using = m_model.createResource( ""
> ]]
> It would be good if schemagen could process imported ontologies, either including them
directly from the web or by enabling the user to specifiy files where they may be found.
> [1]

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message