Skip to content
This repository was archived by the owner on Oct 3, 2023. It is now read-only.

Commit 9e0ca2f

Browse files
committed
Describe non-repeated fields as optional in BinaryEncoding.md.
1 parent 4b4ea5d commit 9e0ca2f

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

encodings/BinaryEncoding.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ Each field that we send on the wire will have the following format:
3131

3232
* `field_format` must be defined for each field separately.
3333

34-
The specification for a data type's format must also specify whether each field is single or
35-
repeated. For example, `Trace-id` in `Trace Context` in single, and `String tag` in `Tag Context`
36-
is repeated. Every single field is optional. The specification for a data type's format MAY define
37-
a default value for any single field, which must be used when the field is missing.
34+
The specification for a data type's format must also specify whether each field is optional or
35+
repeated. For example, `Trace-id` in `Trace Context` is optional, and `String tag` in `Tag Context`
36+
is repeated. The specification for a data type's format MAY define a default value for any
37+
optional field, which must be used when the field is missing.
3838

3939
The specification for a data type can define versions within a version of the format, called data
4040
type version, where each data type version adds new fields. The data type version can be useful

0 commit comments

Comments
 (0)