Quote all keywords in value syntax expression definitions.

[skynavga]

For example, auto should be written "auto".

[skynavga]

This change is intended to address the potential for ambiguous reading of identifier tokens, and, as such, is an editorial change since it does not change the intended or actual syntax.

[skynavga]

In addition, change any tokens that use ' delimiter to use " delimiter.

[nigelmegitt]

I think this applies only to attribute value syntax, in other words there is no need to modify the XML Representations of elements. @skynavga do you agree?

[nigelmegitt]

Arguing for modifying XML Representations of elements as well as attribute value syntax, consider for example: §6.1.5 ttp:extension has an XML Representation that includes the adjacent lines:

  value = (optional|required|use|prohibited) : see prose below
  xml:id = ID

I suppose there could be ambiguity about whether xml:id should have the value ID or be an identifier, given that the value attribute takes one of four string keywords that are listed.

As part of this issue it could be modified to:

  value = ("optional" | "required" | "use" | "prohibited") : see prose below
  xml:id = ID

Doing this across the whole spec will take a while...

[nigelmegitt]

I've answered the question for myself: yes, it should include XML Representations of elements. Will push a fix for that in a moment.