@itemize
@item
-It @strong{must} be schema-less format. Schema-aware ones have
-their definite valuable advantages, but also a complication drawbacks
-and non-friendliness to humans.
-
+ It @strong{must} be schema-less format. Schema-aware ones have
+ their definite valuable advantages, but also a complication drawbacks
+ and non-friendliness to humans.
@item
-Its encoder/decoder @strong{must} be very compact and small in terms of
-code and branches amount, to reduce attack surface on the codec itself.
-
+ Its encoder/decoder @strong{must} be very compact and small in terms of
+ code and branches amount, to reduce attack surface on the codec itself.
@item
-It @strong{must} support enough data types for being able at
-least to replace JSON transparently.
-
+ It @strong{must} support enough data types for being able at
+ least to replace JSON transparently.
@item
-Its encoding @strong{must} be deterministic -- there must be only a
-single representation of the structured data, allowing its usage in
-cryptography-related contexts.
-
+ Its encoding @strong{must} be deterministic -- there must be only a
+ single representation of the structured data, allowing its usage in
+ cryptography-related contexts.
@item
-Its encoder @strong{should} be streaming-friendly, making encoder
-simpler and allowing memory-constrained systems workability.
-
+ Its encoder @strong{should} be streaming-friendly, making encoder
+ simpler and allowing memory-constrained systems workability.
@item
-Its encoding @strong{should} be reasonably compact, to be friendly to
-storage space constrained systems.
-
+ Its encoding @strong{should} be reasonably compact, to be friendly to
+ storage space constrained systems.
@item
-It @strong{should} be frugal to CPU usage for both performance/memory
-constrained and high data volume applications.
+ It @strong{should} be frugal to CPU usage for both performance/memory
+ constrained and high data volume applications.
@end itemize
@include comparison.texi