I’ll explain the motivation behind this question more.
What I want is to be able to reference other files the same way I reference Org-roam files (links, tags, more). Outlined in this question I asked before.
My basic idea: for non-Org, non-text based files, have a separate Org metadata file for each, where the UUID in metadata file is the filename of non-Org file so they can be identified. And then you can create linking of all files the same way as Org-roam files, they can have tags, they can have text referring to them, and more.
At that point, in theory, it also wouldn’t be necessary to have the files in a filesystem, but something more efficient (eg object storage). Because filesystems mainly give hierarchy, but this would be a completely non-hierarchical system. But I’m getting ahead of myself here.
I thought a good first step would be to have all non-Org files in the same folder my Org files are in, give them sane titles, and then at some future date I could extract the titles, change the filenames to UUIDs, and create corresponding Org metadata files for them.
I saw Org-attach, and thought it could be good fit.
But I misunderstood how Org-attach works. It is better to use file links for this first step. Which I am now doing (in a flat folder).
I don’t think Org-attach offers any additional functionality apart from having unique attachments per Org file (like you say) but I want to be able to share “attachments” across different Org files so that is actually what I don’t want.
Yes the way Org-attach currently works is to handle IDs by using folder structure. But I do want to have them all in the same “universe”. This is what I misunderstood.
Thank you for explaining, your explanation has really cleared it up for me.