Feature expression syntax; quoted strings

Folks,

In looking through RFC 2533, I note that a string value for a feature may 
not contain a double quote character, there being no escape mechanism 
within a string.  (This was lifted from RFC 2234, which has alternative 
mechanisms for describing specific individual characters.)  On reflection, 
it seems that assuming that a feature value can never contain a double 
quote character could cause problems in the future.

I am thinking that there should probably be an escape mechanism defined so 
that a quote character can be included in a string -- using a backslash 
escape character is the technique that strings to mind, so that special 
constructs '\\' and '\"' within a string are introduced.

I am not aware of any current use of RFC2533 which would be impacted by 
such a change.

If this change is felt to be a Good Thing, it will have some impact on the 
feature-hash draft (section 3.1.1: description of normalization logic).

Process question:  in view of the CONNEG WG being wound up, what is the 
process for moving the work to draft standard, as and when implementations 
are created?

#g

------------
Graham Klyne
([email protected])