DDS4CCM11 — Name patterns should support underscores and scoping

The name patterns in the normative XML schema in Annex C do not support underscores. For detailed or lengthy profile names (especially including internal acronyms), using underscores significantly improves readability.

In addition, the elementName type is used both for the name and base_name attributes of the qosProfile type; however, the pattern for the elementName type does not support scoping, which is needed for inheritance between profiles in different libraries.

In order to address these, I propose that the elementName and topicNameFilter patterns be changed from:

"([a-zA-Z0-9 ])+"

to:

"^((:?([a-zA-Z0-9_])(:[a-zA-Z0-9_]))*)$"

The latter is the currently commented-out pattern in the schema with the addition of the underscore.