# Nepomuk Contacts Ontology (NCO): All about contacts. Rough equivalent of the VCARD standard.

Authors:
- - Tracker Developers
  - Ludger van Elst, DFKI, <elst@dfki.uni-kl.de>
  - Michael Sintek, DFKI, <michael.sintek@dfki.de>
  - Leo Sauermann, DFKI, <leo.sauermann@dfki.de>
  - Antoni Mylka, DFKI, <antoni.mylka@dfki.de>
Editors:
- - Antoni Mylka, DFKI, <antoni.mylka@dfki.de>
  - Tracker developers (translation into turtle)
Contributors:
- - Christiaan Fluit, Aduna, <christiaan.fluit@aduna-software.com>
  - Evgeny 'phreedom' Egorochkin, KDE Strigi Developer, <stexx@mail.ru>
Upstream:

- Upstream version

ChangeLog:

- Tracker changes

Copyright:

- © 2007 DFKI © 2009 Nokia. The ontologies are made available under the terms of NEPOMUK software license (FIXME verify)

## Overview

### Introduction

This is the ontology modelling contacts and postal addresses. It also extends the original nepomuk adding the Instant Messaging account details, because an 'identity' in an IM account can be consider also a contact.

FIXME This documentation must be completed.

### A contact in this ontology

Document here how a contact with work and personal details is represented in the ontology. So far the QtContacts API is using this model to store the information internally, document here all the assumptions they are doing in the code, so a client using pure Sparql is completely compatible with that information

Do not forget contact groups and affiliations

### Postal Address

Postal address class nco:PostalAddress represents a point in the space defined by the usual street, number, postal code textual data. Most of its parameters come from the RFC 2426 section 3.2.1 with few extensions for more granular APIs (nco:county and nco:district)

### IM Accounts and contacts

Explain here how to represent the accounts of 'me' and the contacts coming from the accounts. Do not forget to explain how do we merge the same user in different accounts under one 'identity'. Also the authorization flow.

### Special remarks

Maybe we need to add here something

### Related information

Links to external docs (QT-contacts, Qt-Landmarks would be nice)

## NCO Ontology Classes

### nco:IMAccount

An account in an Instant Messaging system. This refers to IM accounts of the user 'me'.

`Superclasses` :

  nie:InformationElement,

`Subclasses` :

  --

`In domain of` :

  nco:imEnabled, nco:imDisplayName, nco:imAccountType, nco:imAccountAddress, nco:hasIMContact,

`In range of` :

  --

#### Note:

This class notifies about changes

### nco:PcsNumber

Personal Communication Services Number. A class inspired by the TYPE=pcs parameter of the TEL property defined in RFC 2426 sec. 3.3.1

`Superclasses` :

  nco:VoicePhoneNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:PersonContact

A Contact that denotes a Person. A person can have multiple Affiliations.

`Superclasses` :

  nco:Contact,

`Subclasses` :

  --

`In domain of` :

  nco:hasAffiliation, nco:gender, nco:hobby, nco:nameHonorificPrefix, nco:nameHonorificSuffix, nco:nameAdditional, nco:nameGiven, nco:nameFamily,

`In range of` :

  --

`Predefined instances` :

  nco:default-contact-me,

#### Note:

This class notifies about changes

### nco:VoicePhoneNumber

A 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

`Superclasses` :

  nco:PhoneNumber,

`Subclasses` :

  nco:CellPhoneNumber, nco:PcsNumber, nco:CarPhoneNumber, nco:IsdnNumber, nco:VideoTelephoneNumber,

`In domain of` :

  nco:voiceMail,

`In range of` :

  --

### nco:MessagingNumber

A number that can accept textual messages.

`Superclasses` :

  nco:PhoneNumber,

`Subclasses` :

  nco:CellPhoneNumber, nco:PagerNumber,

`In domain of` :

  --

`In range of` :

  --

### nco:BbsNumber

A 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.

`Superclasses` :

  nco:ModemNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:Gender

Gender. Instances of this class may include male and female.

`Superclasses` :

  rdfs:Resource,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  nco:gender,

`Predefined instances` :

  nco:gender-female, nco:gender-male,

### nco:ContactMedium

A 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.

`Superclasses` :

  rdfs:Resource,

`Subclasses` :

  nco:PostalAddress, nco:PhoneNumber, nco:IMAddress, nco:EmailAddress,

`In domain of` :

  nco:contactMediumComment,

