<br><br><div class="gmail_quote">On Thu, Jul 28, 2011 at 3:00 PM, Sebastian Trüg <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;">
<div class="im">On 07/27/2011 11:42 PM, Vishesh Handa wrote:<br>
><br>
><br>
> On Thu, Jul 28, 2011 at 12:46 AM, Sebastian Trüg <<a href="mailto:trueg@kde.org">trueg@kde.org</a><br>
</div><div class="im">> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>> wrote:<br>
><br>
</div><div class="im">> How about another parameter instead which specifies these kind of<br>
> properties in a list. Then a client can define what makes sense.<br>
><br>
><br>
> That would increase the complexity of storeResources from a clients<br>
> point of view. But I suppose we should provide overloaded variants of<br>
> storeResources.<br>
><br>
> The reason I want to specify this in the ontology is that I can't think<br>
> of a single use case where any of these properties would not be globally<br>
> identifying. Here is an idea : Maybe we could mark these properties as<br>
> InverseFunctionProperties ( inverse cardinality = 1 ), that way we know<br>
> for a fact that they are globally identifying.<br>
<br>
</div>This does sound very reasonable.<br>
BUT: the email is NOT such a property. It is a common use case for<br>
families to share an email address. Still, they are different people.<br></blockquote><div><br>Actually your use case did pop into my mind, and then it occurred to me that a family email should not be added with nco:hasEmailAddress to the contact.<br>
<br>Semantically, I would think a family would be represented by a nco:ContactGroup, and that contact group would collectively have one email address. Unfortunately nco:hasEmailAddress has a range of nco:Role. <br><br>What do you think?<br>
</div></div><br>-- <br><font color="#999999">Vishesh Handa</font><br>