The change I suggested is consistent with the 8/17/2003 RDF, as it adds the keycode back to the definition of DEV_DB08[MySys], which is what was causing the syntax error.
To add more details:
The syntax for a button definition in the RDF is:
[
generic name:]
name[
=keycode[
:restrictions]]
where fields enclosed in square brackets are optional.
If the generic name is omitted, it defaults to the name.
If the keycode is omitted it defaults to the one more than the keycode of the previous button and the restrictions default to those used with the previous button.
If the keycode is specified but the restriction in not (restrictions can only be specified when the keycode is also specified) the restriction returns to the default value (which is specified elsewhere in the RDF).
Restrictions were added after I started working on RM as a way to indicate what was not allowed for a given button. Some remotes have some buttons that can't have keymoves, or learned signals, or macros. Also, extenders define special keys (eg DEV_AUX) that can only be used in macros. IR and RM shouldn't allow you to assign things to these buttons.
So, the definition in the current RDF
DEV_DB08[MySys]:AllBind
results in a key with generic name DEV_DB08[MySys], name AllBind, keycode $70 (one more than the keycode of the previous key, all the way back to DEV_TV). and restriction AllBind (the same as the previous key, all the way back to DEV_TV).
The definition I suggested
DEV_DB08[MySys]=$70:AllBind
is a key definition with generic name and name DEV_DB08[MySys], keycode $70 and restriction AllBind.
The difference is just that the name (as displayed in IR and RM) of the key changes to DEV_DB09[MySys]. That's all.
The other choice that would result in the same thing is just
DEV_DB09[MySys]
but we usually include keycodes and restrictions with the first key on a line just for completeness.
Go ahead and make the change to the RDF.