NEPOMUK Contact Ontology

This document arose from the work of the Task-Force ontologies within the NEPOMUK project. This document is a DRAFT made available by the Nepomuk Consortium for discussion only. This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time.

This document is a part in a set of seven documents, which together comprise the complete specification of the Nepomuk Information Element Ontology Framework. These are: NIE, NFO, NCO, NMO, NCAL, NEXIF, NID3.

Note: Some Contact attributes have been re-organised under three new classes: nco:Name, nco:PersonName and nco:BirthDate. Thus, the modified properties below have undergone a change of domain.
• Added
  • nco:Name
  • nco:PersonName
  • nco:BirthDate
  • nco:birthDate
  • nco:hasName
  • nco:hasPersonName
  • nco:age
• Modified
  • nco:nickname
  • nco:fullname
  • nco:nameAdditional
  • nco:nameFamily
  • nco:nameGiven
  • nco:nameHonorificPrefix
  • nco:nameHonorificSuffix
  • nco:hasBirthDate
• Deprecated

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

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

3. Description of classes and properties

The most important classes are outlined in the Figure below.

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 - (fullname or split into constituent parts - nameFamily, nameGiven etc).

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

A single Contact has one default role (expressed by the fact that the Contact class is a subclass of 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 (PersonContact class that is affiliated (Affiliation) with multiple Organizations (OrganizationContact).

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

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