RFC 2445:Internet Calendaring and Scheduling Core ...
RFC-Ref

Entity


Click on the red underlined text to get to the source

... iCalendar objects are transferred across protocols restricted to the 7bit repertoire. Note that a text valued property in the content entity can also have content encoding of special characters using a BACKSLASH character (US-ASCII ...


... URI within a property value. That is the binary content information SHOULD be placed in an external MIME entity that can be referenced by a URI from within the iCalendar ...
... whose special circumstances demand that an iCalendar object be expressed as a single entity. A property containing inline binary content information MUST specify the "ENCODING" property parameter. ...
... For transport in a MIME entity, the Content-Language header field can ...
... chair of the ; calendar entity / "REQ-PARTICIPANT" ; Indicates a participant whose ; participation is required ...
... sound resource cannot be rendered (because its format is unsupported, or because it cannot be retrieved), then the CUA or other entity responsible for playing the sound may choose a fallback action, such as playing a built-in default sound ...
... Description: When used in a MIME message entity, the value of this property MUST be the same as the Content-Type "method ...
... Purpose: This property defines the equipment or resources anticipated for an activity specified by a calendar entity.. Value Type: TEXT ...
... that specifies a group scheduled calendar entity. This property MUST NOT be specified in an iCalendar object when publishing the calendar ...
... a group scheduled calendar entity. The property is specified within an "EMAIL" category of the "VALARM" calendar component ...
... that specifies a group scheduled calendar entity. This property MUST be specified in an iCalendar object that specifies the publication of ...
... group scheduled calendar entity. The property is specified within the "VFREEBUSY" calendar component ...



Google
Web
RFC-Ref