It was true with MIC 2.0 and earlier that the name of the MICfieldspace must be unique with regards to page names. That is, if there was a page ``new_accounts.html'', then one could not have name="new_accounts" in any fieldspace. Under MIC 3.0, there is effective mangling of the fieldspace names and this is no longer a problem.
It is recommended that the name of the file containing the fieldspace have the same name as the fieldspace plus `.fs.' I.e., it is recommended that the line
<MICfieldspace name="new_accounts" ...
appear within a file called new_accounts.fs.
Note that there are a few reserved words that are disallowed as field
space names. Specifically, `verify' and `inherit' are
forbidden. Other than these, a fieldspace may by any string of
alphabetic characters and the underscore. That is, it must match the
Perl regular expression /A[a-zA-Z_]+
Z/.