"at risk" language for TriG sparql-alignment features

Text for completing ACTION-279 pertaining to ISSUE-137 is below 
(proposed text for the TriG spec, describing the two features at 
risk).    The document doesn't have a ToC which makes it a little hard 
to see where it should go, but I'm thinking right before or right after 
the grammar.

   -- Sandro

    Feature At Risk: GRAPH Keyword


In this version of TriG, but not previous versions, the keyword "GRAPH" 
may occur before graph names, as specified in the grammar. When this 
keyword is present, the syntax of TriG aligns with the syntax of SPARQL, 
so sections of a TriG document can be cut-and-pasted into SPARQL 
queries, and people used to reading SPARQL can more easily understand 
TriG documents.

This keyword is ignored by parsers for this version of TriG, but may 
cause a syntax error for older parsers, so its use should be avoided 
until all likely TriG-consuming systems have updated parsers.  Once 
updated parsers are widespread, the use of GRAPH keyword is suggested to 
provide alignment with SPARQL.

This feature is marked as being "at risk", which means the Working Group 
seeks feedback from the community on whether to allow the GRAPH keyword 
to be present in TriG.  The group might remove this feature without 
publishing another Last Call Working Draft.   Users with a strong 
preference or with information which might influence the Working Group's 
decision whether to keep this feature are encouraged to send feedback.


    Feature At Risk: Bare Triples

In this version of TriG, but not previous versions, triples in the 
default graph are allowed to occur outside of any curly braces. This 
feature is provided in order to align the TriG syntax with the SPARQL 
syntax, to allow for cut-and-paste and for easier TriG comprehension by 
people working with SPARQL.  It also makes TriG an extension of Turtle; 
a TriG file using bare triples and no named graphs is also a Turtle file 
(with the same semantics).

Bare triples will not be understood by some older TriG parsers, so their 
use should be avoided until all likely TriG-consuming systems have 
updated parsers.  Once updated parsers are widespread, the use of bare 
triples is suggested to provide alignment with SPARQL.

This feature is marked as being "at risk", which means the Working Group 
seeks feedback from the community on whether to allow bare triple in 
TriG.  The group might remove this feature without publishing another 
Last Call Working Draft.   Users with a strong preference or with 
information which might influence the Working Group's decision whether 
to keep this feature are encouraged to send feedback.