[
Lists Home |
Date Index |
Thread Index
]
Every time I see keys and values presented this way I conclude that
whoever concocted this setup doesn't really give a damn about markup, so
further discussion about the merits of the markup aspects of their
design is likely pointless.
That still leaves plenty of information modeling issues, and lack of
grouping mechanisms seems to be the main one here.
danny666@virgilio.it (Danny Ayers) writes:
><appSettings>
> <!-- settings related to X -->
> <add key="a" value="1"/>
> <add key="b" value="2"/>
> <!-- settings related to Y -->
> <add key="c" value="3"/>
> <add key="d" value="4"/>
></appSettings>
or in the original:
><appSettings>
> <!-- Start xxxx.Net -->
> <!-- ServerType, PartnerAPI = 2, CorbisInternal = 1 -->
> <add key="ServerType" value="1"/>
> <!-- Framework -->
> <add key="xxxxOne.Validations.ValidationConstructString"
> value="CONNECTIONSTRING=data"/>
> <!-- End xxxx.Net -->
> </appSettings>
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org
|
