CVS difference for ais/ai-00285.txt

Differences between 1.24 and version 1.25
Log of other versions for file ais/ai-00285.txt

--- ais/ai-00285.txt	2005/01/28 02:10:43	1.24
+++ ais/ai-00285.txt	2005/02/08 07:12:29	1.25
@@ -18,6 +18,7 @@
 !standard 0.3(34)
 !standard 1.1.4(14)
 !standard 1.2(8/1)
+!standard 2.2(02)
 !standard 2.2(03)
 !standard 2.2(04)
 !standard 2.2(05)
@@ -27,7 +28,8 @@
 !standard 2.3(03)
 !standard 2.3(05)
 !standard 2.3(06)
-!standard 2.6(06)
+!standard 2.4.1(05)
+!standard 2.6(07)
 !standard 3.5(27)
 !standard 3.5(30-34)
 !standard 3.5(37)
@@ -60,6 +62,7 @@
 !standard A.3.2(49)
 !standard A.4(1)
 !standard A.4.1(4)
+!standard A.4.7(46)
 !standard A.4.8(1)
 !standard A.6(1)
 !standard A.7(4)
@@ -245,11 +248,11 @@
 these characters, so it seems better to disallow them, except in comments where
 they cannot do any harm.
 
-We are removing 3.5.2(5) since an implementation may want to provide a
-nonstandard mode where the set of graphic characters is not a proper subset of
-that defined in ISO/IEC 10646:2003, for instance to deal with private use
-characters. We don't want to prevent implementations from doing anything
-useful. This paragraph has no force anyway, since in a nonstandard mode an
+We are removing 3.5.2(4) and 3.5.2(5) since an implementation may want to
+provide a nonstandard mode where the set of graphic characters is not a proper
+subset of that defined in ISO/IEC 10646:2003, for instance to deal with private
+use characters. We don't want to prevent implementations from doing anything
+useful. These paragraphs have no force anyway, since in a nonstandard mode an
 implementation may do pretty much what it likes.
 
 In order to represent 32-bit characters at run-time, we add new declarations to
@@ -341,24 +344,24 @@
 
 Replace 2.1(1) by:
 
-The characters whose code position is 16#FFFE# or 16#FFFF# are not allowed
-anywhere in the text of a program. The characters in categories other_control,
-other_private_use, and other_surrogate are only allowed in comments.
-
+The character repertoire for the text of an Ada program consists of the
+collection of characters described by the ISO/IEC 10646:2003 Universal
+Multiple-Octet Coded Character Set.
 
-Delete 2.1(2-3).
+Replace 2.1(2-3) by:
 
+A character is any character defined within ISO/IEC 10646:2003
+other than those whose code position is 16#FFFE# or 16#FFFF#.
 
 Replace 2.1(4-14) by:
 
-The character repertoire for the text of an Ada program consists of the
-collection of characters described by the ISO/IEC 10646:2003 Universal
-Multiple-Octet Coded Character Set. The coded representation for these
-characters is implementation defined (it need not be a representation defined
-within ISO/IEC 10646:2003).
+The coded representation for characters is implementation defined (it need not
+be a representation defined within ISO/IEC 10646:2003). The characters whose
+code position is 16#FFFE# or 16#FFFF# are not allowed anywhere in the text of a
+program.
 
 The semantics of an Ada program whose text is not in Normalization Form KC (as
-defined by section 24 of ISO/IEC 10646:2003) are implementation defined.
+defined by section 24 of ISO/IEC 10646:2003) is implementation defined.
 
 The description of the language definition in this International Standard uses
 the character properties General Category, Simple Uppercase Mapping,
@@ -367,7 +370,7 @@
 used by an implementation for the visual representation of the text of an Ada
 program is not specified.
 
-The categories of characters are defined as follows:
+Characters are categorized as follows:
 
 letter_uppercase
 Any character whose General Category is defined to be "Letter, Uppercase".
@@ -396,21 +399,6 @@
 number_letter
 Any character whose General Category is defined to be "Number, Letter".
 
-other_control
-Any character whose General Category is defined to be "Other, Control".
-
-other_format
-Any character whose General Category is defined to be "Other, Format".
-
-other_private_use
-Any character whose General Category is defined to be "Other, Private Use".
-
-other_surrogate
-Any character whose General Category is defined to be "Other, Surrogate".
-
-punctuation_connector
-Any character whose General Category is defined to be "Punctuation, Connector".
-
 separator_space
 Any character whose General Category is defined to be "Separator, Space".
 
