[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: <ged.corba.Node>


Re:  <ged.corba.Node>
One place you see this is in automatic translations from code or IDL.  I had
to work with some xml that was automatically created from the java objects
created for CORBA messages, and they were pretty awful, about what you show.
The IDL developers rightly create readable element names according to
notions of naming conventions, but those names aren't intended to be
instantiated in the message instance.  It's not so easy to get good element
names from such IDL by machine.

Cheers,

Tom P

[Bullard, Claude L (Len]

> It's legal.  That is how the Oster DTD element type names were designed
(early 90s).
> One can do fancy tricks with microparsing that way.   On the other hand, a
nested
> structure can achieve this as well.    As to naming collisions, is the
system so open that
> you can't control that without resorting to element dot naming?
>
> While we're here and in the best practices category,
> I've seen some pretty awful type trees lately
> designed by object programmers determined beyond all good sense to carry
> naming conventions all the way from root to leaf without stopping to
consider
> the structure provides implicit nested naming.
>
> <paramTables>
>    <paramTable>
>       <paramTableName></paramTableName>
>       <paramTableDescription></paramTableDescription>
>       <paramColumns>
>          <paramColumn>
>             <paramColumnName></paramColumnName>
>             <paramColumnPosition></paramColumnPosition>
>             <paramColumnType></paramColumnType>
>             <paramColumnDescription><paramColumnDescription>
>             <paramColumnUnits></paramColumnUnits>
>             <paramColumnMin></paramColumnMin>
>             <paramColumnMax></paramColumnMax>
>             <paramColumnIndex></paramColumnIndex>
>             <paramColumnUnique></paramColumnUnique>
>             <paramColumnWidth></paramColumnWidth>
>             <paramColumnPrecision></paramColumnPrecision>
>          </paramColumn>
>
> The ratio of data to markup in this design is probably less than
> 5% data.   Anyone care to comment on why one would choose
> to work up this kind of scheme or what it is like to use in
> practice?
>


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.