Issue 1251:  "Safe" keyword identifier issue (obv-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: Above rules seem to imply that the
 "safe" keyword identifier can only occur before the first scoped name in the
 <value_parent_spec>, whereas I think the actual intent is that it can only 
 occur before a non-abstract value type, of which there is at most one in the
 list, although it need not be the first. Since this can"t be expressed in the
 rules exactly, I would simply amend the rule to be:
  
       <value_parent_spec> ::= ":" [ <safe_token> ] <scoped_name>
  
               { "," [ <safe_token> ] <scoped_name> }*
  
 and simply express the semantic restriction in the text. There already is a
 brief mention of the semantics of the "safe" keyword in section 5.3.2.5 
 "Substitutability Issues". Perhaps another sentence or two would help clarify
 the intended usage.
 

Resolution: 
Revised Text: 
Actions taken:
April 28, 1998: received issue
July 30, 1998: closed issue
Discussion: 

End of Annotations:=====
Issue 1251 (David Morrill)
-------------------------
Above rules seem to imply that the
'safe' keyword identifier can only occur before the first scoped name
in the
<value_parent_spec>, whereas I think the actual intent is that it can
only 
occur before a non-abstract value type, of which there is at most one
in the
list, although it need not be the first. Since this can't be expressed
in the
rules exactly, I would simply amend the rule to be:
 
      <value_parent_spec> ::= ":" [ <safe_token> ] <scoped_name>
 
              { "," [ <safe_token> ] <scoped_name> }*
 
and simply express the semantic restriction in the text. There already
is a
brief mention of the semantics of the 'safe' keyword in section
5.3.2.5 
'Substitutability Issues'. Perhaps another sentence or two would help
clarify
the intended usage.