## ncal:Attendee ncal:Attendee |

## Description

An attendee of an event. This class has been introduced to serve as the range for ncal:attendee property. See documentation of ncal:attendee for details.

## Class hierarchy

        http://www.w3.org/2000/01/rdf-schema#Resource
            ncal:AttendeeOrOrganizer
            ╰── ncal:Attendee

## Properties

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

    “ncal:partstat”          ncal:ParticipationStatus

To specify the participation status for the calendar user specified by the property. Inspired by RFC 2445 sec. 4.2.12. Originally this parameter had three sets of allowed values. Which set applied to a particular case - depended on the type of calendar entity this parameter occured in. (event, todo, journal entry). This would be awkward to model in RDF so a single ParticipationStatus class has been introduced. Terms of the values vocabulary are expressed as instances of this class. Users are advised to pay attention which instances they use.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:rsvp”          http://www.w3.org/2001/XMLSchema#boolean

To specify whether there is an expectation of a favor of a reply from the calendar user specified by the property value. Inspired by RFC 2445 sec. 4.2.17

Number of possible elements per resource (Cardinality): 1

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

    “ncal:role”          ncal:AttendeeRole

To specify the participation role for the calendar user specified by the property. Inspired by the RFC 2445 sec. 4.2.16. Originally this property had a limited vocabulary for values. The terms of that vocabulary have been expressed as instances of the AttendeeRole class.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:member”          nco:Contact

To specify the group or list membership of the calendar user specified by the property. Inspired by RFC 2445 sec. 4.2.11. Originally this parameter had a value type of CAL-ADDRESS. This has been expressed as nco:Contact to promote integration between NCAL and NCO

Number of possible elements per resource (Cardinality): 1

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

    “ncal:cutype”          ncal:CalendarUserType

To specify the type of calendar user specified by the property. Inspired by RFC 2445 sec. 4.2.3. This parameter has a limited vocabulary. The terms that may serve as values for this property have been expressed as instances of CalendarUserType class. The user may use instances provided with this ontology or create his own.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:delegatedFrom”          nco:Contact

To specify the calendar users that have delegated their participation to the calendar user specified by the property. Inspired by RFC 2445 sec. 4.2.4. Originally the value type for this property was CAL-ADDRESS. This has been expressed as nco:Contact to promote integration between NCAL and NCO.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:delegatedTo”          nco:Contact

To specify the calendar users to whom the calendar user specified by the property has delegated participation. Inspired by RFC 2445 sec. 4.2.5. Originally the value type for this parameter was CAL-ADDRESS. This has been expressed as nco:Contact to promote integration between NCAL and NCO.

Number of possible elements per resource (Cardinality): 1