On Thursday 10 May 2012 21:06:30 Jona Christopher Sahnwaldt wrote: > I think what Marco meant was: the mapping says it's an object > property, so we should extract a URI, even if the property value is > just a string.
Right. > In the case of the musician infoboxes on it wiki, that would work, but > in many other cases, it wouldn't. For example: > http://en.wikipedia.org/wiki/Glenn_Danzig contains "label = Plan 9, > Evilive". Just that string, no links. We could use a heuristic to > split the string into multiple links etc, but I don't think there's a > good, clean solution. With a naive approach we would extract > <http://en.dbpedia.org/resource/Plan_9,_Evilive>, which would be > wrong. We should use the same euristic used by the wikimedia template engine, that way it would match with the proper wikipedia page. > There is a simple rule though: If the Wikipedia template renders > strings as links, then we should extract strings as URIs. Otherwise we > shouldn't. > > The problem is that our code can't find out what the template does > (well, it could, but that would be almost as hard as rendering > templates). But humans can. So to implement that rule, we have to add > a feature to the mappings wiki, as I described in my previous mail, so > users can add a flag saying "yes, plain string values in this property > should be extracted as URIs". But that isn't implicit if the mapping creator maps it to ObjectProperty ? > It seems that Italian Wikipedia templates often work like this, while > English templates rarely do. To make that behavior possible, the > Italian templates use multiple properties like genere, genere2, > genere3 etc, while the English templates use one property which the > editors can fill with links or strings as they like. This again means to me that we should trust mappings. -- ESC:wq ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
