1Blurb::
2Name the interface block; helpful when there are multiple
3
4Description::
5The optional \c id_interface keyword accepts a string that uniquely
6identifies this interface block.  A model can then use this interface
7by specifying the same string in its \c interface_pointer
8specification.
9
10<b>Default Behavior</b>
11
12If the \c id_interface specification is omitted, a particular
13interface specification will be used by a model only if that model
14does not include an \c interface_pointer and the interface block was
15the last (or only) one parsed.
16
17<b>Usage Tips</b>
18- It is a best practice to always use explicit interface IDs and
19  pointers to avoid confusion.
20
21- If only one interface block exists, then \c id_interface can be
22  safely omitted from the interface block (and \c interface_pointer
23  omitted from the model specification(s)), since there is no
24  ambiguity.
25
26
27Topics::	block_identifier
28
29Examples::
30For example, a model specification including
31\verbatim
32model
33  interface_pointer = 'I1'
34\endverbatim
35will link to an interface with
36\verbatim
37id_interface = 'I1'
38\endverbatim
39
40Theory::
41Faq::
42See_Also::
43