| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485 | --- %YAML:1.0test: Trailing Document Separatortodo: truebrief: >    You can separate YAML documents    with a string of three dashes.yaml: |    - foo: 1      bar: 2    ---    more: stuffpython: |    [        [ { 'foo': 1, 'bar': 2 } ],        { 'more': 'stuff' }    ]ruby: |    [ { 'foo' => 1, 'bar' => 2 } ]---test: Leading Document Separatortodo: truebrief: >    You can explicitly give an opening    document separator to your YAML stream.yaml: |    ---    - foo: 1      bar: 2    ---    more: stuffpython: |    [        [ {'foo': 1, 'bar': 2}],        {'more': 'stuff'}    ]ruby: |    [ { 'foo' => 1, 'bar' => 2 } ]---test: YAML Headertodo: truebrief: >    The opening separator can contain directives    to the YAML parser, such as the version    number.yaml: |    --- %YAML:1.0    foo: 1    bar: 2php: |    ['foo' => 1, 'bar' => 2]documents: 1---test: Red Herring Document Separatorbrief: >    Separators included in blocks or strings    are treated as blocks or strings, as the    document separator should have no indentation    preceding it.yaml: |    foo: |        ---php: |    ['foo' => "---\n"]---test: Multiple Document Separators in Blockbrief: >    This technique allows you to embed other YAML    documents within literal blocks.yaml: |    foo: |        ---        foo: bar        ---        yo: baz    bar: |        foonessphp: |    [       'foo' => "---\nfoo: bar\n---\nyo: baz\n",       'bar' => "fooness\n"    ]
 |