@@ -41,23 +41,23 @@ message Document {
4141 //
4242 // The map keys represent field names.
4343 //
44- // A simple field name contains only characters `a` to `z`, `A` to `Z`,
45- // `0` to `9`, or `_`, and must not start with `0` to `9`. For example,
46- // `foo_bar_17`.
47- //
4844 // Field names matching the regular expression `__.*__` are reserved. Reserved
49- // field names are forbidden except in certain documented contexts. The map
50- // keys , represented as UTF-8, must not exceed 1,500 bytes and cannot be
45+ // field names are forbidden except in certain documented contexts. The field
46+ // names , represented as UTF-8, must not exceed 1,500 bytes and cannot be
5147 // empty.
5248 //
5349 // Field paths may be used in other contexts to refer to structured fields
54- // defined here. For `map_value`, the field path is represented by the simple
55- // or quoted field names of the containing fields, delimited by `.`. For
56- // example, the structured field
57- // `"foo" : { map_value: { "x&y" : { string_value: "hello" }}}` would be
58- // represented by the field path `foo.x&y`.
50+ // defined here. For `map_value`, the field path is represented by a
51+ // dot-delimited (`.`) string of segments. Each segment is either a simple
52+ // field name (defined below) or a quoted field name. For example, the
53+ // structured field `"foo" : { map_value: { "x&y" : { string_value: "hello"
54+ // }}}` would be represented by the field path `` foo.`x&y` ``.
55+ //
56+ // A simple field name contains only characters `a` to `z`, `A` to `Z`,
57+ // `0` to `9`, or `_`, and must not start with `0` to `9`. For example,
58+ // `foo_bar_17`.
5959 //
60- // Within a field path, a quoted field name starts and ends with `` ` `` and
60+ // A quoted field name starts and ends with `` ` `` and
6161 // may contain any character. Some characters, including `` ` ``, must be
6262 // escaped using a `\`. For example, `` `x&y` `` represents `x&y` and
6363 // `` `bak\`tik` `` represents `` bak`tik ``.
0 commit comments