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.4. Value Data Types Registry 

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

#  8.3.4. Value Data Types Registry

f  Share

URL

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

    
    
       +-----------------+---------+--------------------------+
       | Value Data Type | Status  | Reference                |
       +-----------------+---------+--------------------------+
       | BINARY          | Current | RFC 5545, Section 3.3.1  |
       |                 |         |                          |
       | BOOLEAN         | Current | RFC 5545, Section 3.3.2  |
       |                 |         |                          |
       | CAL-ADDRESS     | Current | RFC 5545, Section 3.3.3  |
       |                 |         |                          |
       | DATE            | Current | RFC 5545, Section 3.3.4  |
       |                 |         |                          |
       | DATE-TIME       | Current | RFC 5545, Section 3.3.5  |
       |                 |         |                          |
       | DURATION        | Current | RFC 5545, Section 3.3.6  |
       |                 |         |                          |
       | FLOAT           | Current | RFC 5545, Section 3.3.7  |
       |                 |         |                          |
       | INTEGER         | Current | RFC 5545, Section 3.3.8  |
       |                 |         |                          |
       | PERIOD          | Current | RFC 5545, Section 3.3.9  |
       |                 |         |                          |
       | RECUR           | Current | RFC 5545, Section 3.3.10 |
       |                 |         |                          |
       | TEXT            | Current | RFC 5545, Section 3.3.11 |
       |                 |         |                          |
       | TIME            | Current | RFC 5545, Section 3.3.12 |
       |                 |         |                          |
       | URI             | Current | RFC 5545, Section 3.3.13 |
       |                 |         |                          |
       | UTC-OFFSET      | Current | RFC 5545, Section 3.3.14 |
       +-----------------+---------+--------------------------+

[ Previous article: 8.3.3. Parameters Registry  Prev  ](/iCalendar-
RFC-5545/8-3-3-parameters-registry.html) [ Next article: 8.3.5. Calendar User
Types Registry  Next  ](/iCalendar-RFC-5545/8-3-5-calendar-user-types-
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 [ RF