W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > May 2006

RE: Proposed text for ISSUE-10 - Mapping Element and Type names

From: <paul.downey@bt.com>
Date: Mon, 8 May 2006 15:45:35 +0100
Message-ID: <2A7793353757DB4392DF4DFBBC952255E9082B@I2KM11-UKBR.domain1.systemhost.net>
To: <edday@obj-sys.com>, <public-xsd-databinding@w3.org>

> Do you plan to raise the issue of the case of names as part 
> of this?  We
> have found that it seems more natural for mapping to 
> programming languages
> if type names are in uppercase and element names are in 
> lowercase.  I think
> JAXB makes this conversion automatically.  

I've seen tools impose a language naming convention, such as
Java's camelNamesForProperties and PascalNamesForTypes in the
generated code, but that's by no means a common convention in 
other programming languages and shouldn't leak back onto the
wire, no?

> A frequent problem is when schema authors decide to make 
> type and element names the same.  It requires that
> decorations of some sort be applied to the names to keep them 
> separate.

That's a good point. In a way I see this as being similar to 
the issue of people giving their types or elements names such
as "object" or "customer-order" given it's a language specific

Received on Monday, 8 May 2006 14:46:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:12 UTC