Overview

The development of descriptive names for data elements, fields, and traditional data structures is historically a responsibility of the data architect. Data element names are a form of descriptive classification and identification that provide a context (i.e., a taxonomy). Given that XML is a self-describing metadata language, the responsibility for naming XML elements and attributes is an appropriate segue into the data architecture process. However, traditional techniques for data element naming have a long history that is often constrained by database technologies and products. The application of these traditional data element naming practices to XML elements and attributes can result in cryptic, complex, highly abbreviated, or, alternatively, overly verbose names.

To exploit the descriptive capabilities of XML and apply the benefits of a rigorous taxonomy, there are a number of guidelines that should be followed. Basically, all XML element and attribute names should be:

• Descriptive

• Concise

• Devoid of abbreviations or acronyms (unless easily recognized by a broad audience)

• Of "reasonable" length

Some data architects have adopted naming processes that are descriptive and intuitive and do not violate the basic syntax rules of XML. When these processes are applied consistently and are well received by both the technology and business community, they can be adapted for application to XML data element and attribute names.