Title: RE: [xml-dev] a useful naming convention





Example


<Root>

  <Atag>

    <btag/>

    <ctag/>

  </Atag>

</Root>


<btag> evolves and needs to change to become a complex element.  Do you rename <btag> to <Btag> because it is now a complex structure, or keep it lower case?

<Root>

  <Atag>

    <btag>

      <dtag/>

    </btag>

    <ctag/>

  </Atag>

</Root>


Even worse what if <btag> needs to incorporate a complex structure.  Now <btag> includes upper case elements.


<Root>

  <Atag>

    <btag>

      <Dtag>

         <etag/>

         <ftag/>

      </Dtag>

    </btag>

    <ctag/>

  </Atag>

</Root>


Either way <btag> becomes inconsistant with the naming convention.


--

Jon Barwell


-----Original Message-----

From: Bryan Rasmussen [mailto:bry@i...] 

Sent: 02 August 2005 08:57

To: Barwell Jonathan

Cc: xml-dev@l...

Subject: RE: [xml-dev] a useful naming convention










Citat Barwell Jonathan <Jonathan.Barwell@a...>:


> The one big problem I can see with this is that if you subsequently 

> want to restructure your schema, e.g. a simple tag needs complex 

> structure, then you not only have to restructure but you have to 

> rename the tags as well.  This will look nice to start with but after 

> a couple of evolutions there will be Upper and Lower case tags all 

> over the place.

> 




Do you mean that your upper and lower case tags will not be sorted properly in your schema?








-- 

Bryan Rasmussen



************************************************************************

DISCLAIMER

The information contained in this e-mail is confidential and is intended

for the recipient only.

If you have received it in error, please notify us immediately by reply 

e-mail and then delete it from your system. Please do not copy it or

use it for any other purposes, or disclose the content of the e-mail

to any other person or store or copy the information in any medium. 

The views contained in this e-mail are those of the author and not 

necessarily those of Admenta UK Group.

************************************************************************