Should the "semantic embed" become a separate plugin?

[oleq]

In v4 we have Media Embed and Semantic Media Embed as separate plugins.

In the MVP it's controlled via config.mediaEmbed.semanticDataOutput.

Concerns:

• On one hand, it could help developers migrate and understand which is which,
• It could save a couple of bytes because they're never used alongside
  • But come to think about that, they are used next to one another already in the MVP: when a preview–less embed is in the non-semantic output data, it's still expressed semantically because... there's no other way to do that. So maybe this separation does not make sense after all 🤔
    
• Extending builds with plugins in v4 was simple. In v5, it's not that easy so maybe less "plugin juggling" is better.
  • OTOH, I guess media embed will not be a part of any pre-compiled build, right? If not, developers would have to decide if they want it or not so they can just as well select semantic or non-semantic editing plugin in their build config at that stage.

[Reinmar]

Adding to the current milestone to remember to think about it.

[Reinmar]

We made a decision to keep them together. We may revisit this in the future if this feature will start to grow.