A form chunk inside a form is a full-fledged data section.  this means you
can build a composite object such as a multi-frame animation sequence by
nesting available picture FORMs and sound effect FORMs.  You can insert
additional chunks with information like frame rate and frame count.

Using composite forms, you leverage on existing programs that create and
edit the component FORMs.  Those editors may even look into your composite
object to copy out its type of component.  Such editors are not allowed to
replace their component objects within your composite object.  That's
because the IFF standard lets you specify consistency requirements for the
composite FORM such as maintaining a count or a directory of the
components.  Only programs that are written to uphold the rules of your
FORM type may create or modify such FORMs.

Therefore, in designing a program that creates composite objects, you are
strongly requested to provide a facility for your users to import and
export the nested forms.  import and export could move the data through a
clipboard or a file.

Here are several existing form types and rules for defining new ones:

 ftxt      ilbm      pics      other macintosh resource types