<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Martin,<br>
<br>
I focus on the second part...below<br>
<br>
It was Martin Klapetek who said at the right time 20.07.2011 14:59
the following words:
<blockquote
cite="mid:CAPLgePoMpmoF3xsVAxn8Oe1QKF5NVct5XzjeLgWbYq0+b-uPuw@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Wed, Jul 20, 2011 at 14:13, Sebastian
Trueg <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:trueg@kde.org">trueg@kde.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Hi Martin,<br>
<div class="im"><br>
On 07/19/2011 07:46 PM, Martin Klapetek wrote: <br>
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
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. <br>
</div>
</div>
</blockquote>
<br>
The above sounds a bit shaky to me. You can also try german here to
rephrase it.. :-)<br>
<br>
The way it was designed is that you end up with one pimo:Person to
represent claudia:DirkHagemann - "The one and only Dirk Hagemann
which I know and whom I contact using various ways".<br>
Then there is the "grounding occurrence" for Dirk Hagemann, which
usually should map to the address book entry you would naturally
open when clicking on Dirk - think of it as the default data object
to open when the user wants to do something with Dirk.<br>
Then there are many occurrences of Dirk all over the place.<br>
<br>
In the PIMO description [1] (btw, thanks for using it, this helps a
lot and I need not to repeat), on page 10, in Section 6.5, there is
an example explaining what it means in practice. <br>
<br>
I would not go so far to add pimo:occurrences to every email that
Claudia and Dirk sent between each other. But adding multiple
address book entries is fine.<br>
<br>
Sticking with pimo:occurrence and pimo:groundingOccurrence should be
fine, I doubt that real-world systems will interpret
pimo:referencingOccurrence soon (a Facebook URI would be something
like this).<br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAPLgePoMpmoF3xsVAxn8Oe1QKF5NVct5XzjeLgWbYq0+b-uPuw@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<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. <br>
</div>
</div>
</blockquote>
<br>
identifiers:<br>
Copying the email addresses and other identifiers to the pimo:Person
will help you identifying arbitrary data. Given you have some new
data coming into the system, you may want to check if its already
known.<br>
("is this "Dirk" guy someone we know?). This is the "Check
identifiers" step in Section 11.1 on page 30, where you check if you
find a Pimo:Person that represents the resource you are working
with.<br>
<br>
This is why it would be good to copy all identifiers over to the
pimo:Person, to speed up lookups later. <br>
<br>
its data duplication, but it doesn't matter. The key point here is:
you want to be veeery quick when identifying if any new data does
mean something to you. And optimizing this read-accesses is always
good. Say you read 100 emails a day, roughly 10.000 a year. Quickly
checking them against the 1000 contacts you have is nicer if the
identifying information is all in one place (that would be the
pimo:Persons). <br>
<br>
At least, thats the theory. <br>
<br>
hth<br>
Leo<br>
<br>
<blockquote
cite="mid:CAPLgePoMpmoF3xsVAxn8Oe1QKF5NVct5XzjeLgWbYq0+b-uPuw@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div><br>
</div>
<div>Marty K.</div>
<div>[3] - <a moz-do-not-send="true"
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=ISO-8859-1">
<div>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
[1] <a moz-do-not-send="true"
href="https://sourceforge.net/apps/trac/oscaf/ticket/107"
target="_blank">https://sourceforge.net/apps/trac/oscaf/ticket/107</a><br>
[2] <a moz-do-not-send="true"
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 moz-do-not-send="true" href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/nepomuk"
target="_blank">https://mail.kde.org/mailman/listinfo/nepomuk</a><br>
</blockquote>
</div>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Leo Sauermann, Dr.
CEO and Founder
mail: <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@gnowsis.com">leo.sauermann@gnowsis.com</a>
mobile: +43 6991 gnowsis
Where your things come together,
Join: <a class="moz-txt-link-freetext" href="http://www.gnowsis.com/about/content/newsletter">http://www.gnowsis.com/about/content/newsletter</a>
Follow: <a class="moz-txt-link-freetext" href="http://twitter.com/Refinder">http://twitter.com/Refinder</a>
Like: <a class="moz-txt-link-freetext" href="http://www.facebook.com/Refinder">http://www.facebook.com/Refinder</a>
Learn: <a class="moz-txt-link-freetext" href="http://www.gnowsis.com/about/blog">http://www.gnowsis.com/about/blog</a>
Try: <a class="moz-txt-link-freetext" href="http://www.getrefinder.com/accounts/register/">http://www.getrefinder.com/accounts/register/</a>
____________________________________________________
</pre>
</body>
</html>