## NCAL Ontology Properties

### ncal:interval

The INTERVAL rule part contains a positive integer representing how often the recurrence rule repeats. The default value is '1', meaning every second for a SECONDLY rule, or every minute for a MINUTELY rule, every hour for an HOURLY rule, every day for a DAILY rule, every week for a WEEKLY rule, every month for a MONTHLY rule andevery year for a YEARLY rule. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:tzoffsetto

This property specifies the offset which is in use in this time zone observance. nspired by RFC 2445 sec. 4.8.3.4. The original domain was underspecified. It said that this property must appear within a Timezone component. In this ontology a TimezoneObservance class has been introduced to clarify this specification. The original range was UTC-OFFSET. There is no equivalent among the XSD datatypes so plain string was chosen.

`Type` : | --
`Domain` : | ncal:TimezoneObservance,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:related

To specify the relationship of the alarm trigger with respect to the start or end of the calendar component. Inspired by RFC 2445 4.2.14. The RFC has specified two possible values for this property ('START' and 'END') they have been expressed as instances of the TriggerRelation class.

`Type` : | --
`Domain` : | ncal:Trigger,
`Range` : | ncal:TriggerRelation,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:recurrenceId

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:RecurrenceIdentifier,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:freq

Frequency of a recurrence rule. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | ncal:RecurrenceFrequency,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:bymonthday

Day of the month when the event should recur. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:byweekno

The number of the week an event should recur. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:percentComplete

This property is used by an assignee or delegatee of a to-do to convey the percent completion of a to-do to the Organizer. Inspired by RFC 2445 sec. 4.8.1.8

`Type` : | --
`Domain` : | ncal:Todo,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:repeat

This property defines the number of time the alarm should be repeated, after the initial trigger. Inspired by RFC 2445 sec. 4.8.6.2

`Type` : | --
`Domain` : | ncal:Alarm,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:contactAltRep

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:until

The UNTIL rule part defines a date-time value which bounds the recurrence rule in an inclusive manner. If the value specified by UNTIL is synchronized with the specified recurrence, this date or date-time becomes the last instance of the recurrence. If specified as a date-time value, then it MUST be specified in an UTC time format. If not present, and the COUNT rule part is also not present, the RRULE is considered to repeat forever.

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:relatedToParent

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | ncal:ncalRelation,
`Subproperties` : | --

### ncal:count

How many times should an event be repeated. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:fbtype

To specify the free or busy time type. Inspired by RFC 2445 sec. 4.2.9. The RFC specified a limited vocabulary for the values of this property. The terms of this vocabulary have been expressed as instances of the FreebusyType class. The user can use instances provided with this ontology or create his own.

`Type` : | --
`Domain` : | ncal:FreebusyPeriod,
`Range` : | ncal:FreebusyType,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:tzid

This property specifies the text value that uniquely identifies the 'VTIMEZONE' calendar component. Inspired by RFC 2445 sec 4.8.3.1

`Type` : | --
`Domain` : | ncal:Timezone,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:dateTime

Representation of a date an instance of NcalDateTime actually refers to. It's purpose is to express values in DATE-TIME datatype, as defined in RFC 2445 sec. 4.3.5

`Type` : | --
`Domain` : | ncal:NcalDateTime,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:location

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1
`Text indexed` : | This property is indexed, so it can provide results on text search

### ncal:rrule

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:RecurrenceRule,
`Superproperties` : | --
`Subproperties` : | --

### ncal:component

Links the Vcalendar instance with the calendar components. This property has no direct equivalent in the RFC specification. It has been introduced to express the containmnent relations.

`Type` : | --
`Domain` : | ncal:Calendar,
`Range` : | ncal:CalendarDataObject,
`Superproperties` : | nie:hasPart,
`Subproperties` : | --

### ncal:attach

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:Attachment,
`Superproperties` : | nie:hasPart,
`Subproperties` : | --

### ncal:bydayWeekday

Connects a BydayRulePath with a weekday.

