Issue 5511:  69.8.2.9 The sequence Element (components-ftf)
Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com)
Nature: Uncategorized Issue
Severity: 
Summary: Simple Sequence -The current definitions for sequence allow invalid
definitions to be
built but be syntactically correct. A better definition for a simple
sequence would be as
follows:


Current sequence element


<!ELEMENT sequence
( description?
, ( simple*
| struct*
| sequence*
| valuetype*
)
) >
<!ATTLIST sequence
name CDATA #IMPLIED
type CDATA #REQUIRED >


Change to


Add a new simplesequence element:


<!ELEMENT simplesequence
     ( description?,
     , values?
     , choices?
     , range?
     , enumerations?
     , units?
)>
<!ATTLIST simplesequence
name CDATA     #IMPLIED
type  ( boolean | char   | double | float | short  | long   | objref |
octet | string | ulong
| ushort )     #REQUIRED


      <!ELEMENT values
     ( value+
     )>


Change sequence to:


<!ELEMENT sequence
( description?
, ( simplesequence
| struct*
| sequence*
| valuetype*
)
) >
<!ATTLIST sequence
name CDATA #IMPLIED
type CDATA #REQUIRED >


One does not have to keep repeating the same simple definition. This
definition
then has the added advantage where simple name attribute can now be made
mandatory.
<!ELEMENT simple
( description?
, value
, choices?
, defaultvalue?
) >
 <!ATTLIST simple
name CDATA #REQUIRED
type ( boolean
| char
| double
| float
| short
| long
| objref
| octet
| string
| ulong
| ushort
) #REQUIRED >

Resolution: 
Revised Text: 
Actions taken:
July 15, 2002: received issue
Discussion: 
Resolution:
None as this is deferred to the final report of the Components 1.1 RTF.
Revised Text:
None as this is deferred to the final report of the Components 1.1 RTF

End of Annotations:=====
From: Gerald_L_Bickle@raytheon.com 
Subject: CCM Properties DTD Extensions & Changes 
To: issues@omg.org, components-rtf@omg.org 
Cc: "Mike McClimens" <mikemc@mitre.org>, "Smith, Jeff"
<jesmith@mc.com>, 
   Edwin.Wrench@ITT.COM, mike.mcclimens@saalt.army.mil, 
   "Mike McClimens" <mikemc@mitre.org>, 
   David Fitkin <dwfitkin@rockwellcollins.com>,
   jeffrey.olynick@baesystems.com 
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001 
Date: Mon, 15 Jul 2002 13:57:19 -0500 
X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 5.0.8
|June 18, 2001) at 07/15/2002 
 01:57:19 PM 


Document ptc/2001-11-03, CORBA Component Model


Simple Sequence -The current definitions for sequence allow invalid
definitions to be
built but be syntactically correct. A better definition for a simple
sequence would be as
follows:


Current sequence element


<!ELEMENT sequence
( description?
, ( simple*
| struct*
| sequence*
| valuetype*
)
) >
<!ATTLIST sequence
name CDATA #IMPLIED
type CDATA #REQUIRED >


Change to


Add a new simplesequence element:


<!ELEMENT simplesequence
     ( description?,
     , values?
     , choices?
     , range?
     , enumerations?
     , units?
)>
<!ATTLIST simplesequence
name CDATA     #IMPLIED
type  ( boolean | char   | double | float | short  | long   | objref |
octet | string | ulong
| ushort )     #REQUIRED


      <!ELEMENT values
     ( value+
     )>


Change sequence to:


<!ELEMENT sequence
( description?
, ( simplesequence
| struct*
| sequence*
| valuetype*
)
) >
<!ATTLIST sequence
name CDATA #IMPLIED
type CDATA #REQUIRED >


One does not have to keep repeating the same simple definition. This
definition
then has the added advantage where simple name attribute can now be
made
mandatory.
<!ELEMENT simple
( description?
, value
, choices?
, defaultvalue?
) >
 <!ATTLIST simple
name CDATA #REQUIRED
type ( boolean
| char
| double
| float
| short
| long
| objref
| octet
| string
| ulong
| ushort
) #REQUIRED >