W3C home > Mailing lists > Public > semantic-web@w3.org > October 2013

AW: vCard Ontology MD questions

From: Marcel Fröhlich <mfroehlich@brox.de>
Date: Mon, 28 Oct 2013 18:16:44 +0000
To: "Klee, Carsten" <Carsten.Klee@sbb.spk-berlin.de>
CC: "semantic-web@w3.org" <semantic-web@w3.org>
Message-ID: <FB53B649C5C98F499788C102807AD68B01F34B15@SRV-H-EXCH-01.brox.de>
Hello Carsten,

My understanding is that the organization ontology has different groups of elements to model different aspects 
(org structure, org history/provenance, location info, reporting structure).
The way you plan to do it, somehow mixes up the aspect of location with the aspect of organizational roles and org structure.
Maybe you could think of OrganizationalUnits rather than only Sites in your model. The Site class is meant for the location aspect only.
Why model organizational roles on the level of business card information (inside vcard namespace)?
The organization ontology has a neat set of primitives to model roles within the org namespace.

On the other hand, I understand that you are already happy with the solution you found :-)

Best regards, Marcel

-----Ursprüngliche Nachricht-----
Von: Klee, Carsten [mailto:Carsten.Klee@sbb.spk-berlin.de] 
Gesendet: Montag, 28. Oktober 2013 12:59
An: 'Renato Iannella'
Cc: semantic-web@w3.org; Rolschewski, Johann; 'Adrian Pohl' (pohl@hbz-nrw.de); Heise, Andreas; voss@gbv.de
Betreff: AW: vCard Ontology MD questions

> 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:

    vcard:hasAddress $addr ;
    vcard:hasEmail $email1, $email2, $email3 ;
    vcard:hasTelephone $telephone1, $telephone2, $telephone3 .
    vcard:hasRelated $contact3 .

    vcard:hasRelated $email1, $email2, $telephone1, $telephone2, $contact1, $contact2 .

    vcard:hasRole $contact1 .

    vcard:hasRole $contact2 .

    vcard:hasRole $contact3 .

    dc:description "contact1 info" ;
    vcard:role "role1" .

    dc:description "contact2 info" .
    vcard:role "role2" . 

    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.


Received on Monday, 28 October 2013 18:17:14 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:35 UTC