`Type` : | --
`Domain` : | ncal:BydayRulePart,
`Range` : | ncal:Weekday,
`Superproperties` : | --
`Subproperties` : | --

### ncal:attachmentUri

The uri of the attachment. Created to express the actual value of the ATTACH property defined in RFC 2445 sec. 4.8.1.1. This property expresses the default URI datatype of that property. see ncal:attachmentContents for the BINARY datatype.

`Type` : | --
`Domain` : | ncal:Attachment,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:range

To specify the effective range of recurrence instances from the instance specified by the recurrence identifier specified by the property. It is intended to express the RANGE parameter specified in RFC 2445 sec. 4.2.13. The set of possible values for this property is limited. See also the documentation for ncal:recurrenceId for more details.

`Type` : | --
`Domain` : | ncal:RecurrenceIdentifier,
`Range` : | ncal:RecurrenceIdentifierRange,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### 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.']

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:Attendee,
`Superproperties` : | --
`Subproperties` : | --

### ncal:triggerDateTime

The exact date and time of the trigger. This property has been created to express the VALUE=DATE, and VALUE=DATE-TIME parameters of the TRIGGER property. See the documentation for ncal:trigger for more details

`Type` : | --
`Domain` : | ncal:Trigger,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:bysetpos

The BYSETPOS rule part specify values which correspond to the nth occurrence within the set of events specified by the rule. Valid values are 1 to 366 or -366 to -1. It MUST only be used in conjunction with another BYxxx rule part. For example 'the last work day of the month' could be represented as: RRULE: FREQ=MONTHLY; BYDAY=MO', 'TU', 'WE', 'TH', 'FR; BYSETPOS=-1. Each BYSETPOS value can include a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of the specific occurrence within the set of events specified by the rule. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:created

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:dateTime,
`Superproperties` : | nie:created,
`Subproperties` : | --
`Cardinality` : | 1

### ncal:dtend

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:NcalDateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:dir

Specifies a reference to a directory entry associated with the calendar user specified by the property. Inspired by RFC 2445 sec. 4.2.6. Originally the data type of the value of this parameter was URI (Usually an LDAP URI). This has been expressed as rdfs:resource.

`Type` : | --
`Domain` : | ncal:AttendeeOrOrganizer,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:contact

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1
`Text indexed` : | This property is indexed, so it can provide results on text search

### ncal:version

This property specifies the identifier corresponding to the highest version number or the minimum and maximum range of the iCalendar specification that is required in order to interpret the iCalendar object. Defined in RFC 2445 sec. 4.7.4

`Type` : | --
`Domain` : | ncal:Calendar,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:transp

Defines whether an event is transparent or not to busy time searches. Inspired by RFC 2445 sec.4.8.2.7. Values for this property can be chosen from a limited vocabulary. To express this a TimeTransparency class has been introduced.

`Type` : | --
`Domain` : | ncal:Event,
`Range` : | ncal:TimeTransparency,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:locationAltRep

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:journalStatus

Defines the overall status or confirmation for a journal entry. Based on the STATUS property defined in RFC 2445 sec. 4.8.1.11.

`Type` : | --
`Domain` : | ncal:Journal,
`Range` : | ncal:JournalStatus,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:returnStatus

Short return status. Inspired by the first element of the structured value of the REQUEST-STATUS property described in RFC 2445 sec. 4.8.8.2.

`Type` : | --
`Domain` : | ncal:RequestStatus,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:involvedContact

A contact of the Attendee or the organizer involved in an event or other calendar entity. This property has been introduced to express the actual value of the ATTENDEE and ORGANIZER properties. The contact will also represent the CN parameter of those properties. See documentation of ncal:attendee or ncal:organizer for more details.

`Type` : | --
`Domain` : | ncal:AttendeeOrOrganizer,
`Range` : | nco:Contact,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:rsvp

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

`Type` : | --
`Domain` : | ncal:Attendee,
`Range` : | xsd:boolean,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:byhour

