mteb/BrightProStackoverflowRetrieval huggingface dataset:
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 8.3.8. Relationship Types Registry 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  8.3.8. Relationship Types Registry

f  Share

URL

The following table has been used to initialize the relationship types
registry.

    
    
      +-------------------+---------+--------------------------+
      | Relationship Type | Status  | Reference                |
      +-------------------+---------+--------------------------+
      | CHILD             | Current | RFC 5545, Section 3.2.15 |
      |                   |         |                          |
      | PARENT            | Current | RFC 5545, Section 3.2.15 |
      |                   |         |                          |
      | SIBLING           | Current | RFC 5545, Section 3.2.15 |
      +-------------------+---------+--------------------------+

[ Previous article: 8.3.7. Participation Statuses Registry  Prev
](/iCalendar-RFC-5545/8-3-7-participation-statuses-registry.html) [ Next
article: 8.3.9. Participation Roles Registry  Next  ](/iCalendar-
RFC-5545/8-3-9-participation-roles-registry.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 10\. References 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  10\. References

f  Share

URL

[ Previous article: 9. Acknowledgments  Prev  ](/iCalendar-
RFC-5545/9-acknowledgments.html) [ Next article: 10.1. Normative References
Next  ](/iCalendar-RFC-5545/10-1-normative-references.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 8.3. Initial iCalendar Elements Registries 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  8.3. Initial iCalendar Elements Registries

f  Share

URL

The IANA created and maintains the following registries for iCalendar elements
with pointers to appropriate reference documents.

[ Previous article: 8.2.6. Registration Template for Values  Prev
](/iCalendar-RFC-5545/8-2-6-registration-template-for-values.html) [ Next
article: 8.3.1. Components Registry  Next  ](/iCalendar-
RFC-5545/8-3-1-components-registry.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 7\. Security Considerations 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  7\. Security Considerations

f  Share

URL

Because calendaring and scheduling information is very privacy- sensitive, the
protocol used for the transmission of calendaring and scheduling information
should have capabilities to protect the information from possible threats,
such as eavesdropping, replay, message insertion, deletion, modification, and
man-in-the-middle attacks.

As this document only defines the data format and media type of text/ calendar
that is independent of any calendar service or protocol, it is up to the
actual protocol specifications such as iTIP [2446bis], iMIP [2447bis], and
"Calendaring Extensions to WebDAV (CalDAV)" [RFC4791] to describe the threats
that the above attacks present, as well as ways in which to mitigate them.

[ Previous article: 6. Internationalization Considerations  Prev
](/iCalendar-RFC-5545/6-internationalization-considerations.html) [ Next
article: 8. IANA Considerations  Next  ](/iCalendar-RFC-5545/8-iana-
considerations.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .
{calendar_paginate}
<li>
<ul class="pagination">
{calendar_pagination_links}
{first_page}
<li><a href="{pagination_url}">First</a></li>
{/first_page}
{previous_page}
<li><a href="{pagination_url}">&laquo; Previous</a></li>
{/previous_page}
{page}
<li{if current_page} class="active"{/if}><a href="{pagination_url}">{pagination_page_number}</a></li>
{/page}
{next_page}
<li><a href="{pagination_url}">Next &raquo;</a></li>
{/next_page}
{last_page}
<li><a href="{pagination_url}">Last</a></li>
{/last_page}
{/calendar_pagination_links}
</ul>
</li>
{/calendar_paginate}
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 8.3.11. Classifications Registry 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  8.3.11. Classifications Registry

f  Share

URL

The following table has been used to initialize the classifications registry.

    
    
       +----------------+---------+---------------------------+
       | Classification | Status  | Reference                 |
       +----------------+---------+---------------------------+
       | PUBLIC         | Current | RFC 5545, Section 3.8.1.3 |
       |                |         |                           |
       | PRIVATE        | Current | RFC 5545, Section 3.8.1.3 |
       |                |         |                           |
       | CONFIDENTIAL   | Current | RFC 5545, Section 3.8.1.3 |
       +----------------+---------+---------------------------+

[ Previous article: 8.3.10. Actions Registry  Prev  ](/iCalendar-
RFC-5545/8-3-10-actions-registry.html) [ Next article: 8.3.12. Methods
Registry  Next  ](/iCalendar-RFC-5545/8-3-12-methods-registry.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 8\. IANA Considerations 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  8\. IANA Considerations

f  Share

URL

[ Previous article: 7. Security Considerations  Prev  ](/iCalendar-
RFC-5545/7-security-considerations.html) [ Next article: 8.1. iCalendar Media
Type Registration  Next  ](/iCalendar-RFC-5545/8-1-icalendar-media-type-
registration.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .
* [ Code  ](/vuetifyjs/vuetify)
* [ Issues  ](/vuetifyjs/vuetify/issues)
* [ Pull requests  ](/vuetifyjs/vuetify/pulls)
* [ Discussions  ](/vuetifyjs/vuetify/discussions)
* [ Actions  ](/vuetifyjs/vuetify/actions)
* [ Security  ](/vuetifyjs/vuetify/security)
* [ Insights  ](/vuetifyjs/vuetify/pulse)
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 8.2. New iCalendar Elements Registration 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  8.2. New iCalendar Elements Registration

f  Share

URL

This section defines the process to register new or modified iCalendar
elements, that is, components, properties, parameters, value data types, and
values, with IANA.

[ Previous article: 8.1. iCalendar Media Type Registration  Prev
](/iCalendar-RFC-5545/8-1-icalendar-media-type-registration.html) [ Next
article: 8.2.1. iCalendar Elements Registration Procedure  Next  ](/iCalendar-
RFC-5545/8-2-1-icalendar-elements-registration-procedure.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .
*   * [ Notifications ](/login?return_to=%2Fvuetifyjs%2Fvuetify)
* [ Fork  6.9k  ](/login?return_to=%2Fvuetifyjs%2Fvuetify)
* [ Star  39.1k  ](/login?return_to=%2Fvuetifyjs%2Fvuetify)
* [ Code  ](/vuetifyjs/vuetify)
* [ Issues  654  ](/vuetifyjs/vuetify/issues)
* [ Pull requests  130  ](/vuetifyjs/vuetify/pulls)
* [ Discussions  ](/vuetifyjs/vuetify/discussions)
* [ Actions  ](/vuetifyjs/vuetify/actions)
* [ Security  ](/vuetifyjs/vuetify/security)
* [ Insights  ](/vuetifyjs/vuetify/pulse)
<VCalendar :attributes="attributes">
<template #day-popover="{ dayTitle, attributes }">
<div class="px-2">
<div class="text-xs text-gray-700 dark:text-gray-300 font-semibold text-center">
{{ dayTitle }}
</div>
<ul>
<li
v-for="{ key, customData } in attributes"
:key="key"
class="block text-xs text-gray-700 dark:text-gray-300 bg-red-100"
>
{{ customData.description }}
</li>
</ul>
</div>
</template>
</VCalendar>
iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 8.2.4. Registration Template for Parameters 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  8.2.4. Registration Template for Parameters

f  Share

URL

A parameter is defined by completing the following template.

Parameter name: The name of the parameter.

##  Purpose

The purpose of the parameter. Give a short but clear description.

Format definition: The ABNF for the parameter definition needs to be
specified.

##  Description

Any special notes about the parameter, how it is to be used, etc. Example(s):
One or more examples of instances of the parameter need to be specified.

[ Previous article: 8.2.3. Registration Template for Properties  Prev
](/iCalendar-RFC-5545/8-2-3-registration-template-for-properties.html) [ Next
article: 8.2.5. Registration Template for Value Data Types  Next
](/iCalendar-RFC-5545/8-2-5-registration-template-for-value-data-types.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ privacy policy here ](/privacy-policy.html) .