Chronicle Wire supports most of the features available from the YAML 2 specification. TEXT wire type supports a narrow subset which is sufficient to encode and parse Wire record graphs, whereas YAML wire type aims to parse most real-life Yaml documents. This section lists those features and suggests workarounds in Chronicle Wire may define the same thing.
The list below lists the features of the specification that are implemented in Chronicle Wire YAML parser.
Note
|
The numbers refer to the section in the YAML 2 specification. See https://yaml.org/spec/1.2.2/ for more information. |
Feature |
Strict YAML Specification Compliance |
Equivalent Operations in Chronicle Wire |
Section 2_1, |
Yes |
|
Section 2_2, |
Yes |
|
Section 2_3, |
Yes |
|
Section 2_4, |
Yes |
|
Section 2_5, |
Yes |
|
Section 2_6, |
Yes |
|
Section 2_7, |
Yes |
|
Section 2_8, |
Yes |
No special handling of "…" starting the new document without ending previous one |
Section 2_9, |
Yes |
|
Section 2_10, |
Yes |
|
Section 2_11, |
No |
Key-value |
Section 2_12, |
Yes |
|
Section 2_13, |
Yes |
|
Section 2_14, |
Yes |
|
Section 2_15, |
Partial |
Folded/literal blocks are supported, but formatting may deviate from spec |
Section 2_16, |
Partial |
See above |
Section 2_17, |
Yes |
|
Section 2_18, |
No |
Unquoted multi-line strings are not supported |
Section 2_19, |
Yes |
|
Section 2_20, |
Partial |
Limited |
Section 2_21, |
Yes |
|
Section 2_22, |
Partial |
ISO Date-Time format is supported |
Section 2_23, |
Yes |
Supports |
Section 2_24, |
No |
|
Section 2_25, |
No |
|
Section 2_26, |
No |
|
Section 2_27, |
Partial |
|
Section 2_28, |
Partial |