[2.0.0-beta5] Use HTTP URL isntead of a stream wrapper in JSON reference

Hello Ivan,

We have replaced most of ui-patterns:// references by plain JSON schema:

• 📌 [2.0.0-beta4] Comopnent converter: don't abuse schema referneces Active
• 📌 Replace useless ui-patterns:// references Active
• https://git.drupalcode.org/project/ui_suite_bootstrap/-/merge_requests/1...
• https://git.drupalcode.org/project/ui_suite_dsfr/-/merge_requests/55/dif...
• https://git.drupalcode.org/project/ui_suite_material/-/merge_requests/3/...

But some stay and we want them to stay.

You are proposing to use an HTTP URL instead of a PHP stream wrappers in order to be compatible with non-Drupal toolsets. This is interesting. I will update the ticket title.

We didn't do that initially for 2 reasons:

• We were expecting SDC components built outside Drupal to be used with UI Patterns 2 (that's why those references are optional), but not SDC components built with UI Patterns 2 to be used outside of Drupal
• Performance: PHP stream wrappers are way more efficient that HTTP requests

Also, this subject is broader than UIP2, because Experience Builder is also using a PHP stream wrappers: json-schema-definitions://.

What about second suggestion?
Can some schemes which

we want them to stay

be covered by schema?

I still think this question is deeper. And it is not duplication of existing issues.

this subject is broader than UIP2, because Experience Builder is also using a PHP stream wrappers

doesn't mean that this is standard ;)

Now SDC from UI Patterns not compatible with SDC from experience builder and both of them cannot be used outside of that modules.

I've added third suggestion.

doesn't mean that this is standard ;)

Indeed. Just saying it is bigger than just UIP2.

Now SDC from UI Patterns not compatible with SDC from experience builder...

Components made for UI Patterns 2 are supposed to be compatible with Experience Builder, and the other way around. Because, the JSON schema references resolution is made before the schema is read by the tool.

It is not possible to test this yet, because of this Core issue: ✨ ComponentPluginManager must implement CategorizingPluginManagerInterface Active but in theory it is all good.

... and both of them cannot be used outside of that modules.

Indeed, we will need both modules activated at the same time to be able to manage those 3 situations:

• SDC component with ui-patterns:// references -> resolved by UI Patterns 2 -> used by Experience Builder
• SDC component with ui-json-schema-definitions:// references -> resolved by Experience Builder -> used by UI Patterns 2
• SDC component with both ui-patterns:// and json-schema-definitions:// references -> resolved by UI Patterns 2 & Experience Builder &> used by UI Patterns 2 and/or Experience Builder