Smw_import_ is plain broken
Closed, ResolvedPublic


Author: sergey.chernyshev

Smw_import_ is broken which prevents quite a few use cases for SMW to take place, including collaborative vocabulary creation and full-featured RDF export.

More info is available in this thread:

Markus, please update this with more details about the culprits - I'm not sure about what needs to be done:

There have indeed been some changes there somewhere around SMW 1.3/1.4. I
assumed that this is a very rarely used feature, hence did not send any
warnings. Effectively, there is currently no more datatype enforcement for
imported properties and you always need to specify the property datatype

Version: unspecified
Severity: major


bzimport created this task.May 28 2009, 4:14 PM

sergey.chernyshev wrote:

Applied changes that Li Ding submitted to the list (

Markus, it seems to work - does this solve the issue or there is anything else we should pay attention to?

stuart.chalmers wrote:

Have put my vote in for this bug. Have just started trying out tools (the main one being SMW) as a basis for collaborative editing of the International Virtual Observatory Alliance (IVOA) ontologies ( Would like to export the vocabularies using custom includes from various auxilliary ontologies. SMW seems ideal for this, if the include and export is broken.

Thanks for the patch (which actually did a good job as a workaround). The patch enforced unstubbing of all data values whenever retrieved with a certain method. The idea of unstubbing is to do it only whne needed, i.e. when a data value is actually accessed. For the data value that is used for importing, this was simply forgotten: it was never unstubbed before accessing its data. I have now inserted the on-demand unstubs and removed the "isValid" workaround in SVN. I close this bug now, since this is the main issue (and the major bug) that it refers to. If there are any other issues with import of vocabulary, please create new bug reports.

Add Comment