RDF properties to use for wiki titles on import - suggestions?
Wed, 2010-06-30 11:20 | by Samuel Lampa
One of the things we try to do in my GSoC project is to select suitable wiki titles when importing arbitrary RDF triples into Semantic MediaWiki (The full RDF URI:s are very ugly to use as wiki titles!).
Simply shorting the namespace in the entitiy's URI to it's prefix (as specified in the import data) could be a general fallback (see screenshot) but for many types of data it could be nice to make use of a property that puts some "natural language" label for the entity instead. We came up with this list of properties so far:
- http://semantic-mediawiki.org/swivt/1.0#page
- http://purl.org/dc/elements/1.1/title
- http://www.w3.org/2004/02/skos/core#preferredLabel
- http://xmlns.com/foaf/0.1/name
More suggestions?
Recent blog posts
- I created a Udemy course on my favourite linux commandline productivity techniques
- My top-languages-per-use-case list
- The smallest pipeable python script
- Vote for ProcessWire to be packaged as a BitNami image
- Calling Java from Python without the JVM startup latency: NailGun and JPype
- New Google+ communities: Bioclipse, Cheminformatics, Semantic MediaWiki
- Don't use Swedish keyboard with vim/screen/bash
- Easier debugging of Go programs on the command line with CGDB
- Profiling and creating call graphs for Go programs with "go tool pprof"
- Python-like generator functions in Go
Comments
re: more suggestions?
I suggest as general fallback: rdfs:label...
Make sure to turn on OWL reasoning, to also automatically recognize any predicate that subclasses rdfs:label..
Otherwise, have a look at the RDFa namespaces supported by Google and Yahoo... they support a few namespaces for particular 'things'... supporting the 'label' equivalents for those should be a good start...
For science, you might consider looking at ontologies for references, and take the equivalent for the bibtex key as index... ok, I'll email...
No OWL reasoning in ARC2 but...
Many thanks for the suggestions! ARC2 does not support OWL reasoning, but I might be looking at what can be done with this trick. Will look into the other suggestions too...
"The equivalent of a BibTex
"The equivalent of a BibTex key" ... didn't get that?