From: Oren BenKiki <orenbk@ri...>  20011119 08:18:10

Clark C . Evans [mailto:cce@...] wrote: > A node is the base construct of the YAML information > model. For the definition below, both a value and a > type family are an ordered set of unicode characters. Nope (see below). > A node has: >  a type family >  a value Yes. A type family is a mathematical definition of the set of values the node can have. > A node pair consists of >  a node called "key" >  a node called "value" Yes. > A collection is a node that additionally has: >  an unordered (possibly empty) set of > node pairs such that the value of > the key for each pair is unique > within the set. This is a type family. Consider: The collection type family: value is an unordered... The sequence type family: value is a collection with restricted keys: (0..n) integers... The map type family: value is a collection with arbitrary keys... The integer type family: value is (0, 1, 1, ...) The real type family: value is ... The text type family: value is a sequence of Unicode characters. The binary type family: value is a sequence of octets (bytes). This has nothing to do with transfer methods or node styles. We have a map type family, a map node style, and a map transfer encoding (we may also have a map class in some languages). The base name is the same but the concepts are different  we can clarify this by ensuring we use the full name in every place (the map transfer method deserializes a map node style into a map class which much satisfy the requirements from the map type family. It can also deserialize a scalar node style with the empty value, etc.). Have fun, Oren BenKiki 