Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: SV: [xml-dev] a useful naming convention

From: Bryan Rasmussen <bry@------.--->
To: James Lindley Walford <jlw@----.-->
Date: 8/2/2005 7:38:00 PM
Quoting James Lindley Walford <jlw@i...>:

> >As far as the internal syntax of a name is concerned, the only important
> >thing is to try and be consistent: use hyphens or underscores or
> camelCase,
> >but not all three interchangeably.
> 
> >Michael Kay
> 
> I was taught to avoid hypens and underscores due to potential problems with
> e.g. data-binding, though I can't provide concrete examples of such a
> problem. A myth or a reality?
> 

basically I figure it's theoretical, in java which has a lot of databinding
tools a hyphen is not a proper character in an identifier. I would hope that a
databinding tool would have taken this into account and made a workaround  (I
seem to remember that Castor handles it) But maybe that is me being optimistic
and anyway the requirements of naming standards are often based on what
theoretical problems. 

consider the even worse scenario of element names with . in them. Not only
possible databinding headaches, but I suppose css headaches as well if someone
wanted to style the xml via that technology. 

XMI must be a headache for someone.


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent