RE: Context parameters within Message Bodies

[Kevin Hawkins]

An offlist suggestion someone made (msn) - all 'context' bearing parameters
must start with an Uppercase letter or are all uppercase - and normal data
vicaversa

Username=kevin
total=1

OR

USERNAME=kevin
Total=1

Doesn't sacrifice either readability or complexity but facilitates state
manitoring

Or do we agree that the schema must define context parameters and we must
expect any controllers to be able to import schemas somehow (which is
onerous). Howver controllers by definition are likely to be fairly capable
devices.





> >But we still have the username context within the body -
> how would we
> >resolve this ? We need somehow to know that username is a
> 'context'
> >parameter - so we could choose to identify it as such eg
>
> >Status
> >{
> > Total=1
> > +username=kevin
> >} OR
> >Status
> >{
> > Total=1
> > username><kevin
> >} OR
> >*username OR username~kevin or some such identifier but I
> feel his is not
> >really 'xAPlike'
>
> Yuck! Sorry!! It loses the distinction between ASCII and
> binary data too, unless you start doubling up
> UserName=~Kevin, but this also loses potentially valid
> characters from the variable part, causing unexpected problems.