No subject

(not of the internal representation of the information), to provide
compatibility hints to the user. This can be implemented in various
ways, for example Anna knows that his friend Bob only likes to hear
S3M sound modules, so she may check a S3M compatibility flag in her
fancy composer, so she'll be sure that the composer application *won't
allow her* to add features which cannot be represented in a S3M file.

libavsequencer may help the application providing such compatibility
information in some table or providing an API for that, which should
be anyway separated from the sound module representation aka BSS.

Regards.