@prefix dc: .
<> dc:title "Local asumptions about contacts";
dc:description """
Contact, FOAF, vCard and LDIF vocabularies all cover contact information
for people. The mappings in contactStitch.n3 sometimes produce
ambiguities, which these asumptions will clear up. If they are true for your data.
They should not be taken as generally applicable facts and should be used with care.
.
""",
"$Id: contactAssumptions.n3,v 1.1 2007/02/19 02:22:31 timbl Exp $".
@prefix rdf: .
@prefix rdfs: .
@prefix owl: .
@prefix o2: . # Just for 'chain' missing from owl
@prefix wgs: .
@prefix v: .
@prefix foaf: .
@prefix con: .
@prefix ldif: .
@prefix link: .
@prefix doc: .
# Assuming that a person has only one work addres allows us to associate
# any work phone number with a work street, etc
con:work a owl:FunctionalProperty. # You can only have one work address etc
con:home a owl:FunctionalProperty.
# In western tradition people tend to like their given name first.
# In many countries, the opposite
con:givenName owl:equivalentProperty con:firstName. # Western only!
con:familyName owl:equivalentProperty con:lastName. # Assumpion made by much software.
# The FOAF system requires that a foaf:mbox is owned by only one person.
# The same with con:mailbox.
# This is not necessarily true of vcard and ldif mailboxes, but is often
# a useful asumption with a controlled dataset.
foaf:mbox owl:equivalentProperty ldif:email, v:email.
# ends