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.6. Registration Template for Values 

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

#  8.2.6. Registration Template for Values

f  Share

URL

A value is defined by completing the following template.

##  Value

The value literal.

##  Purpose

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

##  Conformance

The calendar properties and/or parameters that can take this value need to be
specified.

##  Example(s)

One or more examples of instances of the value need to be specified.

The following is a fictitious example of a registration of an iCalendar value:

##  Value

TOP-SECRET

##  Purpose

This value is used to specify the access classification of top-secret calendar
components.

##  Conformance

This value can be used with the [ "CLASS" ](/iCalendar-
RFC-5545/3-8-1-3-classification.html) property.

##  Example(s)

The following is an example of this value used with the [ "CLASS"
](/iCalendar-RFC-5545/3-8-1-3-classification.html) property:

    
    
      CLASS:TOP-SECRET

[ Previous article: 8.2.5. Registration Template for Value Data Types  Prev
](/iCalendar-RFC-5545/8-2-5-registration-template-for-value-data-types.html) [
Next article: 8.3. Initial iCalendar Elements Registries  Next  ](/iCalendar-
RFC-5545/8-3-initial-icalendar-elements-registries.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) .