From e00482559e11163d770b070fdf549a20082b3644 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ingy=20d=C3=B6t=20Net?= Date: Sun, 8 Aug 2021 09:05:01 -0700 Subject: [PATCH] Clarify section describing anchors See https://github.com/yaml/yaml-spec/issues/48 --- spec/spec.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/spec/spec.md b/spec/spec.md index f243f90b..1e10532b 100644 --- a/spec/spec.md +++ b/spec/spec.md @@ -1140,12 +1140,10 @@ to this anchor. Otherwise, anchor names are a [serialization detail] and are discarded once [composing] is completed. When [composing] a [representation graph] from [serialized] events, an alias -node refers to the most recent [node] in the [serialization] having the +event refers to the most recent event in the [serialization] having the specified anchor. Therefore, anchors need not be unique within a [serialization]. In addition, an anchor need not have an alias node referring to it. -It is therefore possible to provide an anchor for all [nodes] in -[serialization]. ### #. Presentation Stream