nco:Contact

## nco:Contact nco:Contact |

## Description

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

## Class hierarchy

        http://www.w3.org/2000/01/rdf-schema#Resource http://www.w3.org/2000/01/rdf-schema#Resource
            nie:InformationElement     ──┐
                                         │
                    nco:Role ────────────┤
                                         └── nco:Contact
                        nco:OrganizationContact
                            nco:PersonContact

## Full-text-indexed properties

nco:Contact has the following full-text-indexed properties:

- nco:fullname

- nco:nickname

- nco:note

## Properties

### The `“scal:anniversary”` property

    “scal:anniversary”          scal:Event

links a contact with the calendar event of an anniversary. (SCAL version)

Number of possible elements per resource (Cardinality): Unlimited

### The `“scal:birthday”` property

    “scal:birthday”          scal:Event

links a contact with the calendar event of his birthday. (SCAL version)

Number of possible elements per resource (Cardinality): Unlimited

### The `“ncal:anniversary”` property

    “ncal:anniversary”          ncal:Event

links a contact with the calendar event of an anniversary. (NCAL version)

Number of possible elements per resource (Cardinality): Unlimited

### The `“ncal:birthday”` property

    “ncal:birthday”          ncal:Event

links a contact with the calendar event of his birthday. (NCAL version)

Number of possible elements per resource (Cardinality): Unlimited

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

    “nco:sound”          nie:InformationElement

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.

Number of possible elements per resource (Cardinality): 1

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

    “nco:belongsToGroup”          nco:ContactGroup

Links a Contact with a ContactGroup it belongs to.

Number of possible elements per resource (Cardinality): Unlimited

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

    “nco:birthDate”          http://www.w3.org/2001/XMLSchema#dateTime

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

Number of possible elements per resource (Cardinality): 1

This property supersedes the following properties from this or parent classes:

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

    “nco:photo”          nie:InformationElement

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

Number of possible elements per resource (Cardinality): 1

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

    “nco:representative”          nco:Contact

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

Number of possible elements per resource (Cardinality): 1

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

    “nco:note”          http://www.w3.org/2001/XMLSchema#string

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

Number of possible elements per resource (Cardinality): Unlimited

This property is full-text-indexed, and can be looked up through `fts:match`.

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

    “nco:nickname”          http://www.w3.org/2001/XMLSchema#string

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.

Number of possible elements per resource (Cardinality): 1

This property is full-text-indexed, and can be looked up through `fts:match`.

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

    “nco:hasLocation”          http://www.w3.org/2000/01/rdf-schema#Resource

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

Number of possible elements per resource (Cardinality): 1

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

    “nco:contactLocalUID”          http://www.w3.org/2001/XMLSchema#string

Unique ID for the contact in the local storage

Number of possible elements per resource (Cardinality): 1

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

    “nco:contactUID”          http://www.w3.org/2001/XMLSchema#string

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

Number of possible elements per resource (Cardinality): 1

This property supersedes the following properties from this or parent classes:

- `“nie:identifier”` from the `nie:InformationElement` class

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

    “nco:key”          nie:DataObject

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

Number of possible elements per resource (Cardinality): 1

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

    “nco:fullname”          http://www.w3.org/2001/XMLSchema#string

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.

Number of possible elements per resource (Cardinality): 1

This property is full-text-indexed, and can be looked up through `fts:match`.

This property supersedes the following properties from this or parent classes: