Hello ,
Is it allowed to use ANY in the new ASN.1 (97) descriptions?
If not can you please specify subtitution for this structure( esp. ANY)?
E.g.
XXArg ::= SEQUENCE {
errorId Error,
cause ANY OPTIONAL}
Warm regards,
Vasa
-Original Message-
From: Ed Day [mailto:[EMAIL
Prasad Vasa wrote:
Hello ,
Is it allowed to use ANY in the new ASN.1 (97) descriptions?
NO. By the way, 97 is considered a bit old these days! The current
version is the 2002 version. This is expected to be finally approved by
ITU-T in the middle of July (a couple of weeks away), and by
Maybe my last answer was not so good!
It was factually correct, and the minimum change. However, I think the
spirit of your example is that the type filling the ANY is fully
determined by the value of errorId. Yes?
In that case, you would be better to use the built-in class
TYPE-IDENTIFIER,
Hello john,
Thank you very much prompt solution. You are correct I map the errorId and
cause. They I try to operations on those structures. I feel the built in
TYPE-IDENTIFER would not suit for my requirement. I may try the second
solution that you suggetsed to have one table.
Warm regards,
(I am copying this to asn1edit, as it may need to be registered as a
defect.)
Ed, text that covers defined types:
25.10 If the first alternative of XMLDelimitedItem is used, then if
the component of the sequence-of type (after ignoring any tags) is a
typereference or an ExternalTypeReference,
Hi Ed,
I think in your example you are referring "A" as defined type, correct ?
"A" is CHOICE here, so it will encoded like ChoiceType. Look at clause 25.5
(Table 5).
Following are the XER encoding of the value notations.
value A ::= a : 1
XER Encoding (Look at clause 28.10)
A
a1/a/A
If
Hi Rajul,
Thanks for the response. I did look at table
5 and see no mention of DefinedType in the left column. I also did not get
this from the other clauses you mention. But your answer:
value B ::= {a : 1}
XER Encoding (Look at clause 25.3 and 25.5)
B a1/a/B
answers my question. I'll
Hi Ed,
Look at this, is this something you are looking for ? I think 13.8 is the
answer of your question. I may be wrong also.
13.7 Where a "DefinedType" is used as part of notation governed by a "Type"
(for example, in a "SubtypeConstraint") then the "DefinedType" shall be
compatible with
