On 09/06/2011 04:13 PM, Markus Krötzsch wrote: > What I was wondering about is how to accomplish mapping. Technically, > SPARQL communicates all data via full URIs or literals. The latter is > easy enough (mapping to suitable datatypes) but the treatment of URIs > (both input and output) is not so clear to me. Writing and displaying > full URIs seems not such a nice way of presenting data. > > One can of course always query for the rdfs:label with all data to have > some hope for getting a user-readable label, but this may not always > work. And then it might be that some external URIs refer to an object in > the wiki, suggesting some more elaborate mapping mechanisms.
Yea, it seems that this "URI to wiki page title" [1] mapping problem is a very common one - it was mentioned in at least three talks at SMWCon, with all three having a very similar solution! :) Thus, I guess the optimal thing would have to solve this once and for all in one re-usable component. This should IMO be something where you can prioritize which properties to use in first hand, second hand etc... with an indefinite list of configurable fallbacks ... like rdfs:label as the first one, then dc:title, and so on and so on ... and as a last fallback the local/last part of the URI string itself can be used ... all as shown in slides 17-22 in the RDFIO talk [2]. Maximum configureability + sensible defaults could go a long way, I think. Though still, as you said, someone needs to do the work also :) (in getting a common component, in this case) // Samuel [1] Since, as I understand, all URI:s should be ultimately be mapped to a "wiki page", at least if persisted ... (?) [2] http://www.slideshare.net/SamuelLampa/hooking-up-semantic-mediawiki-with-external-tools-via-sparql -- Samuel Lampa --------------------------------------- Bioinformatician @ Uppsala University Blog: http://saml.rilspace.org --------------------------------------- ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
