--- JSON-XS/XS.pm	2007/12/29 17:33:38	1.81
+++ JSON-XS/XS.pm	2007/12/30 21:24:57	1.82
@@ -908,7 +908,7 @@
 =head2 JSON and YAML
 
 You often hear that JSON is a subset of YAML. This is, however, a mass
-hysteria and very far from the truth. In general, there is no way to
+hysteria(*) and very far from the truth. In general, there is no way to
 configure JSON::XS to output a data structure as valid YAML that works for
 all cases.
 
@@ -933,6 +933,32 @@
 that you will run into severe interoperability problems when you least
 expect it.
 
+=over 4
+
+=item (*)
+
+This is spread actively by the YAML team, however. For many years now they
+claim YAML were a superset of JSON, even when proven otherwise.
+
+Even the author of this manpage was at some point accused of providing
+"incorrect" information, despite the evidence presented (claims ranged
+from "your documentation contains inaccurate and negative statements about
+YAML" (the only negative comment is this footnote, and it didn't exist
+back then; the question on which claims were inaccurate was never answered
+etc.) to "the YAML spec is not up-to-date" (the *real* and suppsedly
+JSON-compatible spec is apparently not currently publicly available)
+to actual requests to replace this section by *incorrect* information,
+suppressing information about the real problem).
+
+So whenever you are told that YAML was a superset of JSON, first check
+wether it is really true (it might be when you check it, but it cetrainly
+is not true when this was written). I would much prefer if the YAML team
+would spent their time on actually making JSON compatibility a truth
+(JSON, after all, has a very small and simple specification) instead of
+trying to lobby/force people into reporting untruths.
+
+=back
+
 
 =head2 SPEED