@@ -428,6 +416,22 @@
 this list are not defined by ISO/IEC 10646:2003; they are only used for
 convenience in this International Standard.
 
+other_control
+Any character whose General Category is defined to be "Other, Control", and
+which is not defined to be a format_effector.
+
+other_format
+Any character whose General Category is defined to be "Other, Format".
+
+other_private_use
+Any character whose General Category is defined to be "Other, Private Use".
+
+other_surrogate
+Any character whose General Category is defined to be "Other, Surrogate".
+
+punctuation_connector
+Any character whose General Category is defined to be "Punctuation, Connector".
+
 graphic_character
 Any character which is not in the categories other_control, other_private_use,
 other_surrogate, other_format, format_effector, and whose code position is
@@ -441,7 +445,7 @@
 identifiers for all programming languages, but we finally decided against this
 option. Note that it is not our intent to diverge from ISO/IEC TR 10176,
 except to the extent that ISO/IEC TR 10176 itself diverges from ISO/IEC
-10646:2003 (which is the case at the time of this writing).
+10646:2003 (which is the case at the time of this writing [January 2005]).
 
 More precisely, we intend to align strictly with ISO/IEC 10646:2003. It must be
 noted that ISO/IEC TR 10176 is a Technical Report while ISO/IEC 10646:2003 is a
@@ -450,19 +454,13 @@
 choice because there are important differences between the two:
 
 o  ISO/IEC TR 10176 is still based on ISO/IEC 10646:2000 while ISO/IEC
-10646:2003 has already been published for a year.
+10646:2003 has already been published for a year. We cannot afford to delay
+the adoption of our amendment until ISO/IEC TR 10176 has been revised.
 
 o  There are considerable differences between the two editions of ISO/IEC 10646,
 notably in supporting characters beyond the BMP (this might be significant for
 some languages, e.g. Korean).
 
-o  ISO/IEC TR 10176 is a moving target. It is in its fourth edition already, and
-nevertheless needs additional revision to catch up with ISO/IEC 10646:2003. We
-cannot afford to revise the Ada language and the vendors cannot afford to change
-the compilers each time ISO/IEC TR 10176 changes. And we cannot afford to delay
-the adoption of our amendment until ISO/IEC TR 10176 has been revised; we would
-run out of interest, money, and the ISO time table before then.
-
 o  ISO/IEC TR 10176 does not define case conversion tables, which are essential
 for a case-insensitive language like Ada. To get case conversion tables, we
 would have to reference either ISO/IEC 10646:2003 or Unicode, or we would have
@@ -506,11 +504,19 @@
 
 
 Delete 2.1(16).
+
+Replace 2.1(17) by:
 
-Delete 2.1(17).
+The characters in categories other_control, other_private_use, and
+other_surrogate are only allowed in comments.
 
+Replace 2.2(2-5) by:
 
-Replace 2.2(3-5) by:
+The text of a compilation is divided into *lines*.
+In general, the representation for an end of line is implementation defined.
+However, a sequence of one or more format_effectors other
+than the character whose code position
+is 16#09# (CHARACTER TABULATION) signifies at least one end of line.
 
 In some cases an explicit _separator_ is required to separate adjacent lexical
 elements. A separator is any of a separator_space, a format_effector or the end
@@ -519,7 +525,8 @@
 o   A separator_space is a separator except within a comment, a string_literal,
     or a character_literal.
 
-o   Character Tabulation is a separator except within a comment.
+o   The character whose code position is 16#09# (CHARACTER TABULATION) is
+    a separator except within a comment.
 
 
 Replace 2.2(8) by:
@@ -558,10 +565,14 @@
 
 Identifiers differing only in the use of corresponding upper and lower case
 letters are considered the same.
+
+Add after 2.4.1(5):
+
+   digit ::= 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
 
-Add after 2.6(6):
+Add after 2.6(7):
 
-No modification is performed on the sequence of characters in a string_literal.
+No transformation is performed on the sequence of characters in a string_literal.
 
 
 Replace 3.5(28-29) by:
@@ -702,11 +713,8 @@
 (Wide_)Wide_Value; they are not usable as enumeration literals.
 
 
