Issue 17399: Name patterns should support underscores and scoping (dds4ccm-ftf)
Source: Northrop Grumman (Mr. Trent Nadeau, trent.nadeau(at)ngc.com)
Nature: Revision
Severity: Minor
Summary: 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.
Resolution: 
Revised Text: 
Actions taken:
May 30, 2012: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 30 May 2012 10:10:21 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Trent Nadeau
Employer:        Northrop Grumman
mailFrom:        Trent.Nadeau@ngc.com
Terms_Agreement: I agree
Specification:   DDS for Lightweight CCM
Section:         Annex C
FormalNumber:    formal/2012-02-01
Version:         1.1
Doc_Year:        2011
Doc_Month:       February
Doc_Day:         01
Page:            43
Title:           Name patterns should support underscores and scoping
Nature:          Revision
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


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.