Last modified: 2012-12-21 23:07:16 UTC
Hi, Using SMW 1.7 our Wiki has imported vocabulary concepts that have underscores or blanks in it (http://terms.gbif.org/wiki/MediaWiki:Smw_import_biorel). The RDF export however does not correctly export the rdf:about URL. Using the Special:Export_RDF feature (http://terms.gbif.org/wiki/Special:ExportRDF/Property%3Abiorel%3Aadjacent_to) the rdf:about URL becomes "to http://terms.gbif.org/biorel/1.0/adjacent" but it should be "http://terms.gbif.org/biorel/1.0/adjacent_to". That means the RDF becomes then gibberish. I see that the RDF exporter does not handle blanks or underscores. Can this be fixed? Thank you! Andreas
Examples: the vocabulary status vs="http://www.w3.org/2003/06/sw-vocab-status/ns#" defines a "term_status". We have a proxy defined for this here: http://terms.gbif.org/wiki/Property:vs:term_status with the import here: http://terms.gbif.org/wiki/MediaWiki:Smw_import_vs However, where used, it produces broken xml, because the namespace is defined as xmlns:vs="status http://www.w3.org/2003/06/sw-vocab-status/ns#" (starting with "status") and the RDF is created as: <vs:term rdf:datatype="http://www.w3.org/2001/XMLSchema#string">recommended</vs:term> i.e. with vs:term (which does not exist) instead of vs:term_status. We use the newest version of SMW (yet on mw 1.18, however), see http://terms.gbif.org/wiki/Special:Version For our project, this is a blocker.
I cannot reproduce this problem using current SMW master. I have created two test pages. One which is an exact copy of http://terms.gbif.org/wiki/MediaWiki:Smw_import_vs; the other a Property page containing the following lines: [[imported from::vs:term_status]] [[has type::String]] [[Term status::recommended]] (One should add the third line in a separate edit; otherwise the type is not stored when it is read.) The RDF export for the property page contains: xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#" and <vs:term_status rdf:datatype="http://www.w3.org/2001/XMLSchema#string">recommended</vs:term_status> as expected.
In Semantic MediaWiki 1.8 this problem does not occur any more.