`In range of` :

  nco:hasContactMedium,

### nco:CellPhoneNumber

A 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.

`Superclasses` :

  nco:VoicePhoneNumber, nco:MessagingNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:Role

A 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.

`Superclasses` :

  rdfs:Resource,

`Subclasses` :

  nco:Contact, nco:Affiliation,

`In domain of` :

  nco:video, nco:hasIMAddress, nco:hasPostalAddress, nco:blogUrl, nco:foafUrl, nco:hasEmailAddress, nco:websiteUrl, nco:hasPhoneNumber, nco:url, nco:hasContactMedium,

`In range of` :

  --

### nco:IsdnNumber

An ISDN phone number. Inspired by the (TYPE=isdn) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.

`Superclasses` :

  nco:VoicePhoneNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:ContactList

A 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.

`Superclasses` :

  nie:InformationElement,

`Subclasses` :

  --

`In domain of` :

  nco:containsContact,

`In range of` :

  --

#### Note:

This class notifies about changes

### nco:VideoTelephoneNumber

A Video telephone number. A class inspired by the TYPE=video parameter of the TEL property defined in RFC 2426 sec. 3.3.1

`Superclasses` :

  nco:VoicePhoneNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:DomesticDeliveryAddress

Domestic Delivery Addresse. Class inspired by TYPE=dom parameter of the ADR property defined in RFC 2426 sec. 3.2.1

`Superclasses` :

  nco:PostalAddress,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:FaxNumber

A fax number. Inspired by the (TYPE=fax) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.

`Superclasses` :

  nco:PhoneNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:OrganizationContact

A Contact that denotes on Organization.

`Superclasses` :

  nco:Contact,

`Subclasses` :

  --

`In domain of` :

  nco:logo,

`In range of` :

  nco:org,

### nco:PhoneNumber

A telephone number.

`Superclasses` :

  nco:ContactMedium,

`Subclasses` :

  nco:FaxNumber, nco:VoicePhoneNumber, nco:MessagingNumber, nco:ModemNumber,

`In domain of` :

  nco:phoneNumber,

`In range of` :

  nco:hasPhoneNumber,

### nco:IMAddress

An instant messaging address such as xmpp:foo@bar.com.

`Superclasses` :

  nco:ContactMedium,

`Subclasses` :

  --

`In domain of` :

  nco:imAddressAuthStatusTo, nco:imAddressAuthStatusFrom, nco:imCapability, nco:presenceLastModified, nco:imPresence, nco:imStatusMessage, nco:imProtocol, nco:imAvatar, nco:imNickname, nco:imID,

`In range of` :

  nco:hasIMAddress, nco:imAccountAddress, nco:hasIMContact,

#### Note:

This class notifies about changes

### nco:PresenceStatus

Predefined set of status level instances

`Superclasses` :

  rdfs:Resource,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  nco:imPresence,

`Predefined instances` :

  nco:presence-status-error, nco:presence-status-unknown, nco:presence-status-busy, nco:presence-status-hidden, nco:presence-status-extended-away, nco:presence-status-away, nco:presence-status-available, nco:presence-status-offline, nco:presence-status-unset,

### nco:PostalAddress

A postal address. A class aggregating the various parts of a value for the 'ADR' property as defined in RFC 2426 Sec. 3.2.1.

`Superclasses` :

  nco:ContactMedium,

`Subclasses` :

  nco:DomesticDeliveryAddress, nco:InternationalDeliveryAddress, nco:ParcelDeliveryAddress,

`In domain of` :

  nco:pobox, nco:district, nco:county, nco:locality, nco:postalcode, nco:streetAddress, nco:addressLocation, nco:extendedAddress, nco:country, nco:region,

`In range of` :

  nco:hasPostalAddress,

### nco:EmailAddress

An email address. The recommended best practice is to use mailto: uris for instances of this class.

`Superclasses` :

  nco:ContactMedium,

`Subclasses` :

  --

`In domain of` :

  nco:emailAddress,

`In range of` :

  nco:hasEmailAddress,

### nco:CarPhoneNumber

A car phone number. Inspired by the (TYPE=car) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.

`Superclasses` :

  nco:VoicePhoneNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:AuthorizationStatus

Predefined instances to indicate the auth status: yes, no, requested

`Superclasses` :

  rdfs:Resource,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  nco:imAddressAuthStatusTo, nco:imAddressAuthStatusFrom,

