Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 984985
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T05:05:53+00:00 2026-05-16T05:05:53+00:00

specifically, the CN (common name) parameter, e.g. ORGANIZER;CN=John Doe,Eng:mailto:jd@some.com The RFC is vague on

  • 0

specifically, the CN (common name) parameter, e.g.

ORGANIZER;CN=John Doe,Eng:mailto:jd@some.com

The RFC is vague on this, IMHO. It is very clear about property values of type TEXT, but for this parameter it just says “The parameter value is text“. Anyways, the escaping specified for TEXT type doesn’t seem complete for parameter values (e.g. ‘:’ is not escaped).

thanks a lot!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T05:05:54+00:00Added an answer on May 16, 2026 at 5:05 am

    Davka,

    Yes, parameter values can be escaped by surrounding the value in double-quotes. Parameter values must be escaped if they contain any of the following characters:

    ; - semicolon
    : - colon
    , - comma
    

    It is illegal to have a double quote " character inside parameter values, so they should be deleted (or otherwise removed from the parameter value).

    So, with your above example, the correct escaping is this:

    ORGANIZER;CN="John Doe,Eng":mailto:jd@some.com
    

    Note that once the first (unquoted) colon : is encountered, parsing engines treat the rest as the property value. It is legal to use the colon : character inside property values, so the colon in mailto:jd@some.com doesn’t need to be escaped.

    We can break the line into it’s parts:

    • ORGANIZER – property name
    • ; – parameter delimiter
    • CN – parameter name
    • = – parameter value delimiter
    • "John Doe,Eng" – parameter value
    • : – property value delimiter
    • mailto:jd@some.com – property value

    Here’s a quote from RFC 5545 Section 3.2 that explains when parameter values are surrounded with double-quotes, and tells us double-quotes are illegal in parameter values:

    Property parameter values that contain
    the COLON, SEMICOLON, or COMMA
    character separators MUST be specified
    as quoted-string text values. Property
    parameter values MUST NOT contain the
    DQUOTE character. The DQUOTE
    character is used as a delimiter for
    parameter values that contain
    restricted characters or URI text.
    For example:

    DESCRIPTION;ALTREP=”cid:part1.0001@example.org”:The
    Fall’98 Wild Wizards Conference – –
    Las Vegas\, NV\, USA

    It’s important to note that parameters can technically contain multiple values. A comma is used to separate these multiple values:

    (from Section 3.2.11 of RFC 5545:)

    ATTENDEE;MEMBER="mailto:projectA@example.com","mailto:pr
     ojectB@example.com":mailto:janedoe@example.com
    

    Not all iCalendar engines will accept multiple values on all parameters, but the following parameters SHOULD allow multiple values (according to the RFC):

    • MEMBER
    • DELEGATED-FROM
    • DELEGATED-TO

    Regards,

    -Doug

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'd like to add some simple text into some files. Specifically, I do this
Specifically I am interested for the LAMP Stack and some of the best practices
What is the difference in how they are handled? Specifically, why is it common
I'd like this thread to be some kind of summary of pros/cons for overriding
I'm having trouble using I18n.translate to translate an array. Specifically, I've got this array,
I need to update some user records in my database every month (specifically, give
First, I know this is kind of common question, but I could not find
I'm not sure whether this is an issue with my use of cl-who (specifically
Context: This is specifically a Windows 8 Metro application question based on their HTML/JS
Specifically common.inc. I need to modify format_date, but I want to do it safely.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.