Matthias Pfefferle

My idea: I agree with @snarfed, every plugin should handle it's properties, the best it can. The main other authority for the rendering is the theme, so I would start...

If the theme is the only authority it is even better. The syntax of the theme support was only a first shot, I would highly recommend to discuss and change...

sure, and that can be handled with more granular theme support flags.

exactly. i would use `microformats2` (because of its adoption) for both

ah, now I know why I proposed a new rendering flag... Let me think about that... perhaps we should create a section on the wiki, where we collect the different...

But that is what I meant... the main renderer is the plugin itself but it can be disabled by the theme... if a second plugin thinks it's a better renderer...

do we have cases where a plugin uses data from an other plugin?

I mentioned that in a comment above and you corrected me: > If a plugin like indie-post-kinds want to overwrite micropub functionality, it should be done individually by remove actions...

ok, got you, but we shouldn't over engineer the feature on the other hand! plugins working really good together at the moment and we only have a problem to identify...

... and we should fix that in time... at least before we start investing time in new `wp-uf2` features, because we currently only know if a plugin supports microformats2 or...