-In 3.5.2(4) change:
+Delete 3.5.2(4).
 
-... Character [and Wide_Character]{, Wide_Character, and Wide_Wide_Character}
-...
-
 
 Delete 3.5.2(5).
 
@@ -895,7 +903,7 @@
 
 Static Semantics
 
-The package Strings.Wide_Wide_Maps has the following declaration.
+The library package Strings.Wide_Wide_Maps has the following declaration.
 
    package Ada.Strings.Wide_Wide_Maps is
       pragma Preelaborate(Wide_Wide_Maps);
@@ -1389,10 +1397,9 @@
 The only characters allowed outside of @fa<comment>s are the
 @fa<graphic_character>s and @fa<format_effector>s.
 @dby
-The characters whose code position is 16#FFFE# or 16#FFFF# are not allowed
-anywhere in the text of a program. The characters in categories
-@fa<other_control>, @fa<other_private_use>, and @fa<other_surrogate> are only
-allowed in @fa<comment>s.
+The character repertoire for the text of an Ada program consists of the
+collection of characters described by the ISO/IEC 10646:2003 Universal
+Multiple-Octet Coded Character Set.
 
 !corrigendum 2.1(2)
 
@@ -1401,9 +1408,11 @@
 
 !corrigendum 2.1(3)
 
-@ddel
+@drepl
 @xcode<@fa<graphic_character ::= identifier_letter | digit | space_character | special_character>>
-
+@dby
+@xindent<A @fa<character> is any character defined within ISO/IEC 10646:2003
+other than those whose code position is 16#FFFE# or 16#FFFF#.>
 
 !corrigendum 2.1(4)
 
@@ -1416,14 +1425,13 @@
 implementation defined (it need not be a representation defined within
 ISO-10646-1).
 @dby
-The character repertoire for the text of an Ada program consists of the
-collection of characters described by the ISO/IEC 10646:2003 Universal
-Multiple-Octet Coded Character Set. The coded representation for these
-characters is implementation defined (it need not be a representation defined
-within ISO/IEC 10646:2003).
+The coded representation for characters is implementation defined (it need not
+be a representation defined within ISO/IEC 10646:2003). The characters whose
+code position is 16#FFFE# or 16#FFFF# are not allowed anywhere in the text of a
+program.
 
 The semantics of an Ada program whose text is not in Normalization Form KC (as
-defined by section 24 of ISO/IEC 10646:2003) are implementation defined.
+defined by section 24 of ISO/IEC 10646:2003) is implementation defined.
 
 !corrigendum 2.1(5)
 
@@ -1443,6 +1451,13 @@
 implementation for the visual representation of the text of an Ada program is
 not specified.
 
+!corrigendum 2.1(6)
+
+@drepl
+The categories of characters are defined as follows:
+@dby
+Characters are categorized as follows:
+
 !corrigendum 2.1(7)
 
 @ddel
@@ -1496,9 +1511,12 @@
 
 !corrigendum 2.1(11)
 
-@ddel
+@drepl
 @xhang<@xterm<@fa<space_character>>
 The character of ISO 10646 BMP named ``Space''.>
+@dby
+@xhang<@xterm<@fa<separator_space>>
+Any character whose General Category is defined to be "Separator, Space".>
 
 !corrigendum 2.1(12)
 
@@ -1508,24 +1526,6 @@
 and is not the @fa<space_character>, an @fa<identifier_letter>, or a
 @fa<digit>.>
 @dby
-@xhang<@xterm<@fa<other_control>>
-Any character whose General Category is defined to be "Other, Control".>
-
-@xhang<@xterm<@fa<other_format>>
-Any character whose General Category is defined to be "Other, Format".>
-
-@xhang<@xterm<@fa<other_private_use>>
-Any character whose General Category is defined to be "Other, Private Use".>
-
-@xhang<@xterm<@fa<other_surrogate>>
-Any character whose General Category is defined to be "Other, Surrogate".>
-
-@xhang<@xterm<@fa<punctuation_connector>>
-Any character whose General Category is defined to be "Punctuation, Connector".>
-
-@xhang<@xterm<@fa<separator_space>>
-Any character whose General Category is defined to be "Separator, Space".>
-
 @xhang<@xterm<@fa<separator_line>>
 Any character whose General Category is defined to be "Separator, Line".>
 
