Migrate loadFromOIM Plugin Into Core Arelle about arelle

[austinmatherne-wk]

Good call. The xBRL-XML OIM validation needs to be behind a flag that's automatically enabled if the deprecated plugin is used.

The benefit of making base XBRL support builtin is reducing our support burden caused by issues of plugin discoverability and complexity of the command line syntax. There are 100+ plugins which makes identifying required plugins less than straightforward for new users. It's also clear from our support channels that many users are confused by what plugin to use and frequently copy paste commands others have run regardless of if they make sense for their use case.

[brettkail-wk]

an empty placeholder that logs a deprecation warning

I thought the problem is that the loadFromOIM plugin also enables OIM processing/validation for xBRL-XML (xbrlxe:unsupportedFraction, etc.). If we deprecate the plugin with a warning, what would people use? I guess we could add --oim that does the same thing, but why break the existing mechanism? Is there some benefit to having the logic be "builtin" rather than loaded as a plugin?