nco:IMAccount: Tracker Ontology Reference Manual

## nco:IMAccount nco:IMAccount |

## Description

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

This class emits notifications about changes, and can be tracked through the `GraphUpdated` DBus signal.

## Class hierarchy

        rdfs:Resource
        ╰── nie:InformationElement
            ╰── nco:IMAccount

## Properties

### The `“nco:imEnabled”` property

    “nco:imEnabled”          xsd:boolean

Number of possible elements per resource (Cardinality): 1

### The `“nco:imDisplayName”` property

    “nco:imDisplayName”          xsd:string

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.

Number of possible elements per resource (Cardinality): 1

### The `“nco:imAccountType”` property

    “nco:imAccountType”          xsd:string

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

Number of possible elements per resource (Cardinality): 1

### The `“nco:imAccountAddress”` property

    “nco:imAccountAddress”          nco:IMAddress

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

Number of possible elements per resource (Cardinality): 1

### The `“nco:hasIMContact”` property

    “nco:hasIMContact”          nco:IMAddress

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

Number of possible elements per resource (Cardinality): Unlimited

## See also

The upstream documentation for the NCO ontology.