`Predefined instances` :

  nco:predefined-auth-status-requested, nco:predefined-auth-status-no, nco:predefined-auth-status-yes,

### nco:ModemNumber

A modem phone number. Inspired by the (TYPE=modem) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.

`Superclasses` :

  nco:PhoneNumber,

`Subclasses` :

  nco:BbsNumber,

`In domain of` :

  --

`In range of` :

  --

### nco:ContactGroup

A 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.

`Superclasses` :

  nie:InformationElement,

`Subclasses` :

  --

`In domain of` :

  nco:contactGroupName,

`In range of` :

  nco:belongsToGroup,

#### Note:

This class notifies about changes

### nco:ContactListDataObject

An entity occuring on a contact list (usually interpreted as an nco:Contact)

`Superclasses` :

  nie:DataObject,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  nco:containsContact,

### nco:ParcelDeliveryAddress

Parcel Delivery Addresse. Class inspired by TYPE=parcel parameter of the ADR property defined in RFC 2426 sec. 3.2.1

`Superclasses` :

  nco:PostalAddress,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:IMCapability

Features of a certain IM connection (depends on the IMAccount implementation used by the Contact)

`Superclasses` :

  rdfs:Resource,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  nco:imCapability,

`Predefined instances` :

  nco:im-capability-dbus-tubes, nco:im-capability-stream-tubes, nco:im-capability-file-transfers, nco:im-capability-upgrading-calls, nco:im-capability-video-calls, nco:im-capability-audio-calls, nco:im-capability-media-calls, nco:im-capability-text-chat,

### nco:PagerNumber

A pager phone number. Inspired by the (TYPE=pager) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.

`Superclasses` :

  nco:MessagingNumber,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:Affiliation

Aggregates 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.

`Superclasses` :

  nco:Role,

`Subclasses` :

  --

`In domain of` :

  nco:role, nco:title, nco:org, nco:department,

`In range of` :

  nco:hasAffiliation,

### nco:InternationalDeliveryAddress

International Delivery Addresse. Class inspired by TYPE=intl parameter of the ADR property defined in RFC 2426 sec. 3.2.1

`Superclasses` :

  nco:PostalAddress,

`Subclasses` :

  --

`In domain of` :

  --

`In range of` :

  --

### nco:Contact

A Contact. A piece of data that can provide means to identify or communicate with an entity.

`Superclasses` :

  nco:Role, nie:InformationElement,

`Subclasses` :

  nco:PersonContact, nco:OrganizationContact,

`In domain of` :

  nco:sound, nco:belongsToGroup, nco:birthDate, nco:photo, nco:representative, nco:note, nco:nickname, nco:hasLocation, nco:contactLocalUID, nco:contactUID, nco:key, nco:fullname,

`In range of` :

  nco:representative, nco:publisher, nco:creator, nco:contributor,

## NCO Ontology Properties

### nco:imAccountType

Type of the IM account. This may be the name of the service that provides the IM functionality. Examples might include Jabber, ICQ, MSN etc

`Type` :

  --

`Domain` :

  nco:IMAccount,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:imID

Identifier of the IM account. Examples of such identifier might include ICQ UINs, Jabber IDs, Skype names etc.

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  xsd:string,

`Superproperties` :

  nao:identifier,

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:imNickname

A nickname attached to a particular IM address.

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:region

Region. Inspired by the fifth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:country

A part of an address specifying the country. Inspired by the seventh part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:imEnabled

`Type` :

  --

`Domain` :

  nco:IMAccount,

`Range` :

  xsd:boolean,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:publisher

An entity responsible for making the InformationElement available.

`Type` :

  --

`Domain` :

  nie:InformationElement,

`Range` :

  nco:Contact,

`Superproperties` :

  dc:publisher,

`Subproperties` :

  --

`Cardinality` :

  1

### nco:representative

An 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

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  nco:Contact,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:imCapability

Capabilities of an IM Contact, what can we interact with him

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  nco:IMCapability,

`Superproperties` :

  --

`Subproperties` :

  --

### nco:hasIMContact

Indicates that this Instant Messaging account has the specified Instant Messaging address in the contact list.

`Type` :

  --

`Domain` :

  nco:IMAccount,

`Range` :

  nco:IMAddress,

`Superproperties` :

  --

`Subproperties` :

  --

### nco:streetAddress

The streed address. Inspired by the third part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:contactMediumComment

A comment about the contact medium.

`Type` :

  --

