## ncal:RecurrenceRule ncal:RecurrenceRule |

## Class hierarchy

        rdfs:Resource
        ╰── ncal:RecurrenceRule

## Properties

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

    “ncal:freq”          ncal:RecurrenceFrequency

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

Number of possible elements per resource (Cardinality): 1

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

    “ncal:bymonth”          xsd:integer

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

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:count”          xsd:integer

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

Number of possible elements per resource (Cardinality): 1

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

    “ncal:byyearday”          xsd:integer

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

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:byminute”          xsd:integer

Minute of recurrence. Defined in RFC 2445 sec. 4.3.10

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:byhour”          xsd:integer

Hour of recurrence. Defined in RFC 2445 sec. 4.3.10

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:bysetpos”          xsd:integer

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

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:bymonthday”          xsd:integer

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

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:byweekno”          xsd:integer

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

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:byday”          ncal:BydayRulePart

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

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:interval”          xsd:integer

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

Number of possible elements per resource (Cardinality): 1

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

    “ncal:wkst”          ncal:Weekday

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

Number of possible elements per resource (Cardinality): 1

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

    “ncal:bysecond”          xsd:integer

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

Number of possible elements per resource (Cardinality): Unlimited

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

    “ncal:until”          xsd:dateTime

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.

Number of possible elements per resource (Cardinality): 1

## See also

The upstream documentation for the NCAL ontology.