@@ -1540,13 +1540,29 @@
 tabulation (VT), carriage return (CR), line feed (LF), and form feed (FF).
 @dby
 @xhang<@xterm<@fa<format_effector>>
-The characters whose code position is 16#09# (CHARACTER TABULATION), 16#0A#
+The characters whose code positions are 16#09# (CHARACTER TABULATION), 16#0A#
 (LINE FEED(LF)), 16#0B# (LINE TABULATION), 16#0C# (FORM FEED(FF)), 16#0D#
 (CARRIAGE RETURN(CR)), 16#85# (NEXT LINE(NEL)), and the characters in
 categories @fa<separator_line> and @fa<separator_paragraph>.  The names
 mentioned in parentheses in this list are not defined by ISO/IEC 10646:2003;
 they are only used for convenience in this International Standard.
 
+@xhang<@xterm<@fa<other_control>>
+Any character whose General Category is defined to be "Other, Control", and
+which is not defined to be a @fa<format_effector>.>
+
+@xhang<@xterm<@fa<other_format>>
+Any character whose General Category is defined to be "Other, Format".>
+
+@xhang<@xterm<@fa<other_private_use>>
+Any character whose General Category is defined to be "Other, Private Use".>
+
+@xhang<@xterm<@fa<other_surrogate>>
+Any character whose General Category is defined to be "Other, Surrogate".>
+
+@xhang<@xterm<@fa<punctuation_connector>>
+Any character whose General Category is defined to be "Punctuation, Connector".>
+
 !corrigendum 2.1(14)
 
 @drepl
@@ -1584,12 +1600,30 @@
 
 !corrigendum 2.1(17)
 
-@ddel
+@drepl
 @xindent<@s9<1  Every code position of ISO 10646 BMP that is not reserved for a
 control function is defined to be a graphic_character by this International
 Standard. This includes all code positions other than 0000 - 001F, 007F -
 009F, and FFFE - FFFF.>>
+@dby
+@xindent<@s9<1  The characters in categories @fa<other_control>,
+@fa<other_private_use>, and @fa<other_surrogate> are only allowed in comments.>>
+
+!corrigendum 2.2(2)
 
+@drepl
+The text of a @fa<compilation> is divided into @i<lines>.
+In general, the representation for an end of line is implementation defined.
+However, a sequence of one or more @fa<format_effector>s other
+than character tabulation (HT) signifies at least one end of line.
+@dby
+The text of a @fa<compilation> is divided into @i<lines>.
+In general, the representation for an end of line is implementation defined.
+However, a sequence of one or more @fa<format_effector>s other
+than the character whose code position
+is 16#09# (CHARACTER TABULATION) signifies at least one end of line.
+
+
 !corrigendum 2.2(3)
 
 @drepl
@@ -1615,7 +1649,8 @@
 @drepl
 @xbullet<Character tabulation (HT) is a separator except within a @fa<comment>.>
 @dby
-@xbullet<Character Tabulation is a separator except within a @fa<comment>.>
+@xbullet<The character whose code position is 16#09# (CHARACTER TABULATION)
+is a separator except within a @fa<comment>.>
 
 !corrigendum 2.2(8)
 
@@ -1665,9 +1700,9 @@
 
 @xbullet<The characters in category @fa<other_format> are eliminated.>
 
-@xbullet<Full case folding, as defined by documents referenced in the note in
-section 1 of ISO/IEC 10646:2003, is applied to obtain the uppercase version
-of each character.>
+@xbullet<Locale-independent full case folding, as defined by documents
+referenced in the note in section 1 of ISO/IEC 10646:2003, is applied to obtain
+the uppercase version of each character.>
 
 !corrigendum 2.3(06)
 
@@ -1680,16 +1715,22 @@
 3  @fa<Identifier>s differing only in the use of corresponding upper and
 lower case letters are considered the same.>>
 
-!corrigendum 2.6(06)
+!corrigendum 2.4.1(05)
 
 @dinsa
-A @i<null string literal> is a @fa<string_literal> with no @fa<string_element>s
-between the quotation marks.
+@xcode<@fa<exponent ::= >@ft<E>@fa< [+] numeral | >@ft<E>@fa< - numeral>>
 @dinst
