RE: Should one adopt the tag naming convention of anexisting X

WIPO Standard ST.36, vocabulary for patent documents, uses hyphen separators rather than underscore or camel case.  Java developers have frequently complained of this, since the hyphen is apparently a reserved character in Java and their tools for automatically creating classes stumble over them when used in element names, requiring manual intervention, or other cleanup actions (so I’m told). 

Is the Java objection real?  Is there any real technical reason to prefer one over the other?

Personally, I find hyphenated element names easier to read than camel case, and vastly easier to type than underscores. 

In general, I’m in the same camp as many others with regard to the source of element names: the business vocabulary takes precedence.  We also try to follow ISO 11179-5, but where there is the slightest chance the results will confuse or snag the business users, we break those rules without hesitation.

Bruce B Cox

OCIO/AED/SAED

571-272-9004

From: Uche Ogbuji [mailto:uche@ogbuji.net]
Sent: 2012 February 3, Friday 15:18
To: xml-dev@l...
Subject: Re: Should one adopt the tag naming convention of an existing XML vocabulary or create one's own tag naming convention?

--
Uche Ogbuji                       http://uche.ogbuji.net
Weblog: http://copia.ogbuji.net
Poetry ed @TNB: http://www.thenervousbreakdown.com/author/uogbuji/
Founding Partner, Zepheira        http://zepheira.com
Linked-in: http://www.linkedin.com/in/ucheogbuji
Articles: http://uche.ogbuji.net/tech/publications/
Friendfeed: http://friendfeed.com/uche
Twitter: http://twitter.com/uogbuji
http://www.google.com/profiles/uche.ogbuji