ncal:UnionParentClass: Tracker Ontology Reference Manual

## ncal:UnionParentClass ncal:UnionParentClass |

## Class hierarchy

        rdfs:Resource
        ╰── ncal:UnionParentClass
            ├── ncal:TimezoneObservance
            ├── ncal:Alarm
            ├── ncal:Event
            ├── ncal:Todo
            ├── ncal:Freebusy
            ├── ncal:Journal
            ╰── ncal:Timezone

## Full-text-indexed properties

ncal:UnionParentClass has the following full-text-indexed properties:

- ncal:comment

- ncal:location

- ncal:summary

- ncal:contact

- ncal:description

## Properties

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

    “ncal:relatedToParent”          xsd:string

The property is used to represent a relationship or reference between one calendar component and another. Inspired by RFC 2445 sec. 4.8.4.5. Originally this property had a RELTYPE parameter. It has been decided that it is more natural to introduce three different properties to express the values of that parameter. This property expresses the RELATED-TO property with no RELTYPE parameter (the default value is PARENT), or with explicit RELTYPE=PARENT parameter.

Number of possible elements per resource (Cardinality): Unlimited

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

- `“ncal:ncalRelation”` from the `ncal:UnionParentClass` class

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

    “ncal:relatedToChild”          xsd:string

The property is used to represent a relationship or reference between one calendar component and another. Inspired by RFC 2445 sec. 4.8.4.5. Originally this property had a RELTYPE parameter. It has been decided to introduce three different properties to express the values of that parameter. This property expresses the RELATED-TO property with RELTYPE=CHILD parameter.

Number of possible elements per resource (Cardinality): Unlimited

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

- `“ncal:ncalRelation”` from the `ncal:UnionParentClass` class

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

    “ncal:categories”          xsd:string

Categories for a calendar component. Inspired by RFC 2445 sec 4.8.1.2 with the following reservations: The LANGUAGE parameter has been discarded. Please use xml:lang literals to express multiple languages. This property can specify multiple comma-separated categories. The order of categories doesn't matter. Please use a separate triple for each category.

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:duration”          xsd:integer

The property specifies a positive duration of time. Inspired by RFC 2445 sec. 4.8.2.5

Number of possible elements per resource (Cardinality): 1

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

    “ncal:relatedToSibling”          xsd:string

The property is used to represent a relationship or reference between one calendar component and another. Inspired by RFC 2445 sec. 4.8.4.5. Originally this property had a RELTYPE parameter. It has been decided that it is more natural to introduce three different properties to express the values of that parameter. This property expresses the RELATED-TO property with RELTYPE=SIBLING parameter.

Number of possible elements per resource (Cardinality): 1

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

- `“ncal:ncalRelation”` from the `ncal:UnionParentClass` class

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

    “ncal:description”          xsd:string

A more complete description of the calendar component, than that provided by the ncal:summary property.Inspired by RFC 2445 sec. 4.8.1.5 with following reservations: the LANGUAGE parameter has been discarded. Please use xml:lang literals to express language. For the ALTREP parameter use the descriptionAltRep property.

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:

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

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

    “ncal:dtstart”          ncal:NcalDateTime

This property specifies when the calendar component begins. Inspired by RFC 2445 sec. 4.8.2.4

Number of possible elements per resource (Cardinality): 1

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

    “ncal:resourcesAltRep”          rdfs:Resource

Alternate representation of the resources needed for an event or todo. Introduced to cover the ALTREP parameter of the resources property. See documentation for ncal:resources for details.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:geo”          rdfs:Resource

This property specifies information related to the global position for the activity specified by a calendar component. Inspired by RFC 2445 sec. 4.8.1.6

Number of possible elements per resource (Cardinality): 1

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

    “ncal:exrule”          ncal:RecurrenceRule

This property defines a rule or repeating pattern for an exception to a recurrence set. Inspired by RFC 2445 sec. 4.8.5.2.

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:hasAlarm”          ncal:CalendarDataObject

Links an event or a todo with a DataObject that can be interpreted as an alarm. This property has no direct equivalent in the RFC 2445. It has been provided to express this relation.

Number of possible elements per resource (Cardinality): Unlimited

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

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

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

    “ncal:locationAltRep”          rdfs:Resource

