The developer Id problem
I believe this topic may not be entirely general, so I'll introduce it here.
Appstream 1.0 was released a few months ago, bringing several changes. While some changes were minor, the introduction of the developer tag and ID portion posed some challenges.
Consequently, I raised an issue about it two months ago, and a minor version of Appstream has since addressed these issues.
The element should have a id property, containing a unique ID to identify the respective developer. It is recommended to use a web URL,like
gnome.org
as ID to achieve a higher chance of uniqueness.
The element is designed to represent the developers or project responsible for development of the project described in the metadata.
The element should have a id property, containing a unique ID to identify the respective developer. It is recommended to use a reverse-DNS name, like org.gnome or io.github.ximion, or a Fediverse handle (like @user@example.org) as ID to achieve a higher chance of uniqueness.
Every developer element must have a name tag as child, which contains a translatable name for the respective developer. Values might be for example "The GNOME Foundation" or "The KDE Community". Hyperlinks or emails must not be used in the name; if you want to link to the developer's homepage, use the -tag instead. The name tag is translatable.
It seems that using "org.gnome" as an ID is limited to GNOME apps as mentioned here, and not every GNOME developer has a website to use for ID confirmation.
Could I use "id.gnome.UserGitlabProfileId" as the developer ID by converting "https://gitlab.gnome.org/sabriunal" to "id.gnome.sabriunal"?"
ps: My English is not as good as you think. I use ChatGPT, Grammarly, and other tools to make my texts more meaningful and less inaccurate for native readers.