Adobe framemaker 6.0 User Manual

ADOBE FRAMEMAKER 6.0

<MIFFile 6.00>

<ImportObject

<ImportObEditor inset_editor_name>

<ImportObFile `2.0 internal inset’>

=facet_name

&data_type

&facet_data

...

=facet_name

&data_type

&facet_data

...

=EndInset

>

Because the graphic inset is stored in the FrameMaker product document, the file does not have an Impor-
tObFileDI statement. 

The ImportObFile statement identifies the file as a FrameMaker version 2.0 internal graphic inset file for 
compatibility with earlier versions of FrameMaker products. If you do not plan to use the graphic insets 
generated by your application with earlier versions of FrameMaker products, you can omit this statement.

Application-specific facets can be in any format your application understands, and a graphic inset file can 
contain as many application-specific facets as you want. 

When selecting application-specific facets for your graphic inset file, you might want to include an 
industry-standard facet (for example, EDIF for EDA applications) so that you can use the graphic inset file 
to share data with applications other than FrameMaker products.

Application-specific facets can be contained entirely within the graphic inset file (a local facet), or the 
graphic inset file can contain a reference to an external data file or database (a remote facet).

A local application-specific facet is contained in the graphic inset file. The formats for external and internal 
graphic insets (described in the sections “External graphic insets” on page 272 and “Internal graphic insets” 
on page 274) apply to local application-specific facets.