| rfc8941v9.txt | rfc8941.txt | |||
|---|---|---|---|---|
| skipping to change at line 338 ¶ | skipping to change at line 338 ¶ | |||
| Each member is separated by a comma and optional whitespace. For | Each member is separated by a comma and optional whitespace. For | |||
| example, a field whose value is defined as a List of Strings could | example, a field whose value is defined as a List of Strings could | |||
| look like: | look like: | |||
| Example-List: "foo", "bar", "It was the best of times." | Example-List: "foo", "bar", "It was the best of times." | |||
| An empty List is denoted by not serializing the field at all. This | An empty List is denoted by not serializing the field at all. This | |||
| implies that fields defined as Lists have a default empty value. | implies that fields defined as Lists have a default empty value. | |||
| Note that Lists can have their members split across multiple lines | Note that Lists can have their members split across multiple lines of | |||
| inside a header or trailer section, as per Section 3.2.2 of | the same header or trailer section, as per Section 3.2.2 of | |||
| [RFC7230]; for example, the following are equivalent: | [RFC7230]; for example, the following are equivalent: | |||
| Example-List: foo, bar | Example-List: foo, bar | |||
| and | and | |||
| Example-List: foo | Example-List: foo | |||
| Example-List: bar | Example-List: bar | |||
| However, individual members of a List cannot be safely split between | However, individual members of a List cannot be safely split between | |||
| skipping to change at line 392 ¶ | skipping to change at line 392 ¶ | |||
| individual Inner List members as they require. | individual Inner List members as they require. | |||
| 3.1.2. Parameters | 3.1.2. Parameters | |||
| Parameters are an ordered map of key-value pairs that are associated | Parameters are an ordered map of key-value pairs that are associated | |||
| with an Item (Section 3.3) or Inner List (Section 3.1.1). The keys | with an Item (Section 3.3) or Inner List (Section 3.1.1). The keys | |||
| are unique within the scope of the Parameters they occur within, and | are unique within the scope of the Parameters they occur within, and | |||
| the values are bare items (i.e., they themselves cannot be | the values are bare items (i.e., they themselves cannot be | |||
| parameterized; see Section 3.3). | parameterized; see Section 3.3). | |||
| Implementations MUST provide access to Parameters both by index and | ||||
| by key. Specifications MAY use either means of accessing the | ||||
| members. | ||||
| The ABNF for Parameters is: | The ABNF for Parameters is: | |||
| parameters = *( ";" *SP parameter ) | parameters = *( ";" *SP parameter ) | |||
| parameter = param-key [ "=" param-value ] | parameter = param-key [ "=" param-value ] | |||
| param-key = key | param-key = key | |||
| key = ( lcalpha / "*" ) | key = ( lcalpha / "*" ) | |||
| *( lcalpha / DIGIT / "_" / "-" / "." / "*" ) | *( lcalpha / DIGIT / "_" / "-" / "." / "*" ) | |||
| lcalpha = %x61-7A ; a-z | lcalpha = %x61-7A ; a-z | |||
| param-value = bare-item | param-value = bare-item | |||
| skipping to change at line 483 ¶ | skipping to change at line 487 ¶ | |||
| a default empty value. | a default empty value. | |||
| Typically, a field specification will define the semantics of | Typically, a field specification will define the semantics of | |||
| Dictionaries by specifying the allowed type(s) for individual members | Dictionaries by specifying the allowed type(s) for individual members | |||
| by their keys, as well as whether their presence is required or | by their keys, as well as whether their presence is required or | |||
| optional. Recipients MUST ignore members whose keys that are | optional. Recipients MUST ignore members whose keys that are | |||
| undefined or unknown, unless the field's specification specifically | undefined or unknown, unless the field's specification specifically | |||
| disallows them. | disallows them. | |||
| Note that Dictionaries can have their members split across multiple | Note that Dictionaries can have their members split across multiple | |||
| lines inside a header or trailer section; for example, the following | lines of the same header or trailer section; for example, the | |||
| are equivalent: | following are equivalent: | |||
| Example-Dict: foo=1, bar=2 | Example-Dict: foo=1, bar=2 | |||
| and | and | |||
| Example-Dict: foo=1 | Example-Dict: foo=1 | |||
| Example-Dict: bar=2 | Example-Dict: bar=2 | |||
| However, individual members of a Dictionary cannot be safely split | However, individual members of a Dictionary cannot be safely split | |||
| between lines; see Section 4.2 for details. | between lines; see Section 4.2 for details. | |||
| End of changes. 3 change blocks. | ||||
| 4 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||