Alternate representation of the event or todo location. Introduced to cover the ALTREP parameter of the LOCATION property. See documentation of ncal:location for details.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:rdate”          ncal:NcalTimeEntity

This property defines the list of date/times for a recurrence set. Inspired by RFC 2445 sec. 4.8.5.3. Note that RFC allows both DATE, DATE-TIME and PERIOD values for this property. That's why the range has been set to NcalTimeEntity.

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:contactAltRep”          rdfs:Resource

Alternate representation of the contact property. Introduced to cover the ALTREP parameter of the CONTACT property. See documentation of ncal:contact for details.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:contact”          xsd:string

The property is used to represent contact information or alternately a reference to contact information associated with the calendar component. Inspired by RFC 2445 sec. 4.8.4.2 with the following reservations: the LANGUAGE parameter has been discarded. Please use xml:lang literals to express language. For the ALTREP parameter use the contactAltRep property.RFC doesn't define any format for the string.

Number of possible elements per resource (Cardinality): 1

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

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

    “ncal:sequence”          xsd:integer

This property defines the revision sequence number of the calendar component within a sequence of revisions. Inspired by RFC 2445 sec. 4.8.7.4

Number of possible elements per resource (Cardinality): 1

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

    “ncal:commentAltRep”          rdfs:Resource

Alternate representation of the comment. Introduced to cover the ALTREP parameter of the COMMENT property. See documentation of ncal:comment for details.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:descriptionAltRep”          rdfs:Resource

Alternate representation of the calendar entity description. Introduced to cover the ALTREP parameter of the DESCRIPTION property. See documentation of ncal:description for details.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:summary”          xsd:string

Defines a short summary or subject for the calendar component. Inspired by RFC 2445 sec 4.8.1.12 with the following reservations: the LANGUAGE parameter has been discarded. Please use xml:lang literals to express language. For the ALTREP parameter use the summaryAltRep property.

Number of possible elements per resource (Cardinality): 1

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

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

    “ncal:exdate”          ncal:NcalDateTime

This property defines the list of date/time exceptions for a recurring calendar component. Inspired by RFC 2445 sec. 4.8.5.1

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:ncalRelation”          xsd:string

A common superproperty for all types of ncal relations. It is not to be used directly.

Number of possible elements per resource (Cardinality): Unlimited

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

- `“dc:relation”` from the `rdfs:Resource` class

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

    “ncal:dtend”          ncal:NcalDateTime

This property specifies the date and time that a calendar component ends. Inspired by RFC 2445 sec. 4.8.2.2

Number of possible elements per resource (Cardinality): 1

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

    “ncal:rrule”          ncal:RecurrenceRule

This property defines a rule or repeating pattern for recurring events, to-dos, or time zone definitions. sec. 4.8.5.4

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:attendee”          ncal:Attendee

The property defines an 'Attendee' within a calendar component. Inspired by RFC 2445 sec. 4.8.4.1. Originally this property accepted many parameters. The Attendee class has been introduced to express them all. Note that NCAL is aligned with NCO. The actual value (of the CAL-ADDRESS type) is expressed as an instance of nco:Contact. Remember that the CN parameter has been removed from NCAL. Instead that value should be expressed using nco:fullname property of the above mentioned nco:Contact instance. The RFC stated that whenever this property is attached to a Valarm instance', 'the Attendee cannot have any parameters apart from involvedContact.']

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:organizer”          ncal:Organizer

The property defines the organizer for a calendar component. Inspired by RFC 2445 sec. 4.8.4.3. Originally this property accepted many parameters. The Organizer class has been introduced to express them all. Note that NCAL is aligned with NCO. The actual value (of the CAL-ADDRESS type) is expressed as an instance of nco:Contact. Remember that the CN parameter has been removed from NCAL. Instead that value should be expressed using nco:fullname property of the above mentioned nco:Contact instance.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:class”          ncal:AccessClassification

Defines the access classification for a calendar component. Inspired by RFC 2445 sec. 4.8.1.3 with the following reservations: this property has limited vocabulary. Possible values are: PUBLIC, PRIVATE and CONFIDENTIAL. The default is PUBLIC. Those values are expressed as instances of the AccessClassification class. The user may create his/her own if necessary.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:dtstamp”          xsd:dateTime

