[db-wg] Sponsored ASNs AccountOwner's in extended delegate file don't move with sponsor

I'm not 100% sure if this is the correct place to report/discuss this
quirk I've come across, but db-wg is the closest I have, so here it
goes.

In (what I call) the RIPE delegate file
https://ftp.ripe.net/ripe/stats/delegated-ripencc-extended-latest
Sponsored ASNs have slightly funny behaviour.

For ASNs that are sponsored, the account owner UUID is always the ASN
that sponsored the ASN first. If sponsorship is moved, the account
owner UUID does not change.

However given (as far as I understand) sponsored ASNs are PI
resources, surely they should get the same treatment as the IPv4 and
IPv6 entries (in that the PI holder has their own accountowner uuid)

What do we think?

Is this behaviour of being sticky to the original sponsor account UUID a bug?

Should sponsored ASNs have their own account UUID?

Have I completely misunderstood what any of this file means?

I ask most of this because my own system bgp.tools allows you to
quickly lookup resources by account, and for my own production ASN:

$ curl -s https://ftp.ripe.net/ripe/stats/delegated-ripencc-extended-latest
| grep 206924
ripencc|GB|asn|206924|1|20170411|allocated|b786bde2-1363-44c5-aec3-5ac65ee325e6

It shows all of the remaining ASNs that were originally registered by
the now defunct LIR:
https://bgp.tools/rir-owner/b786bde2-1363-44c5-aec3-5ac65ee325e6

Cheers
Ben Cartwright-Cox