-No modification is performed on the sequence of characters in a
-@fa<string_literal>.
+@xcode<@fa<digit ::= >@ft<0>@fa< | >@ft<1>@fa< | >@ft<2>@fa< | >@ft<3>@fa< | >@ft<4>@fa< | >@ft<5>@fa< | >@ft<6>@fa< | >@ft<7>@fa< | >@ft<8>@fa< | >@ft<9>>
 
+!corrigendum 2.6(07)
 
+@dinsa
+@xindent<@s9<NOTES@hr
+6  An end of line cannot appear in a @fa<string_literal>.>>
+@dinst
+@xindent<@s9<7  No transformation is performed on the sequence of
+characters in a @fa<string_literal>.>>
+
 !corrigendum 3.5(27)
 
 @dinsa
@@ -1720,10 +1761,9 @@
 identifier in upper case or the corresponding character literal (including the
 two apostrophes); neither leading nor trailing spaces are included. For a
 @i<nongraphic character> (a value of a character type that has no enumeration
-literal associated with it), the result is a corresponding language-defined or
-implementation-defined name in upper case (for example, the image of the
-nongraphic character identified as @i<nul> is "NUL" -- the quotes are not part
-of the image).>
+literal associated with it), the result is a corresponding language-defined
+name in upper case (for example, the image of the nongraphic character
+identified as @i<nul> is "NUL" -- the quotes are not part of the image).>
 
 @xindent<The image of a floating point value is a decimal real literal best
 approximating the value (rounded away from zero if halfway between) with a
@@ -2043,14 +2083,10 @@
 
 !corrigendum 3.5.2(4)
 
-@drepl
+@ddel
 In a nonstandard mode, an implementation may provide other interpretations for
 the predefined types Character and Wide_Character, to conform to local
 conventions.
-@dby
-In a nonstandard mode, an implementation may provide other interpretations for
-the predefined types Character, Wide_Character, and Wide_Wide_Character to
-conform to local conventions.
 
 !corrigendum 3.5.2(5)
 
@@ -2388,7 +2424,8 @@
    -- @ft<@i<Contains each Wide_Character value WC such that Characters.Is_Character(WC) is True>>>
 @dby
 @xcode<   Character_Set : @b<constant> Wide_Maps.Wide_Character_Set;
-   -- @ft<@i<Contains each Wide_Character value WC such that Characters.Handling.Is_Character(WC) is True>>>
+   -- @ft<@i<Contains each Wide_Character value WC such that>>
+   -- @ft<@i<Characters.Handling.Is_Character(WC) is True>>>
 
 !comment Updated for AI-161 change.
 !corrigendum A.4.8(01)
@@ -2403,12 +2440,12 @@
 
 @i<@s8<Static Semantics>>
 
-The package Strings.Wide_Wide_Maps has the following declaration.
+The library package Strings.Wide_Wide_Maps has the following declaration.
 
 @xcode<@b<package> Ada.Strings.Wide_Wide_Maps @b<is>
    @b<pragma> Preelaborate(Wide_Wide_Maps);
 
-   -- Representation for a set of Wide_Wide_Character values:
+   -- @ft<@i<Representation for a set of Wide_Wide_Character values:>>
    @b<type> Wide_Wide_Character_Set @b<is private>;
    @b<pragma> Preelaborable_Initialization(Wide_Wide_Character_Set);
 
@@ -6096,6 +6133,149 @@
 exercise was to show that they were not (and the move to Unicode 4.0.0
 doesn't change this conclusion).  As I recall it took me roughly half a
 day to produce them, so it cannot take Robert more than half an hour ;-)
