NCO - Nepomuk Contact Ontology

Namespace: http://www.semanticdesktop.org/ontologies/2007/03/22/nco# (Version 0.9.0)

Authors:

Antoni Mylka

DFKI

Leo Sauermann

DFKI

Michael Sintek

DFKI

Ludger van Elst

DFKI

Maintainers:

Sebastian Trueg

Mandriva

Contributors:

Evgeny Egorochkin

KDE

Christiaan Fluit

Aduna

Abstract

The Nepomuk Contact Ontology describes contact information, common in many places on the desktop. It evolved from the VCARD specification (RFC 2426) and has been inspired by the Vcard Ontology by Renato Ianella. The scope of NCO is much broader though.

Table of Contents

Classes Overview
Properties Overview
Ontology Visualization
Introduction
Scope
Description of classes and properties
Usage
Examples
References
NCO Vocabulary Summary
Description of Classes
Description of Properties

Classes Overview

nco:Affiliation - Aggregates three properties defined in RFC2426. Originally all three were attach...
nco:AudioIMAccount (deprecated) - Deprecated in favour of nco:imCapabilityAudio.
nco:BbsNumber - A Bulletin Board System (BBS) phone number. Inspired by the (TYPE=bbsl) paramete...
nco:CarPhoneNumber - A car phone number. Inspired by the (TYPE=car) parameter of the TEL property as ...
nco:CellPhoneNumber - A cellular phone number. Inspired by the (TYPE=cell) parameter of the TEL proper...
nco:Contact - A Contact. A piece of data that can provide means to identify or communicate wit...
nco:ContactGroup - A group of Contacts. Could be used to express a group in an addressbook or on a ...
nco:ContactList - A contact list, this class represents an addressbook or a contact list of an IM ...
nco:ContactListDataObject - An entity occuring on a contact list (usually interpreted as an nco:Contact)
nco:ContactMedium - A superclass for all contact media - ways to contact an entity represented by a ...
nco:DomesticDeliveryAddress - Domestic Delivery Addresse. Class inspired by TYPE=dom parameter of the ADR prop...
nco:EmailAddress - An email address. The recommended best practice is to use mailto: uris for insta...
nco:FaxNumber - A fax number. Inspired by the (TYPE=fax) parameter of the TEL property as define...
nco:Gender - Gender. Instances of this class may include male and female.
nco:IMAccount - An account in an Instant Messaging system.
nco:IMCapability - Capabilities of a cetain IMAccount.
nco:IMStatusType - The status type of an IMAccount. Based on the Connection_Presence_Type enumerati...
nco:InternationalDeliveryAddress - International Delivery Addresse. Class inspired by TYPE=intl parameter of the AD...
nco:IsdnNumber - An ISDN phone number. Inspired by the (TYPE=isdn) parameter of the TEL property ...
nco:MessagingNumber - A number that can accept textual messages.
nco:ModemNumber - A modem phone number. Inspired by the (TYPE=modem) parameter of the TEL property...
nco:OrganizationContact - A Contact that denotes on Organization.
nco:PagerNumber - A pager phone number. Inspired by the (TYPE=pager) parameter of the TEL property...
nco:ParcelDeliveryAddress - Parcel Delivery Addresse. Class inspired by TYPE=parcel parameter of the ADR pro...
nco:PcsNumber - Personal Communication Services Number. A class inspired by the TYPE=pcs paramet...
nco:PersonContact - A Contact that denotes a Person. A person can have multiple Affiliations.
nco:PhoneNumber - A telephone number.
nco:PostalAddress - A postal address. A class aggregating the various parts of a value for the 'ADR'...
nco:Role - A role played by a contact. Contacts that denote people, can have many roles (e....
nco:VideoIMAccount (deprecated) - Deprecated in favour of nco:imCapabilityVideo.
nco:VideoTelephoneNumber - A Video telephone number. A class inspired by the TYPE=video parameter of the TE...
nco:VoicePhoneNumber - A telephone number with voice communication capabilities. Class inspired by the ...

Properties Overview

nco:addressLocation - The geographical location of a postal address.
nco:belongsToGroup - Links a Contact with a ContactGroup it belongs to.
nco:birthDate - Birth date of the object represented by this Contact. An equivalent of the 'BDAY...
nco:blogUrl - A Blog url.
nco:contactGroupName - The name of the contact group. This property was NOT defined in the VCARD s...
nco:contactMediumComment (deprecated) - A comment about the contact medium. (Deprecated in favor of nie:comment or nao:d...
nco:contactUID - A value that represents a globally unique identifier corresponding to the indiv...
nco:containsContact - A property used to group contacts into contact groups. This property was NO...
nco:contributor - An entity responsible for making contributions to the content of the Information...
nco:country - A part of an address specyfing the country. Inspired by the seventh part of the ...
nco:creator - Creator of an information element, an entity primarily responsible for the creat...
nco:department - Department. The organizational unit within the organization.
nco:emailAddress -
nco:end - End datetime for the role, such as: the datetime of leaving a project or organiz...
nco:extendedAddress - An extended part of an address. This field might be used to express parts of an ...
nco:foafUrl - The URL of the FOAF file.
nco:fullname - To specify the formatted text corresponding to the name of the object the Contac...
nco:gender - Gender of the given contact.
nco:hasAffiliation - Links a PersonContact with an Affiliation.
nco:hasContactMedium - A superProperty for all properties linking a Contact to an instance of a contact...
nco:hasEmailAddress - An address for electronic mail communication with the object specified by this c...
nco:hasIMAccount - Indicates that an Instant Messaging account owned by an entity represented by th...
nco:hasIMCapability - Indicates that an IMAccount has a certain capability.
nco:hasLocation - Geographical location of the contact. Inspired by the 'GEO' property specified i...
nco:hasPhoneNumber - A number for telephony communication with the object represented by this Contact...
nco:hasPostalAddress - The default Address for a Contact. An equivalent of the 'ADR' property as define...
nco:hobby - A hobby associated with a PersonContact. This property can be used to express ho...
nco:imAccountType - Type of the IM account. This may be the name of the service that provides the IM...
nco:imID - Identifier of the IM account. Examples of such identifier might include ICQ UINs...
nco:imNickname - A nickname attached to a particular IM Account.
nco:imStatus - Current status of the given IM account. When this property is set, the nco:imSta...
nco:imStatusMessage - A feature common in most IM systems. A message left by the user for all his/her ...
nco:imStatusType - Current status type of the given IM account. When this property is set, the nco:...
nco:isAccessedBy - Indicates the local IMAccount by which this IMAccount is accessed. This does not...
nco:isBlocked - Indicates that this IMAccount has been blocked.
nco:key - An encryption key attached to a contact. Inspired by the KEY property defined in...
nco:locality - Locality or City. Inspired by the fourth part of the value of the 'ADR' property...
nco:logo - Logo of a company. Inspired by the LOGO property defined in RFC 2426 sec. 3.5.3
nco:nameAdditional - Additional given name of an object represented by this contact. See documentatio...
nco:nameFamily - The family name of an Object represented by this Contact. These applies to peopl...
nco:nameGiven - The given name for the object represented by this Contact. See documentation for...
nco:nameHonorificPrefix - A prefix for the name of the object represented by this Contact. See documentati...
nco:nameHonorificSuffix - A suffix for the name of the Object represented by the given object. See documen...
nco:nickname - A nickname of the Object represented by this Contact. This is an equivalent of t...
nco:note - A note about the object represented by this Contact. An equivalent for the 'NOTE...
nco:org - Name of an organization or a unit within an organization the object represented ...
nco:phoneNumber -
nco:photo - Photograph attached to a Contact. The DataObject referred to by this property is...
nco:pobox - Post office box. This is the first part of the value of the 'ADR' property as de...
nco:postalcode - Postal Code. Inspired by the sixth part of the value of the 'ADR' property as de...
nco:publisher - An entity responsible for making the InformationElement available.
nco:publishesPresenceTo - Indicates that this IMAccount publishes its presence information to the other IM...
nco:region - Region. Inspired by the fifth part of the value of the 'ADR' property as defined...
nco:representative - An object that represent an object represented by this Contact. Usually this pro...
nco:requestedPresenceSubscriptionTo - Indicates that this IMAccount has requested a subscription to the presence infor...
nco:role - Role an object represented by this contact represents in the organization. This ...
nco:sound - Sound clip attached to a Contact. The DataObject referred to by this property is...
nco:start - Start datetime for the role, such as: the datetime of joining a project or organ...
nco:streetAddress - The streed address. Inspired by the third part of the value of the 'ADR' propert...
nco:title - The official title the object represented by this contact in an organization. E...
nco:url - A uniform resource locator associated with the given role of a Contact. Inspired...
nco:voiceMail - Indicates if the given number accepts voice mail. (e.g. there is an answering ma...
nco:websiteUrl - A url of a website.

Ontology Visualization

Figure 16. 


Introduction

The purpose of the Nepomuk Contact Ontology (NCO) is to describe contact information. It is one of the core elements of every Personal Information Management system and Nepomuk is no exception. Origins of this ontology can be traced back to VCARD specification published in [RFC2426]. The first attempt to convert RFC 2426 to RDF was made by Renato Ianella and published in a W3C working group note[VCARDRDF]. This ontology doesn't meet Nepomuk requirements though. Most of the properties don't have their domains and ranges set. It uses certain modelling techniques that result in untyped blank nodes. Those few range constraints that have been set are violated in the examples provided with the specification document.

All of this led to a decision to create a new ontology. This opportunity has been used to fill in the missing domain and range constraints and to expand the ontology with the concepts of Roles and arbitrary contact media. It came at a cost of reduced compatibility with the VCARD specification. The goal was to allow for lossless import of vCard data. Exporting vCard files might require discarding some information, since NCO is more expressive.

Scope

The meaning of the term 'Contact' in NCO is quite wide. It is every piece of data that identifies an entity or provides means to communicate with it. This definition has two aspects - identification and communication. NCO covers both of them.

A very high level diagram of the scope of NCO is outlined in the figure above. It has two axes: content and complexity. The vertical one refers to the various kinds of entities mentioned in the definition of a Contact. They include people and organizations but in a general case anything that can be contacted, can be represented by an instance of the Contact class. This generality is justified by the fact, that in many cases automatic agents can be contacted with various means. Many companies operate automatic IVR systems the users may call to obtain information or place orders. Emails are sent by various software systems to notify the recipient of some event. In all of these cases, a user might want to reprent such entities on a contact list, even though they are neither people, nor organizations.

The horizontal axis represents the broad spectrum of use cases for this ontology. The left end is intended to cover simple bits of information about contacts. Such information is usually found in various places on a desktop. Recipients of emails, authors of documents, attendees of calendar events. All of these small pieces of data refer to Contacts, even though they are not parts of a typical addressbook or a Contact list.

The rightmost end of the horizontal axis represents cases where a Contact refers to an entry in an Addressbook. There are numerous applications that allow the user to manage a list of contacts. They usually store many pieces of data. In many cases a single person appears in various roles, as a private person and as an employee of a company or an organization. These roles are usually connected with their own addresses (private and business), telephone numbers, email addresses etc. Cases when a person is affiliated with multiple organizations make the matters even more complicated. NCO tries to provide means to express this role-based approach.

Description of classes and properties

The most important classes are outlined in the Figure below.

nco:Contact is the core class of NCO. It provides various properties for the purpose of identifying an entity. They include mostly names, either as one string - (nco:fullname or split into constituent parts - nco:nameFamily, nco:nameGiven etc).

The communication information is expressed with subclasses of the nco:ContactMedium class. They provide various means of communication. An entire hierarchy of various ContactMedia has been presented. Available subclasses include: nco:PostalAddress, nco:PhoneNumber, nco:EmailAddress, and nco:IMAccount. Each medium is equipped with specific properties. For instance the PostalAddress can be split into various parts, an IMAccount has an nco:imID, a nco:imStatus and a status message nco:imStatusMessage.

A single nco:Contact has one default role (expressed by the fact that the Contact class is a subclass of nco:Role. This makes it easier to use Contacts in places where little information is available (leftmost end of the complexity axis). When contacts are extracted from places where they are described in more detail (rightmost end of the complexity axis) the distinction between multiple roles can be expressed. NCO provides means to describe contact information to a person (nco:PersonContact) class that is affiliated (nco:Affiliation) with multiple Organizations (nco:OrganizationContact).

Usage

As already mentioned the definition of a Contact is intentionally broad. NCO is intended to cover a wide array of use cases. The most obvious one is description of entries found in addressbooks. There are many applications that work with such data. The list includes, but is certainly not limited to email clients, calendaring applications, standalone addressbook applications and online social services (like Orkut or LinkedIn).

Addressbook entries are not the only way to use NCO. Instances of the Contact class may come up in many other places, as senders and receivers of emails, as meeting attendees, as fileOwners etc. It is considered a best practice to use an instance of the Contact class wherever some contactable entity is referenced, even when the point where this reference is made contains little other information. See the list of properties that have nco:Contact as their domain for ideas.

The NCO is a good example of the trend towards ontology integration. To illustrate the effect of it let's consider a contact disambiguation tool. It would browse all instances of the class Contact and aggregate those that refer to one Person (by email address or various forms of name). Such a tool wouldn't need to be aware of all properties in all ontologies that even though they have a plain String as their range - actually indicate a name of a person. If we left the names and email addresses as plain string values of specialized properties - it would become much more difficult to assign them to appropriate people automatically.

Examples

  • nco-contact.ttl A simple NCO Contact. It represents an individual, with some contact media affiliated with an organization. His work address and telephone is also expressed.

  • nco-key.ttl Demonstrates how to attach information about public keys. NCO doesn't have any particular vocabulary for elements of public keys. A key is treated as an attachment file. Future NIE extensions may add more expressive vocabulary for this.

  • nco-photossounds.ttl Demonstrates how to attach information about photos and sounds to a contact. They are also expressed as attachments, but NIE provides vocabulary that can be used to interpret those attachments as InformationElements of a concrete type.

References

VCARDRDF

Representing vcard objects in rdf/xml, Renato Ianella, W3C Note 22 February 2001 http://www.w3.org/TR/vcard-rdf

RFC2426

vcard mime directory profile, Frank Dawson and Tim Howes http://www.ietf.org/rfc/rfc2426.txt

NCO Vocabulary Summary

Description of Classes

nco:Affiliation

LabelAffiliation
DescriptionAggregates three properties defined in RFC2426. Originally all three were attached directly to a person. One person could have only one title and one role within one organization. This class is intended to lift this limitation.
Super-classesnco:Role (direct)
Sub-classes 
In domain ofnco:org, nco:department, nco:role, nco:title
In range ofnco:hasAffiliation
Mentioned inDescription of classes and properties

nco:AudioIMAccount (deprecated)

LabelAudioIMAccount
DescriptionDeprecated in favour of nco:imCapabilityAudio.
Super-classesnco:IMAccount (direct), nco:ContactMedium
Sub-classesnco:VideoIMAccount (direct)
In domain of 
In range of 

nco:BbsNumber

LabelBbsNumber
DescriptionA Bulletin Board System (BBS) phone number. Inspired by the (TYPE=bbsl) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.
Super-classesnco:ModemNumber (direct), nco:PhoneNumber, nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:CarPhoneNumber

LabelCarPhoneNumber
DescriptionA car phone number. Inspired by the (TYPE=car) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.
Super-classesnco:VoicePhoneNumber (direct), nco:PhoneNumber, nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:CellPhoneNumber

LabelCellPhoneNumber
DescriptionA cellular phone number. Inspired by the (TYPE=cell) parameter of the TEL property as defined in RFC 2426 sec 3.3.1. Usually a cellular phone can accept voice calls as well as textual messages (SMS), therefore this class has two superclasses.
Super-classesnco:PhoneNumber, nco:VoicePhoneNumber (direct), nco:MessagingNumber (direct), nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:ContactGroup

LabelContactGroup
DescriptionA group of Contacts. Could be used to express a group in an addressbook or on a contact list of an IM application. One contact can belong to many groups.
Super-classesnie:InformationElement (direct)
Sub-classes 
In domain ofnco:contactGroupName
In range ofnco:belongsToGroup, nso:sharedWithGroup

nco:ContactList

LabelContactList
DescriptionA contact list, this class represents an addressbook or a contact list of an IM application. Contacts inside a contact list can belong to contact groups.
Super-classesnie:InformationElement (direct)
Sub-classes 
In domain ofnco:containsContact
In range of 

nco:ContactListDataObject

LabelContactListDataObject
DescriptionAn entity occuring on a contact list (usually interpreted as an nco:Contact)
Super-classesnie:DataObject (direct)
Sub-classes 
In domain of 
In range ofnco:containsContact

nco:ContactMedium

LabelContactMedium
DescriptionA superclass for all contact media - ways to contact an entity represented by a Contact instance. Some of the subclasses of this class (the various kinds of telephone numbers and postal addresses) have been inspired by the values of the TYPE parameter of ADR and TEL properties defined in RFC 2426 sec. 3.2.1. and 3.3.1 respectively. Each value is represented by an appropriate subclass with two major exceptions TYPE=home and TYPE=work. They are to be expressed by the roles these contact media are attached to i.e. contact media with TYPE=home parameter are to be attached to the default role (nco:Contact or nco:PersonContact), whereas media with TYPE=work parameter should be attached to nco:Affiliation or nco:OrganizationContact.
Super-classes 
Sub-classesnco:IMAccount (direct), nco:VoicePhoneNumber, nco:InternationalDeliveryAddress, nco:VideoTelephoneNumber, nco:IsdnNumber, nco:PagerNumber, nco:PcsNumber, nco:EmailAddress (direct), nco:VideoIMAccount, nco:CarPhoneNumber, nco:CellPhoneNumber, nco:DomesticDeliveryAddress, nco:PhoneNumber (direct), nco:PostalAddress (direct), nco:ParcelDeliveryAddress, nco:BbsNumber, nco:FaxNumber, nco:ModemNumber, nco:AudioIMAccount, nco:MessagingNumber
In domain ofnco:contactMediumComment
In range ofnmo:secondaryMessageRecipient, nmo:messageSender, nmo:messageReplyTo, nmo:messageFrom, nmo:emailCc, nmo:messageRecipient, nmo:primaryMessageRecipient, nmo:emailTo, nco:hasContactMedium, nmo:emailBcc
Mentioned inDescription of classes and properties

nco:DomesticDeliveryAddress

LabelDomesticDeliveryAddress
DescriptionDomestic Delivery Addresse. Class inspired by TYPE=dom parameter of the ADR property defined in RFC 2426 sec. 3.2.1
Super-classesnco:PostalAddress (direct), nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:EmailAddress

LabelEmailAddress
DescriptionAn email address. The recommended best practice is to use mailto: uris for instances of this class.
Super-classesnco:ContactMedium (direct)
Sub-classes 
In domain ofnco:emailAddress
In range ofnco:hasEmailAddress
Mentioned inDescription of classes and properties

nco:FaxNumber

LabelFaxNumber
DescriptionA fax number. Inspired by the (TYPE=fax) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.
Super-classesnco:PhoneNumber (direct), nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:Gender

LabelGender
DescriptionGender. Instances of this class may include male and female.
Super-classes 
Sub-classes 
In domain of 
In range ofnco:gender
Instancesnco:female, nco:male

nco:IMCapability

LabelimCapability
DescriptionCapabilities of a cetain IMAccount.
Super-classes 
Sub-classes 
In domain of 
In range ofnco:hasIMCapability
Instancesnco:imCapabilityAudio, nco:imCapabilityText, nco:imCapabilityVideo

nco:IMStatusType

Labelinstant messaging status type
DescriptionThe status type of an IMAccount. Based on the Connection_Presence_Type enumeration of the Telepathy project: http://telepathy.freedesktop.org/spec/Connection_Interface_Simple_Presence.html#Enum:Connection_Presence_Type
Super-classes 
Sub-classes 
In domain of 
In range ofnco:imStatusType
Instancesnco:IMStatusTypeAvailable, nco:IMStatusTypeBusy, nco:IMStatusTypeExtendedAway, nco:IMStatusTypeHidden, nco:IMStatusTypeAway, nco:IMStatusTypeUnknown, nco:IMStatusTypeOffline

nco:InternationalDeliveryAddress

LabelInternationalDeliveryAddress
DescriptionInternational Delivery Addresse. Class inspired by TYPE=intl parameter of the ADR property defined in RFC 2426 sec. 3.2.1
Super-classesnco:PostalAddress (direct), nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:IsdnNumber

LabelIsdnNumber
DescriptionAn ISDN phone number. Inspired by the (TYPE=isdn) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.
Super-classesnco:VoicePhoneNumber (direct), nco:PhoneNumber, nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:MessagingNumber

LabelMessagingNumber
DescriptionA number that can accept textual messages.
Super-classesnco:PhoneNumber (direct), nco:ContactMedium
Sub-classesnco:PagerNumber (direct), nco:CellPhoneNumber (direct)
In domain of 
In range of 

nco:ModemNumber

LabelModemNumber
DescriptionA modem phone number. Inspired by the (TYPE=modem) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.
Super-classesnco:PhoneNumber (direct), nco:ContactMedium
Sub-classesnco:BbsNumber (direct)
In domain of 
In range of 

nco:OrganizationContact

LabelOrganizationContact
DescriptionA Contact that denotes on Organization.
Super-classesnao:Party, nco:Contact (direct), nco:Role, nie:InformationElement
Sub-classes 
In domain ofnco:logo
In range ofnco:org
Mentioned inDescription of classes and properties

nco:PagerNumber

LabelPagerNumber
DescriptionA pager phone number. Inspired by the (TYPE=pager) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.
Super-classesnco:MessagingNumber (direct), nco:PhoneNumber, nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:ParcelDeliveryAddress

LabelParcelDeliveryAddress
DescriptionParcel Delivery Addresse. Class inspired by TYPE=parcel parameter of the ADR property defined in RFC 2426 sec. 3.2.1
Super-classesnco:PostalAddress (direct), nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:PcsNumber

LabelPcsNumber
DescriptionPersonal Communication Services Number. A class inspired by the TYPE=pcs parameter of the TEL property defined in RFC 2426 sec. 3.3.1
Super-classesnco:VoicePhoneNumber (direct), nco:PhoneNumber, nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:PersonContact

LabelPersonContact
DescriptionA Contact that denotes a Person. A person can have multiple Affiliations.
Super-classesnao:Party, nco:Contact (direct), nco:Role, nie:InformationElement
Sub-classes 
In domain ofnco:gender, nco:nameHonorificPrefix, nco:nameHonorificSuffix, nco:nameGiven, nco:nameFamily, nco:hobby, nco:nameAdditional, nco:hasAffiliation
In range of 
Mentioned inDescription of classes and properties

nco:PhoneNumber

nco:PostalAddress

LabelPostalAddress
DescriptionA postal address. A class aggregating the various parts of a value for the 'ADR' property as defined in RFC 2426 Sec. 3.2.1.
Super-classesnco:ContactMedium (direct)
Sub-classesnco:ParcelDeliveryAddress (direct), nco:InternationalDeliveryAddress (direct), nco:DomesticDeliveryAddress (direct)
In domain ofnco:streetAddress, nco:postalcode, nco:pobox, nco:extendedAddress, nco:addressLocation, nco:locality, nco:country, nco:region
In range ofnco:hasPostalAddress
Mentioned inDescription of classes and properties

nco:Role

LabelRole
DescriptionA role played by a contact. Contacts that denote people, can have many roles (e.g. see the hasAffiliation property and Affiliation class). Contacts that denote Organizations or other Agents usually have one role. Each role can introduce additional contact media.
Super-classes 
Sub-classesnco:PersonContact, nco:OrganizationContact, nco:Contact (direct), nco:Affiliation (direct)
In domain ofnco:hasPhoneNumber, nco:hasPostalAddress, nco:end, nco:url, nco:blogUrl, nco:websiteUrl, nco:hasEmailAddress, nco:hasIMAccount, nco:foafUrl, nco:start, nco:hasContactMedium
In range of 
Mentioned inDescription of classes and properties

nco:VideoIMAccount (deprecated)

LabelVideoIMAccount
DescriptionDeprecated in favour of nco:imCapabilityVideo.
Super-classesnco:IMAccount, nco:AudioIMAccount (direct), nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:VideoTelephoneNumber

LabelVideoTelephoneNumber
DescriptionA Video telephone number. A class inspired by the TYPE=video parameter of the TEL property defined in RFC 2426 sec. 3.3.1
Super-classesnco:VoicePhoneNumber (direct), nco:PhoneNumber, nco:ContactMedium
Sub-classes 
In domain of 
In range of 

nco:VoicePhoneNumber

LabelVoicePhoneNumber
DescriptionA telephone number with voice communication capabilities. Class inspired by the TYPE=voice parameter of the TEL property defined in RFC 2426 sec. 3.3.1
Super-classesnco:PhoneNumber (direct), nco:ContactMedium
Sub-classesnco:PcsNumber (direct), nco:CarPhoneNumber (direct), nco:VideoTelephoneNumber (direct), nco:IsdnNumber (direct), nco:CellPhoneNumber (direct)
In domain ofnco:voiceMail
In range of 

Description of Properties

nco:addressLocation

LabeladdressLocation
DescriptionThe geographical location of a postal address.
Domainnco:PostalAddress
Rangehttp://www.w3.org/2003/01/geo/wgs84_pos#Point
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:belongsToGroup

LabeladdressLocation
DescriptionLinks a Contact with a ContactGroup it belongs to.
Domainnco:Contact
Rangenco:ContactGroup
Cardinalitynone
Super-properties 
Sub-properties 

nco:birthDate

LabelbirthDate
DescriptionBirth date of the object represented by this Contact. An equivalent of the 'BDAY' property as defined in RFC 2426 Sec. 3.1.5.
Domainnco:Contact
Rangexsd:date
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:blogUrl

LabelblogUrl
DescriptionA Blog url.
Domainnco:Role
Rangerdfs:Resource
Cardinalitynone
Super-propertiesnco:url (direct)
Sub-properties 

nco:contactGroupName

LabelcontactGroupName
DescriptionThe name of the contact group. This property was NOT defined in the VCARD standard. See documentation of the 'ContactGroup' class for details
Domainnco:ContactGroup
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:contactMediumComment (deprecated)

LabelcontactMediumComment
DescriptionA comment about the contact medium. (Deprecated in favor of nie:comment or nao:description - based on the context)
Domainnco:ContactMedium
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:contactUID

LabelcontactUID
DescriptionA value that represents a globally unique identifier corresponding to the individual or resource associated with the Contact. An equivalent of the 'UID' property defined in RFC 2426 Sec. 3.6.7
Domainnco:Contact
Rangexsd:string
Maximum Cardinality1
Super-propertiesnie:identifier (direct), nao:identifier
Sub-properties 

nco:containsContact

LabelcontainsContact
DescriptionA property used to group contacts into contact groups. This property was NOT defined in the VCARD standard. See documentation for the 'ContactList' class for details
Domainnco:ContactList
Rangenco:ContactListDataObject
Cardinalitynone
Super-propertiesnie:hasPart (direct), nie:relatedTo
Sub-properties 

nco:contributor

Labelcontributor
DescriptionAn entity responsible for making contributions to the content of the InformationElement.
Domainnie:InformationElement
Rangenco:Contact
Cardinalitynone
Super-propertiesnao:contributor (direct), nao:annotation
Sub-propertiesnmm:composer (direct), nmm:cinematographer (direct), nexif:artist, nmm:producer (direct), nmm:assistantDirector (direct), nmm:performer (direct), nmm:director (direct), nmm:writer (direct), nmm:lyricist (direct), nmm:actor (direct), nco:creator (direct), nfo:foundry

nco:country

Labelcountry
DescriptionA part of an address specyfing the country. Inspired by the seventh part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1
Domainnco:PostalAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:creator

Labelcreator
DescriptionCreator of an information element, an entity primarily responsible for the creation of the content of the data object.
Domainnie:InformationElement
Rangenco:Contact
Cardinalitynone
Super-propertiesnco:contributor (direct), nao:contributor, nao:annotation, nao:creator (direct)
Sub-propertiesnfo:foundry (direct), nexif:artist (direct)

nco:department

Labeldepartment
DescriptionDepartment. The organizational unit within the organization.
Domainnco:Affiliation
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:emailAddress

LabelemailAddress
Description
Domainnco:EmailAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:end

Labelend
DescriptionEnd datetime for the role, such as: the datetime of leaving a project or organization, datetime of ending employment, datetime of divorce. If absent or set to a date in the future, the role is currently active.
Domainnco:Role
Rangexsd:dateTime
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:extendedAddress

LabelextendedAddress
DescriptionAn extended part of an address. This field might be used to express parts of an address that aren't include in the name of the Contact but also aren't part of the actual location. Usually the streed address and following fields are enough for a postal letter to arrive. Examples may include ('University of California Campus building 45', 'Sears Tower 34th floor' etc.) Inspired by the second part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1
Domainnco:PostalAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:foafUrl

LabelfoafUrl
DescriptionThe URL of the FOAF file.
Domainnco:Role
Rangerdfs:Resource
Cardinalitynone
Super-propertiesnco:url (direct)
Sub-properties 

nco:fullname

Labelfullname
DescriptionTo specify the formatted text corresponding to the name of the object the Contact represents. An equivalent of the FN property as defined in RFC 2426 Sec. 3.1.1.
Domainnco:Contact
Rangexsd:string
Maximum Cardinality1
Super-propertiesnao:prefLabel, nie:title (direct)
Sub-properties 
Mentioned inDescription of classes and properties

nco:gender

Labelgender
DescriptionGender of the given contact.
Domainnco:PersonContact
Rangenco:Gender
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:hasAffiliation

LabelhasAffiliation
DescriptionLinks a PersonContact with an Affiliation.
Domainnco:PersonContact
Rangenco:Affiliation
Cardinalitynone
Super-properties 
Sub-properties 

nco:hasContactMedium

LabelhasContactMedium
DescriptionA superProperty for all properties linking a Contact to an instance of a contact medium.
Domainnco:Role
Rangenco:ContactMedium
Cardinalitynone
Super-properties 
Sub-propertiesnco:hasPhoneNumber (direct), nco:hasPostalAddress (direct), nco:hasIMAccount (direct), nco:hasEmailAddress (direct)

nco:hasEmailAddress

LabelhasEmailAddress
DescriptionAn address for electronic mail communication with the object specified by this contact. An equivalent of the 'EMAIL' property as defined in RFC 2426 Sec. 3.3.1.
Domainnco:Role
Rangenco:EmailAddress
Cardinalitynone
Super-propertiesnco:hasContactMedium (direct)
Sub-properties 

nco:hasIMAccount

LabelhasIMAccount
DescriptionIndicates that an Instant Messaging account owned by an entity represented by this contact.
Domainnco:Role
Rangenco:IMAccount
Cardinalitynone
Super-propertiesnco:hasContactMedium (direct)
Sub-properties 

nco:hasIMCapability

LabelhasIMCapability
DescriptionIndicates that an IMAccount has a certain capability.
Domainnco:IMAccount
Rangenco:IMCapability
Cardinalitynone
Super-properties 
Sub-properties 

nco:hasLocation

LabelhasLocation
DescriptionGeographical location of the contact. Inspired by the 'GEO' property specified in RFC 2426 Sec. 3.4.2
Domainnco:Contact
Rangehttp://www.w3.org/2003/01/geo/wgs84_pos#Point
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:hasPhoneNumber

LabelhasPhoneNumber
DescriptionA number for telephony communication with the object represented by this Contact. An equivalent of the 'TEL' property defined in RFC 2426 Sec. 3.3.1
Domainnco:Role
Rangenco:PhoneNumber
Cardinalitynone
Super-propertiesnco:hasContactMedium (direct)
Sub-properties 

nco:hasPostalAddress

LabelhasPostalAddress
DescriptionThe default Address for a Contact. An equivalent of the 'ADR' property as defined in RFC 2426 Sec. 3.2.1.
Domainnco:Role
Rangenco:PostalAddress
Cardinalitynone
Super-propertiesnco:hasContactMedium (direct)
Sub-properties 

nco:hobby

Labelhobby
DescriptionA hobby associated with a PersonContact. This property can be used to express hobbies and interests.
Domainnco:PersonContact
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:imAccountType

LabelimAccountType
DescriptionType of the IM account. This may be the name of the service that provides the IM functionality. Examples might include Jabber, ICQ, MSN etc
Domainnco:IMAccount
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:imID

LabelimID
DescriptionIdentifier of the IM account. Examples of such identifier might include ICQ UINs, Jabber IDs, Skype names etc.
Domainnco:IMAccount
Rangexsd:string
Cardinalitynone
Super-propertiesnao:identifier (direct)
Sub-properties 
Mentioned inDescription of classes and properties

nco:imNickname

LabelimNickname
DescriptionA nickname attached to a particular IM Account.
Domainnco:IMAccount
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:imStatus

LabelimStatus
DescriptionCurrent status of the given IM account. When this property is set, the nco:imStatusType should also always be set. Applications should attempt to parse this property to determine the presence, only falling back to the nco:imStatusType property in the case that this property's value is unrecognised. Values for this property may include 'available', 'offline', 'busy' etc. The exact choice of them is unspecified, although it is recommended to follow the guidance of the Telepathy project when choosing a string identifier http://telepathy.freedesktop.org/spec/Connection_Interface_Simple_Presence.html#description
Domainnco:IMAccount
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 
Mentioned inDescription of classes and properties

nco:imStatusMessage

LabelimStatusMessage
DescriptionA feature common in most IM systems. A message left by the user for all his/her contacts to see.
Domainnco:IMAccount
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 
Mentioned inDescription of classes and properties

nco:imStatusType

Labelinstant messaging status type
DescriptionCurrent status type of the given IM account. When this property is set, the nco:imStatus property should also always be set. Applications should attempt to parse the nco:imStatus property to determine the presence, only falling back to this property in the case that the nco:imStatus property's value is unrecognised.
Domainnco:IMAccount
Rangenco:IMStatusType
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:isAccessedBy

LabelisKnownBy
DescriptionIndicates the local IMAccount by which this IMAccount is accessed. This does not imply membership of a contact list.
Domainnco:IMAccount
Rangenco:IMAccount
Cardinalitynone
Super-properties 
Sub-properties 

nco:isBlocked

LabelisBlocked
DescriptionIndicates that this IMAccount has been blocked.
Domainnco:IMAccount
Rangexsd:boolean
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:key

Labelkey
DescriptionAn encryption key attached to a contact. Inspired by the KEY property defined in RFC 2426 sec. 3.7.2
Domainnco:Contact
Rangenie:DataObject
Cardinalitynone
Super-propertiesnie:hasPart (direct), nie:relatedTo
Sub-properties 

nco:locality

Labellocality
DescriptionLocality or City. Inspired by the fourth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1
Domainnco:PostalAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:logo

Labellogo
DescriptionLogo of a company. Inspired by the LOGO property defined in RFC 2426 sec. 3.5.3
Domainnco:OrganizationContact
Rangenie:DataObject
Cardinalitynone
Super-propertiesnie:hasPart (direct), nie:relatedTo
Sub-properties 

nco:nameAdditional

LabelnameAdditional
DescriptionAdditional given name of an object represented by this contact. See documentation for 'nameFamily' property for details.
Domainnco:PersonContact
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:nameFamily

LabelnameFamily
DescriptionThe family name of an Object represented by this Contact. These applies to people that have more than one given name. The 'first' one is considered 'the' given name (see nameGiven) property. All additional ones are considered 'additional' names. The name inherited from parents is the 'family name'. e.g. For Dr. John Phil Paul Stevenson Jr. M.D. A.C.P. we have contact with: honorificPrefix: 'Dr.', nameGiven: 'John', nameAdditional: 'Phil', nameAdditional: 'Paul', nameFamily: 'Stevenson', honorificSuffix: 'Jr.', honorificSuffix: 'M.D.', honorificSuffix: 'A.C.P.'. These properties form an equivalent of the compound 'N' property as defined in RFC 2426 Sec. 3.1.2
Domainnco:PersonContact
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 
Mentioned inDescription of classes and properties

nco:nameGiven

LabelnameGiven
DescriptionThe given name for the object represented by this Contact. See documentation for 'nameFamily' property for details.
Domainnco:PersonContact
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 
Mentioned inDescription of classes and properties

nco:nameHonorificPrefix

LabelnameHonorificPrefix
DescriptionA prefix for the name of the object represented by this Contact. See documentation for the 'nameFamily' property for details.
Domainnco:PersonContact
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:nameHonorificSuffix

LabelnameHonorificSuffix
DescriptionA suffix for the name of the Object represented by the given object. See documentation for the 'nameFamily' for details.
Domainnco:PersonContact
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:nickname

Labelnickname
DescriptionA nickname of the Object represented by this Contact. This is an equivalent of the 'NICKNAME' property as defined in RFC 2426 Sec. 3.1.3.
Domainnco:Contact
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:note

Labelnote
DescriptionA note about the object represented by this Contact. An equivalent for the 'NOTE' property defined in RFC 2426 Sec. 3.6.2
Domainnco:Contact
Rangexsd:string
Cardinalitynone
Super-propertiesnao:description, nao:annotation, nie:description (direct)
Sub-properties 

nco:org

Labelorg
DescriptionName of an organization or a unit within an organization the object represented by a Contact is associated with. An equivalent of the 'ORG' property defined in RFC 2426 Sec. 3.5.5
Domainnco:Affiliation
Rangenco:OrganizationContact
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:phoneNumber

LabelphoneNumber
Description
Domainnco:PhoneNumber
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:photo

Labelphoto
DescriptionPhotograph attached to a Contact. The DataObject referred to by this property is usually interpreted as an nfo:Image. Inspired by the PHOTO property defined in RFC 2426 sec. 3.1.4
Domainnco:Contact
Rangenie:DataObject
Cardinalitynone
Super-propertiesnie:hasPart (direct), nie:relatedTo
Sub-properties 

nco:pobox

Labelpobox
DescriptionPost office box. This is the first part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1
Domainnco:PostalAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:postalcode

Labelpostalcode
DescriptionPostal Code. Inspired by the sixth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1
Domainnco:PostalAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:publisher

Labelpublisher
DescriptionAn entity responsible for making the InformationElement available.
Domainnie:InformationElement
Rangenco:Contact
Cardinalitynone
Super-properties 
Sub-properties 

nco:publishesPresenceTo

LabelpublishesPresenceTo
DescriptionIndicates that this IMAccount publishes its presence information to the other IMAccount.
Domainnco:IMAccount
Rangenco:IMAccount
Cardinalitynone
Super-properties 
Sub-properties 

nco:region

Labelregion
DescriptionRegion. Inspired by the fifth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1
Domainnco:PostalAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:representative

Labelrepresentative
DescriptionAn object that represent an object represented by this Contact. Usually this property is used to link a Contact to an organization, to a contact to the representative of this organization the user directly interacts with. An equivalent for the 'AGENT' property defined in RFC 2426 Sec. 3.5.4
Domainnco:Contact
Rangenco:Contact
Cardinalitynone
Super-properties 
Sub-properties 

nco:requestedPresenceSubscriptionTo

LabelrequestedPresenceSubscriptionTo
DescriptionIndicates that this IMAccount has requested a subscription to the presence information of the other IMAccount.
Domainnco:IMAccount
Rangenco:IMAccount
Cardinalitynone
Super-properties 
Sub-properties 

nco:role

Labelrole
DescriptionRole an object represented by this contact represents in the organization. This might include 'Programmer', 'Manager', 'Sales Representative'. Be careful to avoid confusion with the title property. An equivalent of the 'ROLE' property as defined in RFC 2426. Sec. 3.5.2. Note the difference between nco:Role class and nco:role property.
Domainnco:Affiliation
Rangexsd:string
Cardinalitynone
Super-properties 
Sub-properties 

nco:sound

Labelsound
DescriptionSound clip attached to a Contact. The DataObject referred to by this property is usually interpreted as an nfo:Audio. Inspired by the SOUND property defined in RFC 2425 sec. 3.6.6.
Domainnco:Contact
Rangenie:DataObject
Cardinalitynone
Super-propertiesnie:hasPart (direct), nie:relatedTo
Sub-properties 

nco:start

Labelstart
DescriptionStart datetime for the role, such as: the datetime of joining a project or organization, datetime of starting employment, datetime of marriage
Domainnco:Role
Rangexsd:dateTime
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:streetAddress

LabelstreetAddress
DescriptionThe streed address. Inspired by the third part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1
Domainnco:PostalAddress
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:title

Labeltitle
DescriptionThe official title the object represented by this contact in an organization. E.g. 'CEO', 'Director, Research and Development', 'Junior Software Developer/Analyst' etc. An equivalent of the 'TITLE' property defined in RFC 2426 Sec. 3.5.1
Domainnco:Affiliation
Rangexsd:string
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:url

Labelurl
DescriptionA uniform resource locator associated with the given role of a Contact. Inspired by the 'URL' property defined in RFC 2426 Sec. 3.6.8.
Domainnco:Role
Rangerdfs:Resource
Cardinalitynone
Super-properties 
Sub-propertiesnco:blogUrl (direct), nco:foafUrl (direct), nco:websiteUrl (direct)

nco:voiceMail

LabelvoiceMail
DescriptionIndicates if the given number accepts voice mail. (e.g. there is an answering machine). Inspired by TYPE=msg parameter of the TEL property defined in RFC 2426 sec. 3.3.1
Domainnco:VoicePhoneNumber
Rangexsd:boolean
Maximum Cardinality1
Super-properties 
Sub-properties 

nco:websiteUrl

LabelwebsiteUrl
DescriptionA url of a website.
Domainnco:Role
Rangerdfs:Resource
Cardinalitynone
Super-propertiesnco:url (direct)
Sub-properties