…valid JID is a string of Unicode code points [ Unicode ], encoded using UTF-8 [ RFC3629 ], and structured as an ordered sequence of localpart, domainpart, and resourcepart, where the first two parts are demarcated by the '@' character used as a separator and the last two parts ar…

… Unicode characters where that makes sense, an SMTP Extension to permit UTF-8 [ RFC3629 ] mail addressing and delivery of those extended headers, and (finally) a requirement for support of the 8BITMIME SMTP extension [ RFC1652 ] so that all of these can be transported through the…

…S-ASCII = UTF8-2 / UTF8-3 / UTF8-4 ; UTF8-2, UTF8-3, and UTF8-4 are defined in [RFC3629] CONTROL = %x00-08 / %x0A-1F / %x7F ; All the controls except HTAB The property value component of a content line has a format that is property specific. Refer to the section describing each p…

…below. 3.1 . Character Set The character set for vCard is UTF-8 as defined in [ RFC3629 ]. There is no way to override this. It is invalid to specify a different character set in the "charset" MIME parameter (see Section 10.1 ). 3.2 . Line Delimiting and Folding Individual lines …

…S-ASCII = UTF8-2 / UTF8-3 / UTF8-4 ; UTF8-2, UTF8-3, and UTF8-4 are defined in [RFC3629] CONTROL = %x00-08 / %x0A-1F / %x7F ; All the controls except HTAB The property value component of a content line has a format that is property specific. Refer to the section describing each p…

…s of binary content. Major type 3: A text string ( Section 2 ) encoded as UTF-8 RFC3629 . The number of bytes in the string is equal to the argument. A string containing an invalid UTF-8 sequence is well-formed but invalid ( Section 1.2 ). This type is provided for systems that n…

…n systems that are not part of a closed ecosystem MUST be encoded using UTF-8 [ RFC3629 ]. 4.1 File Format If the credential is signed using the 7.2 JSON Web Token Proof Format (VC-JWT) the contents of the file MUST be the Compact JWS string formed as a result of signing the ClrC…

…s of binary content. Major type 3: A text string ( Section 2 ) encoded as UTF-8 RFC3629 . The number of bytes in the string is equal to the argument. A string containing an invalid UTF-8 sequence is well-formed but invalid ( Section 1.2 ). This type is provided for systems that n…

…-ASCII = UTF8-2 / UTF8-3 / UTF8-4 ; UTF8-2, UTF8-3, and UTF8-4 are defined in [ RFC3629 CONTROL = %x00-08 / %x0A-1F / %x7F ; All the controls except HTAB The property value component of a content line has a format that is property specific. Refer to the section describing each pr…

…s of binary content. Major type 3: A text string ( Section 2 ) encoded as UTF-8 RFC3629 . The number of bytes in the string is equal to the argument. A string containing an invalid UTF-8 sequence is well-formed but invalid ( Section 1.2 ). This type is provided for systems that n…

…-ASCII = UTF8-2 / UTF8-3 / UTF8-4 ; UTF8-2, UTF8-3, and UTF8-4 are defined in [ RFC3629 CONTROL = %x00-08 / %x0A-1F / %x7F ; All the controls except HTAB The property value component of a content line has a format that is property specific. Refer to the section describing each pr…

…of a WebVTT file body encoded as UTF-8 and labeled with the MIME type text/vtt [RFC3629] WebVTT file body consists of the following components, in the following order: An optional U+FEFF BYTE ORDER MARK (BOM) character. The string " WEBVTT ". Optionally, either a U+0020 SPACE cha…

…er-tag MUST be encoded in US-ASCII. The Header-value MUST be encoded in UTF-8 [ RFC3629 ]. A line that is not a continuation line that has no ':' in it is the first line of the base64-encoded body. (See Section 3.4 .) The space of header-tags is managed as described in Section 5 …

…tring (including comments) is ignored in the prefixed case. o CDDL uses UTF-8 [ RFC3629 ] for its encoding. Processing of CDDL does not involve Unicode normalization processes. Example: ; This is a comment person = { g } g = ( "name": tstr, age: int, ; "age" is a bareword ) 3.2 .…

…he user), the user agent might wish to try using the UTF-8 character encoding [ RFC3629 ] to decode the octet sequence. This decoding might fail, however, because not every sequence of octets is valid UTF-8. Barth Standards Track [Page 26] RFC 6265 HTTP State Management Mechanism…