Issue 5509: 69.8.2.7 The range Element, pages 69-537/538 (components-ftf)
Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com)
Nature: Uncategorized Issue
Severity: 
Summary: Range Element - why is the min and max order not specified?
<!ELEMENT range (value, value) >


I understand the software logic can do a compare to determine the min and
max values, but it seems the following definition would be easier to
understand from human reader.


Change Range to


<!ELEMENT range EMPTY>
<!ATTLIST range
min       CDATA     #REQUIRED
max       CDATA     #REQUIRED>

Resolution: 
Revised Text: 
Actions taken:
July 24, 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


3.   69.8.2.7 The range Element, pages 69-537/538
Range Element - why is the min and max order not specified?
<!ELEMENT range (value, value) >


I understand the software logic can do a compare to determine the min
and
max values, but it seems the following definition would be easier to
understand from human reader.


Change Range to


<!ELEMENT range EMPTY>
<!ATTLIST range
min       CDATA     #REQUIRED
max       CDATA     #REQUIRED>