Limitations section

[pyderasn.git] / doc / features.rst

diff --git a/doc/features.rst b/doc/features.rst
index 9913ea328b263600cac81c97f3a471b4fce39596..19cf7f97fa6ebd300c55b1f30ddc22ef28be3e7e 100644 (file)
--- a/doc/features.rst
+++ b/doc/features.rst
@@ -9,6 +9,7 @@ Features
 * Working with sequences as high level data objects with ability to
   (un)marshall them
 * Python 2.7/3.5/3.6 compatibility
+* Aimed to be complaint with `X.690-201508 <https://www.itu.int/rec/T-REC-X.690-201508-I/en>`__
 
 Why yet another library? `pyasn1 <http://snmplabs.com/pyasn1/>`__
 had all of this a long time ago. PyDERASN resembles it in many ways. In
@@ -27,7 +28,7 @@ practice it should be relatively easy to convert ``pyasn1``'s code to
 * However they do not require tags matching: IMPLICIT/EXPLICIT tags will
   be set automatically in the given sequence
 * Descriptive errors, like ``pyderasn.DecodeError: UTCTime
-  (tbsCertificate.validity.notAfter.utcTime) (at 328) invalid UTCTime format``
+  (tbsCertificate:validity:notAfter:utcTime) (at 328) invalid UTCTime format``
 * ``__slots__`` friendliness
 * Could be significantly faster. For example parsing of CACert.org's CRL
   under Python 3.5.2:
@@ -42,6 +43,4 @@ practice it should be relatively easy to convert ``pyasn1``'s code to
 There are drawbacks:
 
 * No old Python versions support
-* Strings are not validated in any way, except just trying to be decoded
-  in ``ascii``, ``iso-8859-1``, ``utf-8/16/32`` correspondingly
-* No REAL, RELATIVE OID, EXTERNAL, INSTANCE OF, EMBEDDED PDV, CHARACTER STRING
+* See :ref:`limitations <limitations>`