-
Notifications
You must be signed in to change notification settings - Fork 0
/
null.dbk
173 lines (152 loc) · 3.8 KB
/
null.dbk
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
<?xml version="1.0"?>
<!DOCTYPE article
PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article>
<articleinfo>
<title>
Null Language-Independent Type for
<trademark>YAML</trademark> Version 1.1
</title>
<subtitle>
Working Draft 2005-01-18
</subtitle>
<authorgroup>
<author>
<firstname>Oren</firstname>
<surname>Ben-Kiki</surname>
<email>oren@ben-kiki.org</email>
</author>
<author>
<firstname>Clark</firstname>
<surname>Evans</surname>
<email>cce+yaml@clarkevans.com</email>
</author>
<author>
<firstname>Brian</firstname>
<surname>Ingerson</surname>
<email>ingy@ttul.org</email>
</author>
</authorgroup>
<copyright>
<year>2001-2005</year>
<holder>Oren Ben-Kiki<fo>, </fo></holder>
<holder>Clark Evans<fo>, </fo></holder>
<holder>Brian Ingerson</holder>
</copyright>
<legalnotice>
This document may be freely copied provided it is not modified.
</legalnotice>
<abstract>
<title>Status</title>
<para>
This specification is a draft reflecting consensus reached by members of
the <ulink
url="http://lists.sourceforge.net/lists/listinfo/yaml-core">yaml-core
mailing list</ulink>. Any questions regarding this draft should be
raised on this list.
</para>
</abstract>
</articleinfo>
<section>
<variablelist>
<varlistentry>
<term>
<para>
URI:
</para>
</term>
<listitem>
<para>
<userinput>tag:yaml.org,2002:null</userinput>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<para>
Shorthand:
</para>
</term>
<listitem>
<para>
<userinput>!!null</userinput>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<para>
Kind:
</para>
</term>
<listitem>
<para>
Scalar.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<para>
Canonical:
</para>
</term>
<listitem>
<para>
<userinput>~</userinput>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Regexp:</term>
<listitem>
<screen>
~ <lineannotation># (canonical)</lineannotation>
|null|Null|NULL <lineannotation># (English)</lineannotation>
| <lineannotation># (Empty)</lineannotation>
</screen>
</listitem>
</varlistentry>
<varlistentry>
<term>Definition:</term>
<listitem>
<para>
Devoid of value.
</para>
<para>
A null value is used to indicate the lack of a value. This is
typically converted into any native null-like value (e.g.,
<userinput>undef</userinput> in Perl, <userinput>None</userinput>
in Python). Note that a null is different from an empty string and
that a mapping entry with some key and a null value is valid and
different from not having that key in the mapping.
</para>
</listitem>
</varlistentry>
</variablelist>
<example>
<title><userinput>!!null</userinput> Examples</title>
<programlisting>
# A document may be null.
---
---
# This mapping has four keys,
# one has a value.
empty:
canonical: ~
english: null
~: null key
---
# This sequence has five
# entries, two have values.
sparse:
- ~
- 2nd entry
-
- 4th entry
- Null
</programlisting>
</example>
</section>
</article>