> Hi Carsten, I can see the utility of having hasIndividual, > hasOrganisation, hasLocation, and hasGroup properties for clearer > relationships between the four vCard Kinds. > > In some respects, hasContact is a short-cut for hasRelated to a Resource > of type "Contact". > We could apply the same idea to the 20 relationship types [1]. Hence we > could also have a hasAgent property, and even a hasSweetheart (my > favourite ;-) I see. Then I will stick to the hasRelated property. And I think my solution then will look like: $orgOrSite vcard:hasAddress $addr ; vcard:hasEmail $email1, $email2, $email3 ; vcard:hasTelephone $telephone1, $telephone2, $telephone3 . vcard:hasRelated $contact3 . $addr vcard:hasRelated $email1, $email2, $telephone1, $telephone2, $contact1, $contact2 . $email1 $telephone1 vcard:hasRole $contact1 . $email2 $telephone2 vcard:hasRole $contact2 . $email3 $telephone3 vcard:hasRole $contact3 . $contact1 dc:description "contact1 info" ; vcard:role "role1" . $contact2 dc:description "contact2 info" . vcard:role "role2" . $contact3 dc:description "contact3 info" . vcard:role "role3" . Now all telephone numbers and email addresses can be queried directly for $orgOrSite and the hierarchy and the roles are also represented. Cheers! CarstenReceived on Monday, 28 October 2013 11:59:47 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:35 UTC