+
+*************************************************************
+
+From: Dan Eilers
+Sent: Friday, January 28, 2005  11:56 AM
+
+Robert Dewar wrote:
+> P.S. Pascal's tables in the AI for letters and numbers are
+> significantly wrong. If people are interested, I am happy to
+> post GNAT's understanding of the unicode categorizations :-)
+
+Are you offering to post "GNAT's" understanding of the the
+unicode categorizations as public domain information that
+anyone can incorporate into proprietary software with no
+obligation whatsoever, including acknowledgement, copyright notice, etc.?
+
+If so, I would welcome such a post, and would not be required by my
+attorneys to shade my eyes from reading it.
+
+Pascal Leroy wrote:
+> I know, I
+> know, but please don't post your tables.  If I read any piece of code from
+> GNAT my brain gets polluted by public domain software, and IBM won't let
+> me work on Apex anymore (it does sound silly, but it's absolutely true).
+
+Are the tables that currently exist in this AI (or any other AI)
+subject to any sort of intellectual property ownership rights
+that would prevent their incorporation into proprietary software
+with no obligation whatsoever?  If so, please let us know which
+AI's these are, since our attorneys have similar concerns to
+those of IBM, and won't let us do compiler work anymore if we
+have been potentially contaminated by material for which someone
+could potentially claim infringement.
+
+****************************************************************
+
+From: Robert A. Duff
+Sent: Friday, January 28, 2005  1:02 PM
+
+I've no idea.
+
+But the RM itself is copyright, and there are some requirements stated.
+Most Ada implementations include excerpts from the RM -- the spec
+of package Ada.Text_IO, for example.
+
+****************************************************************
+
+From: Robert Dewar
+Sent: Friday, January 28, 2005  2:33 PM
+
+Tables like this are not protectable, since the material they contain
+is dictated entirely by external requirements (in this case the unicode
+database).
+
+****************************************************************
+
+From: Robert Dewar
+Sent: Friday, January 28, 2005  2:36 PM
+
+Exactly, the tables are not protectable in any case. The GNAT code
+that searches the table is protected by copyright, but licensed
+under the GMGPL which allows you to incorporate it into proprietary
+software with no obligation whatsoever (just as our customers writing
+proprietary and classified code incorporate the GNAT run time).
+
+****************************************************************
+
+From: Dan Eilers
+Sent: Friday, January 28, 2005  3:04 PM
+
+If the tables are not protectable, but the GNAT code is protected,
+then I would suggest that you post your corrected version of the tables,
+and perhaps any high-level description of the GNAT algorithms that
+you are willing and able to contribute to the public domain, but not
+the actual copyrighted GNAT code.
+
+>                                                      The GNAT code
+> that searches the table is protected by copyright, but licensed
+> under the GMGPL which allows you to incorporate it into proprietary
+> software with no obligation whatsoever (just as our customers writing
+> proprietary and classified code incorporate the GNAT run time).
+
+I believe that anyone making use of copyrighted GMGPL code is in fact
+under certain obligations, such as retaining the GMGPL copyright notices
+on derived works.
+
+****************************************************************
+
+From: Pascal Leroy
+Sent: Saturday, January 29, 2005  4:40 AM
+
+Dan asked:
+
+> Are the tables that currently exist in this AI (or any other
+> AI) subject to any sort of intellectual property ownership
+> rights that would prevent their incorporation into
+> proprietary software with no obligation whatsoever?
+
+Well, as others have pointed out, the tables in question are broken, so
+incorporating them in a piece of software is probably not a good idea
+anyway ;-)
+
+These tables were posted when Rational was still an independent company,
+and Rational had a very lax policy with respect to IP, so it would have
+been fine at the time to incorporate them in a product.  They didn't have
+a copyright notice, and that was on purpose.
+
+IBM of course has rather stricter policies, so I suppose that today I
+wouldn't post the tables anymore, at least not without a copyright notice
+and/or approval by our legal department.
+
+> If so, please let us know which AI's these are...
+
+This is an irrelevant question.  The only document you need to implement
+Ada-related products is the AARM for Ada 2005, and certainly the copyright
+situation for the AARM is very clear.
+
+****************************************************************
+
+From: Robert Dewar
+Sent: Saturday, January 29, 2005 5:03 AM
+
+Pascal Leroy wrote:
+
+> These tables were posted when Rational was still an independent company,
+> and Rational had a very lax policy with respect to IP, so it would have
+> been fine at the time to incorporate them in a product.  They didn't have
+> a copyright notice, and that was on purpose.
+
+a) copyright notices have zero legal sigficance (true since 1986)
+b) tables like this are not copyrightable anyway
+
+>
+> This is an irrelevant question.  The only document you need to implement
+> Ada-related products is the AARM for Ada 2005, and certainly the copyright
+> situation for the AARM is very clear.
+
+That surely is NOT true here, the necessary information for implementing
+the unicode stuff is not incorporated in the AARM (should it be? I would
+think the answer should be yes, we should include the tables in the AARM).
+
+Is the copyright situation for the AARM clear. It is owned by everyone
+who has contributed text. Have they all signed waivers or assignments?
 
 *************************************************************
 

Questions? Ask the ACAA Technical Agent