nco:Affiliation: Tracker Ontology Reference Manual

## nco:Affiliation nco:Affiliation |

## Description

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.

## Class hierarchy

        rdfs:Resource
        ╰── nco:Role
            ╰── nco:Affiliation

## Full-text-indexed properties

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

- nco:department

- nco:title

- nco:role

## Properties

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

    “nco:role”          xsd:string

Number of possible elements per resource (Cardinality): 1

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

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

    “nco:title”          xsd:string

Number of possible elements per resource (Cardinality): Unlimited

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

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

    “nco:org”          nco:OrganizationContact

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

Number of possible elements per resource (Cardinality): 1

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

    “nco:department”          xsd:string

Department. The organizational unit within the organization.

Number of possible elements per resource (Cardinality): 1

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

## See also

The upstream documentation for the NCO ontology.