Hour of recurrence. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:comment

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1
`Text indexed` : | This property is indexed, so it can provide results on text search

### ncal:lastModified

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:eventStatus

Defines the overall status or confirmation for an Event. Based on the STATUS property defined in RFC 2445 sec. 4.8.1.11.

`Type` : | --
`Domain` : | ncal:Event,
`Range` : | ncal:EventStatus,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:method

This property defines the iCalendar object method associated with the calendar object. Defined in RFC 2445 sec. 4.7.2

`Type` : | --
`Domain` : | ncal:Calendar,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:summaryAltRep

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:periodEnd

End of a period of time. Inspired by the second part of a structured value of a PERIOD datatype specified in RFC 2445 sec. 4.3.9. Note that a single NcalPeriod instance shouldn't have the periodEnd and periodDuration properties specified simultaneously.

`Type` : | --
`Domain` : | ncal:NcalPeriod,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:summary

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1
`Text indexed` : | This property is indexed, so it can provide results on text search

### ncal:attachmentContent

The uri of the attachment. Created to express the actual value of the ATTACH property defined in RFC 2445 sec. 4.8.1.1. This property expresses the BINARY datatype of that property. see ncal:attachmentUri for the URI datatype.

`Type` : | --
`Domain` : | ncal:Attachment,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:recurrenceIdDateTime

The date and time of a recurrence identifier. Provided to express the actual value of the ncal:recurrenceId property. See documentation for ncal:recurrenceId for details.

`Type` : | --
`Domain` : | ncal:RecurrenceIdentifier,
`Range` : | ncal:NcalDateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:tzname

Specifies the customary designation for a timezone description. Inspired by RFC 2445 sec. 4.8.3.2 The LANGUAGE parameter has been discarded. Please xml:lang literals to express languages. Original specification for the domain of this property stated that it must appear within the timezone component. In this ontology the TimezoneObservance class has been itroduced to clarify this specification.

`Type` : | --
`Domain` : | ncal:TimezoneObservance,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:date

Date an instance of NcalDateTime refers to. It was conceived to express values in DATE datatype specified in RFC 2445 4.3.4

`Type` : | --
`Domain` : | ncal:NcalDateTime,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### 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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:Organizer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:calscale

This property defines the calendar scale used for the calendar information specified in the iCalendar object. Defined in RFC 2445 sec. 4.7.1

`Type` : | --
`Domain` : | ncal:Calendar,
`Range` : | ncal:CalendarScale,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:exrule

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:RecurrenceRule,
`Superproperties` : | --
`Subproperties` : | --

### ncal:role

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.

`Type` : | --
`Domain` : | ncal:Attendee,
`Range` : | ncal:AttendeeRole,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:resourcesAltRep

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:categories

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --

### ncal:bysecond

Second of a recurrence. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:standard

Links the timezone with the standard timezone observance. This property has no direct equivalent in the RFC 2445. It has been inspired by the structure of the Vtimezone component defined in sec.4.6.5

`Type` : | --
`Domain` : | ncal:Timezone,
`Range` : | ncal:TimezoneObservance,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:cutype

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.

`Type` : | --
`Domain` : | ncal:Attendee,
`Range` : | ncal:CalendarUserType,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### 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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:Trigger,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:descriptionAltRep

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:delegatedTo

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.

`Type` : | --
`Domain` : | ncal:Attendee,
`Range` : | nco:Contact,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:todoStatus

Defines the overall status or confirmation for a todo. Based on the STATUS property defined in RFC 2445 sec. 4.8.1.11.

`Type` : | --
`Domain` : | ncal:Todo,
`Range` : | ncal:TodoStatus,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:commentAltRep

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:encoding

To specify an alternate inline encoding for the property value. Inspired by RFC 2445 sec. 4.2.7. Originally this property had a limited vocabulary. ('8BIT' and 'BASE64'). The terms of this vocabulary have been expressed as instances of the AttachmentEncoding class

`Type` : | --
`Domain` : | ncal:Attachment,
`Range` : | ncal:AttachmentEncoding,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:prodid

