> We could enforce this - that other field names must not start with
> underscore. But what I am thinking is that in general, we should treat
> *private* link properties differently, therefore we probably should add
> a reserved naming prefix for all link properties (when writing them to
> the private configuration file and stripping the prefix when reading
> them from the file).
Right, sort of an optional qualifier, which we could make either
implicit or explicit, for instance:
[<qualifier>:]<name>=<value>
name=string,bge0;class=int,1;property:mtu=int,9000;
Sounds like any of the alternatives requires to reserve at least one
character (leading underscore, colon, etc) for special use.
-Artem
