Re: Updated vCard in OWL

Ah, I meant it might be nice to say that an individual org:Organization is the same as another individual vcard:Org. owl:sameAs may be inappropriate to express that relation.

Otherwise, I don't see much overlap between ORG and vCard. Here are the classes and properties that could possibly be made to overlap:

org:Organization vcard:Org
org:OrganizationUnit org:OrgUnit
org:Role vcard:Role
org:Site vcard:Location

org:memberOf vcard:hasOrg
org:hasUnit vcard:hasOrgUnit
org:hasRole vcard:hasRole
org:hasMember vcard:hasMember

On 2012-10-12, at 11:09 AM, Dave Reynolds wrote:

> On 12/10/12 15:47, James McKinney wrote:
>> It would be nice to be able to say that an org:Organization is owl:saveAs another vcard:Organization. I assume they would have to be equivalent classes to do that.
> 
> No, owl:sameAs is a stronger statement but in any case I don't think org:Organization and vcard:Organization are owl:equivalentClass.
> 
> Dave
> 
>> On 2012-10-12, at 3:08 AM, Phil Archer wrote:
>> 
>>> Renato Iannella posted a message to the Semantic Web list today that many in this group will have seen [1]. He's seeking comments on the work he's doing to update the vCard in RDF schema. Given that vCard is explicitly used in ORG and includes things like organisations and roles... should we look for overlaps and seek the inclusion of equivalent class or property relationships in that (or whatever is appropriate)?
>>> 
>>> 
>>> 
>>> [1] http://lists.w3.org/Archives/Public/semantic-web/2012Oct/0030.html
>>> --
>>> 
>>> 
>>> Phil Archer
>>> W3C eGovernment
>>> http://www.w3.org/egov/
>>> 
>>> http://philarcher.org
>>> +44 (0)7887 767755
>>> @philarcher1
>>> 
>> 
>> 
> 
> 

Received on Friday, 12 October 2012 15:41:21 UTC