CVS difference for ai12s/ai12-0116-1.txt

Differences between 1.3 and version 1.4
Log of other versions for file ai12s/ai12-0116-1.txt

--- ai12s/ai12-0116-1.txt	2014/07/12 02:06:21	1.3
+++ ai12s/ai12-0116-1.txt	2014/09/30 01:52:51	1.4
@@ -1,4 +1,4 @@
-!standard 13.1(9/3)                                  14-07-11  AI12-0116-1/02
+!standard 13.1(9/3)                                  14-09-29  AI12-0116-1/03
 !standard 13.1(9.1/3)
 !class binding interpretation 15-06-19
 !status Corrigendum 2015 14-07-11
@@ -87,9 +87,9 @@
 this way).
 
 The existing rules in 13.1(9/3) and 13.1(9.1/3) could be read to cover all
-aspects. That was purely unintentional; when these paragraphs were to cover
-aspects as well as other kinds of representation/operational items, the
-rewording doesn't restrict the kinds of aspects involved. Thus, the
+aspects. That was purely unintentional; when these paragraphs were reworded
+to cover aspects as well as other kinds of representation/operational items,
+the rewording didn't restrict the kinds of aspects involved. Thus, the
 rewording can be read to cover all aspects. This makes 13.1(9/3) conflict
 with 13.1(9.1/3) - they both seem to apply in some cases.
 
@@ -105,7 +105,7 @@
 13.1.1 so that language laywers will know that it exists.
 
 An alternative would be to define both subtype predicates and type invariants
-as operational aspects. Since 13.1(9.1/3) allow operational aspects on any
+as operational aspects. Since 13.1(9.1/3) allows operational aspects on any
 kind of entity, both could be treated as operational. However, that would
 drag in some inheritance rules that we probably don't want. In addition, we'd
 have to have a default value, and support confirming aspects. That might all

Questions? Ask the ACAA Technical Agent