`Domain` :

  nco:ContactMedium,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:logo

Logo of a company. Inspired by the LOGO property defined in RFC 2426 sec. 3.5.3

`Type` :

  --

`Domain` :

  nco:OrganizationContact,

`Range` :

  nie:DataObject,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:contactLocalUID

Unique ID for the contact in the local storage

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:nameAdditional

Additional given name of an object represented by this contact. See documentation for 'nameFamily' property for details.

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:contributor

An entity responsible for making contributions to the content of the InformationElement.

`Type` :

  --

`Domain` :

  nie:InformationElement,

`Range` :

  nco:Contact,

`Superproperties` :

  dc:contributor,

`Subproperties` :

  nco:creator,

### nco:role

`Type` :

  --

`Domain` :

  nco:Affiliation,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:hasLocation

Geographical location of the contact. Inspired by the 'GEO' property specified in RFC 2426 Sec. 3.4.2

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  rdfs:Resource,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:contactGroupName

The name of the contact group. This property was NOT defined in the VCARD standard. See documentation of the 'ContactGroup' class for details

`Type` :

  --

`Domain` :

  nco:ContactGroup,

`Range` :

  xsd:string,

`Superproperties` :

  dc:title,

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:sound

Sound clip attached to a Contact. The DataObject refered to by this property is usually interpreted as an nfo:Audio. Inspired by the SOUND property defined in RFC 2425 sec. 3.6.6.

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  nie:InformationElement,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:org

Name 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

`Type` :

  --

`Domain` :

  nco:Affiliation,

`Range` :

  nco:OrganizationContact,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:addressLocation

The geographical location of a postal address.

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  rdfs:Resource,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:hasIMAddress

An address for communication using instant messages with the object specified by this contact.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  nco:IMAddress,

`Superproperties` :

  nco:hasContactMedium,

`Subproperties` :

  --

### nco:imProtocol

Protocol of the account ('skype', 'gtalk', 'icq', ...)

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:video

Video avatar of a contact. Note that is an icon/avatar, not a generic 'present in video' property

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  nie:InformationElement,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:title

`Type` :

  --

`Domain` :

  nco:Affiliation,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:birthDate

Birth date of the object represented by this Contact. An equivalent of the 'BDAY' property as defined in RFC 2426 Sec. 3.1.5.

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  xsd:dateTime,

`Superproperties` :

  dc:date,

`Subproperties` :

  --

`Cardinality` :

  1

### nco:containsContact

A 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

`Type` :

  --

`Domain` :

  nco:ContactList,

`Range` :

  nco:ContactListDataObject,

`Superproperties` :

  nie:hasPart,

`Subproperties` :

  --

### nco:blogUrl

A Blog url.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  rdfs:Resource,

`Superproperties` :

  nco:url,

`Subproperties` :

  --

### nco:creator

Creator of a data object, an entity primarily responsible for the creation of the content of the data object.

`Type` :

  --

`Domain` :

  nie:InformationElement,

`Range` :

  nco:Contact,

`Superproperties` :

  nco:contributor, dc:creator,

`Subproperties` :

  --

### nco:hasContactMedium

A superProperty for all properties linking a Contact to an instance of a contact medium.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  nco:ContactMedium,

`Superproperties` :

  --

`Subproperties` :

  nco:hasIMAddress, nco:hasPostalAddress, nco:hasEmailAddress, nco:hasPhoneNumber,

### nco:contactUID

A 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

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  xsd:string,

`Superproperties` :

  nie:identifier,

`Subproperties` :

  --

`Cardinality` :

  1

### nco:note

A note about the object represented by this Contact. An equivalent for the 'NOTE' property defined in RFC 2426 Sec. 3.6.2

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:foafUrl

The URL of the FOAF file.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  rdfs:Resource,

`Superproperties` :

  nco:url,

`Subproperties` :

  --

### nco:hasEmailAddress

An 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.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  nco:EmailAddress,

`Superproperties` :

  nco:hasContactMedium,

`Subproperties` :

  --

### nco:locality

Locality or City. Inspired by the fourth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:district

Local division inside a city. Not in RFC 2426 sec 3.2.1. Added for API compatibility

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:nameHonorificSuffix

A suffix for the name of the Object represented by the given object. See documentation for the 'nameFamily' for details.

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:websiteUrl

A url of a website.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  rdfs:Resource,

`Superproperties` :

  nco:url,

`Subproperties` :

  --

