How to specify submodule when overriding capabilities?

[ludomikula]

This is more of an ODL question but anyway.

Using lighty 21 RNC app I am trying to connect to a device that sends back crap instead of its capabilities. Thus I am trying to override it while connecting like this (using RESTCONF):

{
    "network-topology:node": [
    {
        "node-id": "mynode",
        "netconf-node-topology:netconf-node": {
            "yang-module-capabilities": {
                  "override": true,
                  "capability": [
                        ...
                        ... other module dependencies
                        ...
                        "http://tail-f.com/yang/common?revision=2023-02-21&module=tailf-common"
                  ]
            }
        }
    } 
    ]
}

However, schema creation build fails with:

unsatisfied imports: {SourceIdentifier [tailf-common@2023-02-21]=[Include[name=Unqualified{localName=tailf-meta-extensions}, revision=2017-03-08], Include[name=Unqualified{localName=tailf-cli-extensions}, revision=2021-12-17]]}

All YANG schemas are already in the schema cache folder. I have tried to add the two schemas to yang-module-capabilities but of course it fails, because both are submodules.

I've also tried to add them to non-module-capabilities, but they were not picked up probably because I did not use the correct URI format.

So my question is: what is the proper way to define a submodule when I am overriding capabilities?

[ihrasko]

Hope that helps: ODL NETCONF user guide.