GNOME Bugzilla – Bug 762675
a photo not in the domain nco:Contact of property nco:representative
Last modified: 2016-05-13 22:31:07 UTC
Created attachment 322359 [details] log.txt Good day, In the logs, I get what I've attached as log.txt for about 67 different files.
Sorry, I submitted too early. Let me continue : At line 25 you can see that the photo in question gets a nco:representative property. As described at http://www.semanticdesktop.org/ontologies/2007/03/22/nco/#representative and https://git.gnome.org/browse/tracker/tree/src/ontologies/32-nco.ontology#n415 , this predicate takes a nco:Contact as a subject. It seems that this predicate is set at https://git.gnome.org/browse/tracker/tree/src/tracker-extract/tracker-extract-jpeg.c#n341 . I have only tested on version 1.6.1. I can attach the jpeg file in question on request. Have a good day.
Created attachment 323542 [details] [review] IPTC extractors : use nco:contributor for contact metadata 5a27279a7e07a9f1f0c58f663f4c290c397d4aff adds support for contact IPTC metadata and represents it with a nco:representative predicate. This contradicts the ontology that stipulates that the subject of a nco:representative predicate is a nco:Contact. Consequently, updates from extraction of files containing this IPTC field are rejected by the store. This fix uses the nco:contributor predicate instead. Official documentation at [1] says the field "Identifies the person or organisation which can provide further background information on the objectdata." Nco:contributor is therefore too narrow as not every such person need be a contributor. The adequate predicate doesn't exist but if it did it would definitely at least be a nao:annotation or more narrowly a nao:isRelated. But I deem these too broad because their range isn't a person or an organisation.
Thanks very much for the patch, it is now in git. Attachment 323542 [details] pushed as a05758c - IPTC extractors : use nco:contributor for contact metadata