Hi Martin,

I focus on the second part...below

It was Martin Klapetek who said at the right time 20.07.2011 14:59 the following words:
On Wed, Jul 20, 2011 at 14:13, Sebastian Trueg <[email protected]> wrote:
Hi Martin,

On 07/19/2011 07:46 PM, Martin Klapetek wrote:
> 2) How to pick "the right data"?
> For example address. Imagine you have three NCO:PersonContacts as a
> grounding occurence in PIMO:Person and all three have different
> addresses. We must again choose one as the "main/default" address, but
> how should I write that into PIMO:Person? Same with emails, phones etc.
> Of course I can simply pick the address from the first NCO:PersonContact
> in the result set, but that may be the wrong one. What do you think?

IMHO use pimo:groundingOccurrence vs. pimo:occurrence. But maybe Leo can
shed some more light here since he created PIMO.

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.

The above sounds a bit shaky to me. You can also try german here to rephrase it.. :-)

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".
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.
Then there are many occurrences of Dirk all over the place.

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.

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.

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).





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.

identifiers:
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.
("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.

This is why it would be good to copy all identifiers over to the pimo:Person, to speed up lookups later.

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).

At least, thats the theory.

hth
Leo



-- 
Leo Sauermann, Dr.
CEO and Founder

mail: [email protected]
mobile: +43 6991 gnowsis           

Where your things come together,
Join:   http://www.gnowsis.com/about/content/newsletter
Follow: http://twitter.com/Refinder
Like:   http://www.facebook.com/Refinder
Learn:  http://www.gnowsis.com/about/blog
Try:    http://www.getrefinder.com/accounts/register/
____________________________________________________
_______________________________________________
Nepomuk mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/nepomuk

Reply via email to