> 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.
>
>
> (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>
I'm curious Simon (or anyone) about how you would go about improving the
representation of keys & values (or modelling when the solution seems to
suggest keys & values).
Cheers,
Danny.