This property specifies the identifier for the product that created the iCalendar object. Defined in RFC 2445 sec. 4.7.2

`Type` : | --
`Domain` : | ncal:Calendar,
`Range` : | xsd:string,
`Superproperties` : | nie:generator,
`Subproperties` : | --
`Cardinality` : | 1

### ncal:ncalTimezone

The timezone instance that should be used to interpret an NcalDateTime. The purpose of this property is similar to the TZID parameter specified in RFC 2445 sec. 4.2.19

`Type` : | --
`Domain` : | ncal:NcalDateTime,
`Range` : | ncal:Timezone,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:relatedToChild

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | ncal:ncalRelation,
`Subproperties` : | --

### ncal:bydayModifier

A n integer modifier for the BYDAY rule part. Each BYDAY value can also be preceded by a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of the specific day within the MONTHLY or YEARLY RRULE. For example, within a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday within the month, whereas -1MO represents the last Monday of the month. If an integer modifier is not present, it means all days of this type within the specified frequency. For example, within a MONTHLY rule, MO represents all Mondays within the month. Inspired by RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:BydayRulePart,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:member

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

`Type` : | --
`Domain` : | ncal:Attendee,
`Range` : | nco:Contact,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:dtstamp

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:daylight

Links a timezone with it's daylight observance. This property has no direct equivalent in the RFC 2445. It has been inspired by the structure of the Vtimezone component defined in sec.4.6.5

`Type` : | --
`Domain` : | ncal:Timezone,
`Range` : | ncal:TimezoneObservance,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:byyearday

Day of the year the event should occur. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:uid

This property defines the persistent, globally unique identifier for the calendar component. Inspired by the RFC 2445 sec 4.8.4.7

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | nie:identifier,
`Subproperties` : | --
`Cardinality` : | 1

### ncal:sequence

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:relatedToSibling

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | ncal:ncalRelation,
`Subproperties` : | --
`Cardinality` : | 1

### ncal:freebusy

The property defines one or more free or busy time intervals. Inspired by RFC 2445 sec. 4.8.2.6. Note that the periods specified by this property can only be expressed with UTC times. Originally this property could have many comma-separated values. Please use a separate triple for each value.

`Type` : | --
`Domain` : | ncal:Freebusy,
`Range` : | ncal:FreebusyPeriod,
`Superproperties` : | --
`Subproperties` : | --

### ncal:description

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | nie:description,
`Subproperties` : | --
`Cardinality` : | 1
`Text indexed` : | This property is indexed, so it can provide results on text search

### ncal:completed

This property defines the date and time that a to-do was actually completed. Inspired by RFC 2445 sec. 4.8.2.1. Note that the RFC allows ONLY UTC time values for this property.

`Type` : | --
`Domain` : | ncal:Todo,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:rdate

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:NcalTimeEntity,
`Superproperties` : | --
`Subproperties` : | --

### ncal:resources

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --

### ncal:byminute

Minute of recurrence. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:ncalRelation

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:string,
`Superproperties` : | dc:relation,
`Subproperties` : | ncal:relatedToParent, ncal:relatedToChild, ncal:relatedToSibling,

### ncal:periodDuration

Duration of a period of time. Inspired by the second part of a structured value of the PERIOD datatype specified in RFC 2445 sec. 4.3.9. Note that a single NcalPeriod instance shouldn't have the periodEnd and periodDuration properties specified simultaneously.

`Type` : | --
`Domain` : | ncal:NcalPeriod,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:action

This property defines the action to be invoked when an alarm is triggered. Inspired by RFC 2445 sec 4.8.6.1. Originally this property had a limited set of values. They are expressed as instances of the AlarmAction class.

`Type` : | --
`Domain` : | ncal:Alarm,
`Range` : | ncal:AlarmAction,
`Superproperties` : | --
`Subproperties` : | --

### ncal:delegatedFrom

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.

