A basic question to avoid xmp-sidecars

[sinus]

Hey folks, sorry, this is a kind of a basic question, I think, hence I am bit cautious. 
For customize file formats I use the IMatch defaults since ages (and also the Metadata working group compliance).
Means in my case: 
IMatch creates sidecars for my nefs, and embedds the Metadata into my jpgs.
Fine.

I work also with Blender and there I have a lot of the format stl. And I do not use metadata for this format.
Now I want to have them also in IMatch, not exclude them from IMatch. 

Now my question:
Is it a good idea let IMatch not create xmp-sidecars for stl-files?
And if yes, what is the best way to do so? 
I have read in the helpfile, but to be honest, I have not touched this since years and hence I am not more sure.

I have included the stl-file-extension (for 3D) a long time ago, and I think, IMatch does not natively support it (at least I did not find it).

[Mario]

IMatch creates XMP in sidecar files to persist metadata outside the IMatch database. For RAW files and for all other file formats that don't support embedded XMP metadata.

For me it makes sense to use metadata with basically any file format, including Blender files. A description, some keywords to aid searching, a rating and label maybe is always helpful.

And when you write back, IMatch stores this information in standard-compliant XMP sidecar files. There is no disadvantage for having XMP files in the same folder as the corresponding image / video / audio or other file. XMP files are small. And they are an independent backup for all the metadata you have created.

[sinus]

Thanks, Mario 
in this case I let it be, like it is. 
Your arguments makes sense.