when splitting the schema to sub schemas the UI sends the data flat and not nested and the SWF fails the schema validation.
In these examples examples that the development was based on, the workflow itself accesses the flat data and ignores the extra layer.
In the ansible-job-template example, the main schema contains the property "ansible-job-template_ref-schema_GitHub_Repository_Info.json" of type object referencing the sub schema
Technically to satisfy the schema, the data should contain two hierarchies:
{
   ansible-job-template_ref-schema_GitHub_Repository_Info.json:

   ...
}
However the workflow itself expects flat data, it expects the structure:

it accesses .githubOrg directly as can be seen here

The solution should be that the data the UI sends should match the official schema and the examples with refs should treat the data as nested