Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!murtoa.cs.mu.oz.au!munnari.oz.au!otc!metro!ipso!stcns3!stca77!nick
From: nick@stca77.stc.oz (Nick Lochrin)
Newsgroups: comp.protocols.iso.dev-environ
Subject: bug in ISODE-5.0 ?
Message-ID: <523@stca77.stc.oz>
Date: 16 Jun 89 05:33:24 GMT
Reply-To: nick@stca77.stc.oz (Nick Lochrin)
Organization: Alcatel STC Australia, Alexandria
Lines: 61


Does anyone know if this is a bug in ISODE-5.0 ?

When defining a ROSE 'OPERATION', the syntax for the 'ARGUMENT' field
(according to the ROSE macro definitions in X.219) is:

-------
Argument ::= ARGUMENT NamedType | empty

-------
and (from X.208) the relevent ASN.1 is:

-------
NamedType ::= identifier Type | Type | SelectionType

Type ::= BuiltinType | DefinedType | SubType

BuiltinType ::= ... | AnyType | ... -- just look at AnyType

AnyType ::= ANY | ANY DEFINED BY identifier
 
-------
The problem is that when ISODE generates pseudo types, the result of
this operation:
-------
transmitTerminalMessage OPERATION 
	ARGUMENT ANY -- don't have any identifier
	RESULT userResponse ANY -- let's have an identifier
	ERRORS
	{
		userError
	}
	::= 0

-------
is (after being fed through rosy):

-------
Pseudo-transmitTerminalMessage ::=
        ANY

Pseudo-transmitTerminalMessage-1 ::=
        userResponse
            ANY
-------
The second one is not correct, as this is meant to be a Type definition
not a NamedType, and therefore should not include an identifier.
Has anyone seen this before or has any suggestions ?

		many thanks in advance,

			nick.

ps. I'd be interested in being added to the ISODE discussion group, if possible.


-- 
Nick Lochrin                 nick@stca77.stc.oz
Alcatel STC Australia        ...!uunet!stca77.stc.oz!nick
41 Mandible St               nick%stca77.stc.oz@uunet.UU.NET
ALEXANDRIA  NSW  2015        "Are you the police ?.. No mam, we're musicians."