The property indicates the date/time that the instance of the iCalendar object was created. Inspired by RFC 2445 sec. 4.8.7.1. Note that the RFC allows ONLY UTC values for this property.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:recurrenceId”          ncal:RecurrenceIdentifier

Number of possible elements per resource (Cardinality): 1

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

    “ncal:requestStatus”          ncal:RequestStatus

This property defines the status code returned for a scheduling request. Inspired by RFC 2445 sec. 4.8.8.2. Original value of this property was a four-element structure. The RequestStatus class has been introduced to express it. In RFC 2445 this property could have the LANGUAGE parameter. This has been discarded in this ontology. Use xml:lang literals to express it if necessary.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:uid”          xsd:string

This property defines the persistent, globally unique identifier for the calendar component. Inspired by the RFC 2445 sec 4.8.4.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 `“ncal:location”` property

    “ncal:location”          xsd:string

Defines the intended venue for the activity defined by a calendar component. Inspired by RFC 2445 sec 4.8.1.7 with the following reservations: the LANGUAGE parameter has been discarded. Please use xml:lang literals to express language. For the ALTREP parameter use the locationAltRep property.

Number of possible elements per resource (Cardinality): 1

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

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

    “ncal:resources”          xsd:string

Defines the equipment or resources anticipated for an activity specified by a calendar entity. Inspired by RFC 2445 sec. 4.8.1.10 with the following reservations: the LANGUAGE parameter has been discarded. Please use xml:lang literals to express language. For the ALTREP parameter use the resourcesAltRep property. This property specifies multiple resources. The order is not important. it is recommended to introduce a separate triple for each resource.

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:priority”          xsd:integer

The property defines the relative priority for a calendar component. Inspired by RFC 2445 sec. 4.8.1.9

Number of possible elements per resource (Cardinality): 1

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

    “ncal:summaryAltRep”          rdfs:Resource

Alternate representation of the comment. Introduced to cover the ALTREP parameter of the SUMMARY property. See documentation of ncal:summary for details.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:comment”          xsd:string

Non-processing information intended to provide a comment to the calendar user. Inspired by RFC 2445 sec. 4.8.1.4 with the following reservations: the LANGUAGE parameter has been discarded. Please use xml:lang literals to express language. For the ALTREP parameter use the commentAltRep property.

Number of possible elements per resource (Cardinality): 1

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

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

    “ncal:url”          rdfs:Resource

This property defines a Uniform Resource Locator (URL) associated with the iCalendar object. Inspired by the RFC 2445 sec. 4.8.4.6. Original range had been specified as URI.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:created”          xsd:dateTime

This property specifies the date and time that the calendar information was created by the calendar user agent in the calendar store. Note: This is analogous to the creation date and time for a file in the file system. Inspired by RFC 2445 sec. 4.8.7.1. Note that this property is a subproperty of nie:created. The domain of nie:created is nie:DataObject. It is not a superclass of UnionOf_Vevent_Vjournal_Vtodo, but since that union is conceived as an 'abstract' class, and in real-life all resources referenced by this property will also be DataObjects, than this shouldn't cause too much of a problem. Note that RFC allows ONLY UTC time values for this property.

Number of possible elements per resource (Cardinality): 1

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

- `“nie:created”` from the `nie:DataObject` class

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

    “ncal:trigger”          ncal:Trigger

This property specifies when an alarm will trigger. Inspired by RFC 2445 sec. 4.8.6.3 Originally the value of this property could accept two types : duration and date-time. To express this fact a Trigger class has been introduced. It also has a related property to account for the RELATED parameter.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:lastModified”          xsd:dateTime

The property specifies the date and time that the information associated with the calendar component was last revised in the calendar store. Note: This is analogous to the modification date and time for a file in the file system. Inspired by RFC 2445 sec. 4.8.7.3. Note that the RFC allows ONLY UTC time values for this property.

Number of possible elements per resource (Cardinality): 1

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

    “ncal:attach”          ncal:Attachment

The property provides the capability to associate a document object with a calendar component. Defined in the RFC 2445 sec. 4.8.1.1

Number of possible elements per resource (Cardinality): Unlimited

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

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

## See also

The upstream documentation for the NCAL ontology.