CVS difference for ais/ai-00170.txt
--- ais/ai-00170.txt 1998/10/16 18:42:43 1.3
+++ ais/ai-00170.txt 1999/04/01 21:37:57 1.4
@@ -1,26 +1,28 @@
!standard 13.03 (05) 98-10-15 AI95-00170/01
!class confirmation 96-11-16
+!status ARG Approved (with changes) 8-0-1 99-03-24
!status work item 98-10-15
!status received 96-11-16
!priority Low
!difficulty Easy
!subject Can an attribute defined in an annex be set in an attribute definition clause?
-!summary 98-10-15
+!summary
An attribute defined in an annex cannot be set in an attribute definition
-clause, unless the Reference Manual explicitely allows it.
+clause, unless the Reference Manual explicitly allows it.
+!question
-!question 96-11-16
+Consider non-specifiable attribute defined in an annex (Partition_Id, for
+example). Can an implementation support an attribute definition clause
+for such an attribute? (No.)
-Can an attribute defined in an annex be set in an attribute definition clause?
+!response
-!response 98-10-15
-
13.3(5) says that:
"An attribute_designator is allowed in an attribute_definition_clause only if
- this International Standard explicitely allows it, or for an implementation
+ this International Standard explicitly allows it, or for an implementation
defined attribute if the implementation allows it. [...]"
1.1.2 (14) says that:
@@ -29,7 +31,7 @@
Therefore, the legality rule in 13.3(5) clearly applies to annexes as well as to
the core language.
-!appendix 98-10-15
+!appendix
!section 13.3(05)
!subject Can an attribute defined in an annex be set in an attribute definition clause?
Questions? Ask the ACAA Technical Agent