Hi,
Thanks for that clarification,
but I guess I had not put the question very clearly. I understand
that the following is the X.680 specification for XMLSequenceValue -
XMLSequenceValue:
XMLComponentValueList
| // empty
;
XMLComponentValueList:
XMLNamedValue
| XMLComponentValueList XMLNamedValue
;
XMLNamedValue:
"<" & identifier ">" XMLValue "</" & identifier ">"
;
If the above is the grammar for XMLSequenceValue, then under what specification in X.680 is the notation <c/> valid. I understand that the same is valid when the identifier within the Open Tag ("<") and Close Empty Tag ("/>") is a xmlasn1typename. Thanking you.
XMLNamedValue
| XMLComponentValueList XMLNamedValue
;
XMLNamedValue:
"<" & identifier ">" XMLValue "</" & identifier ">"
;
If the above is the grammar for XMLSequenceValue, then under what specification in X.680 is the notation <c/> valid. I understand that the same is valid when the identifier within the Open Tag ("<") and Close Empty Tag ("/>") is a xmlasn1typename. Thanking you.
Yours Sincerely
Ramaswamy R
To deny our instincts, is to deny the very thing that makes us human - Mouse (The Matrix)
-----Original Message-----
From: Paul Thorpe [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 26, 2004 3:48 AM
To: [EMAIL PROTECTED]
Subject: Re: [ASN.1] XML Notation
Hi Ramaswamy,
Yes, ASN.1 (2002) does permit the value notation you have used below.
Note, however, that use of <c/> does not indicate the absense of the
OPTIONAL field, but indicates it is present with zero-length value.
Ramaswamy R
To deny our instincts, is to deny the very thing that makes us human - Mouse (The Matrix)
-----Original Message-----
From: Paul Thorpe [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 26, 2004 3:48 AM
To: [EMAIL PROTECTED]
Subject: Re: [ASN.1] XML Notation
Hi Ramaswamy,
Yes, ASN.1 (2002) does permit the value notation you have used below.
Note, however, that use of <c/> does not indicate the absense of the
OPTIONAL field, but indicates it is present with zero-length value.