…"=" byseclist ) / ( "BYMINUTE" "=" byminlist ) / ( "BYHOUR" "=" byhrlist ) / ( "BYDAY" "=" bywdaylist ) / ( "BYMONTHDAY" "=" bymodaylist ) / ( "BYYEARDAY" "=" byyrdaylist ) / ( "BYWEEKNO" "=" bywknolist ) / ( "BYMONTH" "=" bymolist ) / ( "BYSETPOS" "=" bysplist ) / ( "WKST" "=" w…

…"=" byseclist ) / ( "BYMINUTE" "=" byminlist ) / ( "BYHOUR" "=" byhrlist ) / ( "BYDAY" "=" bywdaylist ) / ( "BYMONTHDAY" "=" bymodaylist ) / ( "BYYEARDAY" "=" byyrdaylist ) / ( "BYWEEKNO" "=" bywknolist ) / ( "BYMONTH" "=" bymolist ) / ( "BYSETPOS" "=" bysplist ) / ( "WKST" "=" w…

…"=" byseclist ) / ( "BYMINUTE" "=" byminlist ) / ( "BYHOUR" "=" byhrlist ) / ( "BYDAY" "=" bywdaylist ) / ( "BYMONTHDAY" "=" bymodaylist ) / ( "BYYEARDAY" "=" byyrdaylist ) / ( "BYWEEKNO" "=" bywknolist ) / ( "BYMONTH" "=" bymolist ) / ( "BYSETPOS" "=" bysplist ) / ( "WKST" "=" w…

…"=" byseclist ) / ( "BYMINUTE" "=" byminlist ) / ( "BYHOUR" "=" byhrlist ) / ( "BYDAY" "=" bywdaylist ) / ( "BYMONTHDAY" "=" bymodaylist ) / ( "BYYEARDAY" "=" byyrdaylist ) / ( "BYWEEKNO" "=" bywknolist ) / ( "BYMONTH" "=" bymolist ) / ( "BYSETPOS" "=" bysplist ) / ( "WKST" "=" w…

…"=" byseclist ) / ( "BYMINUTE" "=" byminlist ) / ( "BYHOUR" "=" byhrlist ) / ( "BYDAY" "=" bywdaylist ) / ( "BYMONTHDAY" "=" bymodaylist ) / ( "BYYEARDAY" "=" byyrdaylist ) / ( "BYWEEKNO" "=" bywknolist ) / ( "BYMONTH" "=" bymolist ) / ( "BYSETPOS" "=" bysplist ) / ( "WKST" "=" w…

…nt. A jCal parser MUST be able to understand both data types. * Similarly, the "byday" rule part can have one or more string values. If it contains multiple values, an array of strings MUST be used. As before, a single-valued rule part can be represented using either a single str…

…nt. A jCal parser MUST be able to understand both data types. * Similarly, the "byday" rule part can have one or more string values. If it contains multiple values, an array of strings MUST be used. As before, a single-valued rule part can be represented using either a single str…

…he component property discussed above , nor for properties such as interval and byday used in recurrence rules. Those should be added in due course. The schema also currently lacks information about which properties are functional or inverse-functional, which are needed for certa…

…ion: Appendix A # 3.3.10 Example: <recur> <freq>YEARLY</freq> <count>5</count> <byday>-1SU</byday> <bymonth>10</bymonth> </recur> Daboo, et al. Standards Track [Page 14] RFC 6321 xCal August 2011 3.6.11 . Text ( RFC 5545, Section 3.3.11 ) Description: iCalendar "TEXT" property va…

…ion: Appendix A # 3.3.10 Example: <recur> <freq>YEARLY</freq> <count>5</count> <byday>-1SU</byday> <bymonth>10</bymonth> </recur> 3.6.11. Text (RFC 5545, Section 3.3.11) Description: iCalendar "TEXT" property values are represented by the IC:text XML element. The content of the e…

… "startDate": "2017-01-01", "endDate": "2017-12-31", "repeatFrequency": "P1W", "byDay": "https://schema.org/Wednesday", "startTime": "19:00:00", "endTime": "20:00:00", "scheduleTimezone": "Europe/London" } } </script> Structured representation of the JSON-LD example. { "@context"…

… "startDate": "2017-01-01", "endDate": "2017-12-31", "repeatFrequency": "P1W", "byDay": "https://schema.org/Wednesday", "startTime": "19:00:00", "endTime": "20:00:00", "scheduleTimezone": "Europe/London" </script> Structured representation of the JSON-LD example. "@context": "htt…

…ion: Appendix A # 3.3.10 Example: <recur> <freq>YEARLY</freq> <count>5</count> <byday>-1SU</byday> <bymonth>10</bymonth> </recur> Daboo, et al. Standards Track [Page 14] RFC 6321 xCal August 2011 3.6.11 . Text ( RFC 5545, Section 3.3.11 Description: iCalendar "TEXT" property valu…

…th September 2016 Tested up to 4.6.1 bugfix: In the iCal field don’t change the BYDAY property when a city is used as a timezone (i.e. instead of a UTC offset). Fixes #376 3.1.3 – 23rd July 2016 bugfix: Fixed tranlsation (.mo files) bugfix: Fixed image files enhancement: Updated …

…th September 2016 Tested up to 4.6.1 bugfix: In the iCal field don’t change the BYDAY property when a city is used as a timezone (i.e. instead of a UTC offset). Fixes #376 3.1.3 – 23rd July 2016 bugfix: Fixed tranlsation (.mo files) bugfix: Fixed image files enhancement: Updated …