`Type` : | --
`Domain` : | ncal:Attendee,
`Range` : | nco:Contact,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:hasAlarm

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:CalendarDataObject,
`Superproperties` : | nie:hasPart,
`Subproperties` : | --

### ncal:priority

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:fmttype

To specify the content type of a referenced object. Inspired by RFC 2445 sec. 4.2.8. The value of this property should be an IANA-registered content type (e.g. application/binary)

`Type` : | --
`Domain` : | ncal:Attachment,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:duration

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:requestStatusData

Additional data associated with a request status. Inspired by the third part of the structured value for the REQUEST-STATUS property defined in RFC 2445 sec. 4.8.8.2 ('Textual exception data. For example, the offending property name and value or complete property line')

`Type` : | --
`Domain` : | ncal:RequestStatus,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:statusDescription

Longer return status description. Inspired by the second part of the structured value of the REQUEST-STATUS property defined in RFC 2445 sec. 4.8.8.2

`Type` : | --
`Domain` : | ncal:RequestStatus,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:partstat

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.

`Type` : | --
`Domain` : | ncal:Attendee,
`Range` : | ncal:ParticipationStatus,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:periodBegin

Beginng of a period. Inspired by the first part of a structured value of the PERIOD datatype specified in RFC 2445 sec. 4.3.9

`Type` : | --
`Domain` : | ncal:NcalPeriod,
`Range` : | xsd:dateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### 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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:RequestStatus,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:tzoffsetfrom

This property specifies the offset which is in use prior to this time zone observance. Inspired by RFC 2445 sec. 4.8.3.3. The original domain was underspecified. It said that this property must appear within a Timezone component. In this ontology a TimezoneObservance class has been introduced to clarify this specification. The original range was UTC-OFFSET. There is no equivalent among the XSD datatypes so plain string was chosen.

`Type` : | --
`Domain` : | ncal:TimezoneObservance,
`Range` : | xsd:string,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:bymonth

Number of the month of the recurrence. Valid values are integers from 1 (January) to 12 (December). Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --

### ncal:triggerDuration

The duration of a trigger. This property has been created to express the VALUE=DURATION parameter of the TRIGGER property. See documentation for ncal:trigger for more details.

`Type` : | --
`Domain` : | ncal:Trigger,
`Range` : | xsd:integer,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:class

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:AccessClassification,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:byday

Weekdays the recurrence should occur. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | ncal:BydayRulePart,
`Superproperties` : | --
`Subproperties` : | --

### ncal:tzurl

The TZURL provides a means for a VTIMEZONE component to point to a network location that can be used to retrieve an up-to- date version of itself. Inspired by RFC 2445 sec. 4.8.3.5. Originally the range of this property had been specified as URI.

`Type` : | --
`Domain` : | ncal:Timezone,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:wkst

The day that's counted as the start of the week. It is used to disambiguate the byweekno rule. Defined in RFC 2445 sec. 4.3.10

`Type` : | --
`Domain` : | ncal:RecurrenceRule,
`Range` : | ncal:Weekday,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:url

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.

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:dtstart

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:NcalDateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:exdate

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | ncal:NcalDateTime,
`Superproperties` : | --
`Subproperties` : | --

### ncal:sentBy

To specify the calendar user that is acting on behalf of the calendar user specified by the property. Inspired by RFC 2445 sec. 4.2.18. The original data type of this property was a mailto: URI. This has been changed to nco:Contact to promote integration between NCO and NCAL.

`Type` : | --
`Domain` : | ncal:AttendeeOrOrganizer,
`Range` : | nco:Contact,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:geo

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

`Type` : | --
`Domain` : | ncal:UnionParentClass,
`Range` : | rdfs:Resource,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1

### ncal:due

This property defines the date and time that a to-do is expected to be completed. Inspired by RFC 2445 sec. 4.8.2.3

`Type` : | --
`Domain` : | ncal:Todo,
`Range` : | ncal:NcalDateTime,
`Superproperties` : | --
`Subproperties` : | --
`Cardinality` : | 1