Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Element names guidelines

From: Frans Englich <frans.englich@-----.--->
To: xmlschema-dev@--.---
Date: 11/18/2004 2:32:00 PM

Hello,

At the risk of starting a flamefest, I wonder: What is the best naming 
conventions for elements and attributes? A crucial question in modeling XML 
formats.

Assuming the phrase "car description" should be translated to an element name, 
and the criteria for judgment are easy to type and readability, there exist a 
number of different alternatives:


<CarDescription>
----------------
In my opinion, too elaborated; The capitalized C is unnecessary since the 
phrase is automatically distinguished at the boundaries by the tag 
characters.

<carDescription>
----------------
I'll call this the WXS-style. I find it (visually) beautiful and simple. It's 
relatively easy to read. Perhaps I'm biased by the Qt/KDE API. Regarding 
typing ergonomics it perhaps could be better than capitalized letters.


<car-description>
-----------------
I'll call this the XSLT-style. IMO, more heavy and dense in its look, but 
easier to type.

<cardescription>
----------------
The Docbook-style. Hard to read but fast to type. That this naming scheme was 
chosen, suggests that other criteria than readability and typing ergonomics 
exists..


But which one is best, and is there other alternatives? What other criteria 
are there, rendering my ramblings simplified? Does it depend on usage 
scenario?

What was the reasonings behind XSLT's and WXS's styles?


Cheers,

		Frans




From ekimber@i... Thu Nov 18 14:56:34 2004
Received: from lisa.


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