Altova Mailing List Archives

Re: conventions for case of names?

From: Rick JELLIFFE <ricko@--------.--->
To: xml-dev@---.---
Date: 5/8/2000 10:30:00 PM
"DuCharme, Robert" wrote:
> We're deciding on naming standards for a large project and I wanted to ask
> who has been involved with such decisions on projects or who knows of
> explicit standards.

I guess every company will have inhouse conventions, but I don't know if
anyone has ever come up with convincing arguments one way or another for
particular spelling conventions; just as with programming languages.

You might however detect that XML used functionally (e.g. XSLT) will
tend to have "-" while XML used descriptively (e.g. XML Schema) will
tend to use camelCase, in the W3C specs. (One could speculate that this
is the influence of TeX (i.e., literate programming), emacs and DSSSL on
the functional specs. This seems a good decision, from the point of view
of making these specs pallatable to existing text processing and
document processing people.)

When XML was being developed, I proposed that the various punctuation
marks available should be quaranteened with specific semantics: "_"
would be used in place of spaces, "." would be a class/container
operator, "-" would be a phrase joiner, and "::" might be used for
hierarchical names (following ISO 9070 rules).  One of the sample SGML
declarations I made had this.  But there was a feeling that such a rule
could not be made without compromising backwards-compatability with
existing DTDs (and with names taken from databases).   (An in the end,
the various ideas for hierarchical names reduced (degenerated) into
two-level formal public names using URIs: emerging as XML Namespaces.)

Rick Jelliffe

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.