### nco:nameFamily

The 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

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:imAccountAddress

Instant Messaging address of this IM account. The user 'me' can send and receive messages from this IM address.

`Type` :

  --

`Domain` :

  nco:IMAccount,

`Range` :

  nco:IMAddress,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:nameHonorificPrefix

A prefix for the name of the object represented by this Contact. See documentation for the 'nameFamily' property for details.

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:hasAffiliation

Links a PersonContact with an Affiliation.

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  nco:Affiliation,

`Superproperties` :

  --

`Subproperties` :

  --

### nco:gender

Gender of the given contact.

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  nco:Gender,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:imAddressAuthStatusTo

Do i authorize this im Account to receive my information

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  nco:AuthorizationStatus,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:extendedAddress

An 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

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:imStatusMessage

A feature common in most IM systems. A message left by the user for all his/her contacts to see.

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:key

An encryption key attached to a contact. Inspired by the KEY property defined in RFC 2426 sec. 3.7.2

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  nie:DataObject,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:imAvatar

A picture attached to a particular IM address.

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  nie:DataObject,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:emailAddress

`Type` :

  --

`Domain` :

  nco:EmailAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:url

A uniform resource locator associated with the given role of a Contact. Inspired by the 'URL' property defined in RFC 2426 Sec. 3.6.8.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  rdfs:Resource,

`Superproperties` :

  --

`Subproperties` :

  nco:blogUrl, nco:foafUrl, nco:websiteUrl,

### nco:postalcode

Postal Code. Inspired by the sixth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:hasPhoneNumber

A 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

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  nco:PhoneNumber,

`Superproperties` :

  nco:hasContactMedium,

`Subproperties` :

  --

### nco:photo

Photograph attached to a Contact. The DataObject refered to by this property is usually interpreted as an nfo:Image. Inspired by the PHOTO property defined in RFC 2426 sec. 3.1.4

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  nie:InformationElement,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:nameGiven

The given name for the object represented by this Contact. See documentation for 'nameFamily' property for details.

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:imPresence

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  nco:PresenceStatus,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:nickname

A nickname of the Object represented by this Contact. This is an equivalen of the 'NICKNAME' property as defined in RFC 2426 Sec. 3.1.3.

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:hobby

A hobby associated with a PersonContact. This property can be used to express hobbies and interests.

`Type` :

  --

`Domain` :

  nco:PersonContact,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:department

Department. The organizational unit within the organization.

`Type` :

  --

`Domain` :

  nco:Affiliation,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:phoneNumber

`Type` :

  --

`Domain` :

  nco:PhoneNumber,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:presenceLastModified

Timestamp of the last change in the presence status

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  xsd:dateTime,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:pobox

Post office box. This is the first part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:imDisplayName

The user-visible name of this account. This SHOULD be chosen by the user at account creation time. The account creation user interface is responsible for setting a reasonable default value in the user's locale; something like 'Jabber (bob@example.com)' would be sensible.

`Type` :

  --

`Domain` :

  nco:IMAccount,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:fullname

To 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.

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  xsd:string,

`Superproperties` :

  dc:title,

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:imAddressAuthStatusFrom

Has the other end authorize to receive information about his changes

`Type` :

  --

`Domain` :

  nco:IMAddress,

`Range` :

  nco:AuthorizationStatus,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:hasPostalAddress

The default Address for a Contact. An equivalent of the 'ADR' property as defined in RFC 2426 Sec. 3.2.1.

`Type` :

  --

`Domain` :

  nco:Role,

`Range` :

  nco:PostalAddress,

`Superproperties` :

  nco:hasContactMedium,

`Subproperties` :

  --

### nco:county

Regional division between state and city. Not in RFC 2426 sec 3.2.1. Added for API compatibility

`Type` :

  --

`Domain` :

  nco:PostalAddress,

`Range` :

  xsd:string,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

`Text indexed` :

  This property is indexed, so it can provide results on text search

### nco:voiceMail

Indicates 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

`Type` :

  --

`Domain` :

  nco:VoicePhoneNumber,

`Range` :

  xsd:boolean,

`Superproperties` :

  --

`Subproperties` :

  --

`Cardinality` :

  1

### nco:belongsToGroup

Links a Contact with a ContactGroup it belongs to.

`Type` :

  --

`Domain` :

  nco:Contact,

`Range` :

  nco:ContactGroup,

`Superproperties` :

  --

`Subproperties` :

  --