From 70c48be27e74916dfbcee48343ede1882658832c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= <bjorn@erlang.org>
Date: Tue, 25 Mar 2014 06:58:48 +0100
Subject: Document the asn1_OPENTYPE wrapper

---
 lib/asn1/doc/src/asn1_ug.xml | 17 +++++++++++++++++
 lib/asn1/doc/src/asn1ct.xml  |  9 +++++----
 2 files changed, 22 insertions(+), 4 deletions(-)

(limited to 'lib/asn1/doc')

diff --git a/lib/asn1/doc/src/asn1_ug.xml b/lib/asn1/doc/src/asn1_ug.xml
index ee54fdffd7..cef7945226 100644
--- a/lib/asn1/doc/src/asn1_ug.xml
+++ b/lib/asn1/doc/src/asn1_ug.xml
@@ -1438,6 +1438,23 @@ StartMessage  ::= SEQUENCE {
       <c><![CDATA[&amp;Message]]></c> in the class. The <c>msgId</c> field is always
       encoded as a PrintableString, since the field refers to a fixed type
       in the class.</p>
+    <p>In practice, object sets are usually declared to be extensible so
+    so that more objects can be added to the set later. Extensibility is
+    indicated like this:</p>
+    <pre>
+GENERAL-PROCEDURES GENERAL-PROCEDURE ::= {
+    object1 | object2, ...}    </pre>
+     <p>When decoding a type that uses an extensible set constraint,
+     there is always the possibility that the value in the UNIQUE
+     field is unknown (i.e. the type has been encoded with a later
+     version of the ASN.1 specification). When that happens, the
+     unencoded data will be returned wrapped in a tuple like this:</p>
+
+     <pre>
+{asn1_OPENTYPE,Binary}</pre>
+     <p>where <c>Binary</c> is an Erlang binary that contains the encoded
+     data. (If the option <c>legacy_erlang_types</c> has been given,
+     just the binary will be returned.)</p>
   </section>
 
   <section>
diff --git a/lib/asn1/doc/src/asn1ct.xml b/lib/asn1/doc/src/asn1ct.xml
index 4d5a1a402a..32ff2d52cf 100644
--- a/lib/asn1/doc/src/asn1ct.xml
+++ b/lib/asn1/doc/src/asn1ct.xml
@@ -45,10 +45,11 @@
 	<p>By default in OTP 17, the representation of the BIT STRING
 	and OCTET STRING types as Erlang terms have changed. BIT
 	STRING values are now Erlang bitstrings and OCTET STRING values
-	are binaries.  For details see <seealso
-	marker="asn1_ug#BIT STRING">BIT STRING</seealso> and <seealso
-	marker="asn1_ug#OCTET STRING">OCTET STRING</seealso> in User's
-	Guide.</p>
+	are binaries.  Also, an undecoded open type will now be wrapped in
+	a <c>asn1_OPENTYPE</c> tuple. For details see <seealso
+	marker="asn1_ug#BIT STRING">BIT STRING</seealso>, <seealso
+	marker="asn1_ug#OCTET STRING">OCTET STRING</seealso>, and
+	<seealso marker="asn1_ug#Information%20Object">ASN.1 Information Objects</seealso> in User's Guide.</p>
 	<p>To revert to the old representation of the types, use the
 	<c>legacy_erlang_types</c> option.</p>
       </note>
-- 
cgit v1.2.3