<div class="gmail_quote">On Wed, Jul 20, 2011 at 14:13, Sebastian Trueg <span dir="ltr"><<a href="mailto:trueg@kde.org">trueg@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Martin,<br>
<div class="im"><br>
On 07/19/2011 07:46 PM, Martin Klapetek wrote:<br>
> Hi,<br>
><br>
> I'm working on a GSoC project which implements a proper PIMO:Person<br>
> creation from PIM data. However I'm facing some issues about which I<br>
> could use some advices.<br>
><br>
> 1) How to set a photo for PIMO:Person?<br>
> There may be several NCO:PersonContacts with their own photos, I can<br>
> pick just one (or let the user choose), but what ontology etc. should I<br>
> use to store the photo in?<br>
<br>
</div>I figured we already discussed that. The idea we had was to use<br>
nao:prefSymbol and nao:Symbol. To that end I even improved the<br>
documentation of the two[1].<br>
There are basically 2 ways to do this (in general, for your case it will<br>
probably always be the second one):<br>
1. Use a freedesktop icon via nao:FreedesktopIcon and nao:iconName<br>
2. Use double-typing by adding type nao:Symbol to a nfo:RasterImage<br>
which is stored on disk (nfo:FileDataObject) or on the web<br>
(nfo:RemoteDataObject or the upcoming nfo:WebResource[2]).<br></blockquote><div><br></div><div>Well yes, we started discussing it but it was right before you had to leave, so we never actually got to it :) So if I got it right, I need a resource with types nao:Symbol and nfo:RasterImage, which will hold property with the image url and then add this resource to Person with nao:prefSymbol, right?</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> 2) How to pick "the right data"?<br>
> For example address. Imagine you have three NCO:PersonContacts as a<br>
> grounding occurence in PIMO:Person and all three have different<br>
> addresses. We must again choose one as the "main/default" address, but<br>
> how should I write that into PIMO:Person? Same with emails, phones etc.<br>
> Of course I can simply pick the address from the first NCO:PersonContact<br>
> in the result set, but that may be the wrong one. What do you think?<br>
<br>
</div>IMHO use pimo:groundingOccurrence vs. pimo:occurrence. But maybe Leo can<br>
shed some more light here since he created PIMO.<br></blockquote><div><br></div><div>So pimo:occurence for everything and pimo:groundingOccurence for the "default" data? But that doesn't really work, because think of three properties - email, phone and an address. Each one of these is a separate NCO:PersonContact. So they should all be pimo:groundingOccurence then, but if for example the NCO:PersonContact for address have also email, we're doomed. </div>
<div><br></div><div>Btw. when reading the PIMO guide [3], it says on page 31 to copy all identifiers. Do I understand it correctly that it should copy all identifiers from new NCO:PersonContact into PIMO:Person (and should I do that too)? This seems like an unnecessary data duplication. </div>
<div><br></div><div>Marty K.</div><div>[3] - <a href="http://www.semanticdesktop.org/ontologies/2007/11/01/pimo/v1.1/pimo_v1.1.pdf">http://www.semanticdesktop.org/ontologies/2007/11/01/pimo/v1.1/pimo_v1.1.pdf</a></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
[1] <a href="https://sourceforge.net/apps/trac/oscaf/ticket/107" target="_blank">https://sourceforge.net/apps/trac/oscaf/ticket/107</a><br>
[2] <a href="https://sourceforge.net/apps/trac/oscaf/ticket/105" target="_blank">https://sourceforge.net/apps/trac/oscaf/ticket/105</a><br>
_______________________________________________<br>
Nepomuk mailing list<br>
<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/nepomuk" target="_blank">https://mail.kde.org/mailman/listinfo/nepomuk</a><br>
</blockquote></div><br>