Hi, I have couple of questions regarding ValueSet definition.
1) According to Debusion book, page 335, clause (15). ValueSet should have
*Dubuisson*
atleast one common value with parent type. While in TCAPMessage.asn(X.880) file, I have found following definition:
Component{OPERATION:Invokable, OPERATION:Returnable} ::= CHOICE { basicROS ROS{{TCInvokeIdSet}, {Invokable}, {Returnable}}, returnResultNotLast [7] returnResult < ROS{{TCInvokeIdSet}, {Invokable}, {Returnable}} }
TCInvokeIdSet ::= InvokeId(WITH COMPONENTS { present (-128..127) })
As TCInvokeIdSet is not ValueSetAssignment & is a TypeAssignment, Here TCInvokeIdSet doesn't represent common value with parent type InvokeId.
2) Is ValueSet means It can have only Values as ElementSetSpecs or It can also be Types.
Types are sets of values, so it is correct to use a Type as an ElementSetSpec in a ValueSet.
Is following definition is correct? TypeA ::= INEGER ValueSetA TypeA ::= { TypeA (123 .. 125) }
Here "TypeA(123 ..125) is" Type, not a Value.
3) Can ValueSet have DefinedType in ElementSetSpecs?
Yes
4) If I compare ValueSet with ObjectSet. ObjectSet can have only InformationObjects. So ValueSet should have only Values. Is it correct. Or ValueSet can have Values & Types, While ObjectSet can have only InformationObject, but can't have CLASS.
A type is a set of values and a value set is made of values. You can imagine a value set as a bag in which you put values whether they are single values or values coming from another value set or from a type.
--
Olivier DUBUISSON
france telecom R&D
DTL/TAL - 22307 Lannion Cedex - France t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/
