validation fails on developer IDs with uppercase
The following:
<developer id="io.github.Uppercase">
<name>Hello</name>
</developer>
produces a warning:
$ appstreamcli validate --explain app.metainfo.xml
W: app.drey.Test:6: developer-id-invalid io.github.Uppercase
The developer-ID is invalid. It should be an rDNS string identifying the developer, or a
Fediverse handle. It must also only contain lowercase ASCII letters, numbers and punctuation.
The docs at https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-developer do not mention any requirement on lowercase vs uppercase.
Either the docs are missing info or the linter is not doing the right thing.
Since using the app id as developer id will be a common use case - it would be pragmatic to allow upper case letters in the developer id.
See also https://matrix.to/#/!jcUJARuitCjSJLKnYP:gnome.org/$8oPWRH_nrNHPCDwQR4EaYYBU25ficM85cybtJ1n1_Y0
Note that @[email protected] would also fail. Can a Fediverse handle be case sensitive? If so it makes sense to allow uppercase in those.
I agree, sorry for the delayed response! (I am very preoccupied at the moment) We could make this an info hint, like with component-IDs, but TBH I think the better thing to do is to just drop the case check, especially since it does not follow the spec in that regard.
I faintly remember that we initially wanted to allow only lowercase, then dropped that, and it looks like I did not adjust the check (it was supposed to test only the domain part of the rDNS for case, not the whole string...). Maybe I will get to it today, otherwise some time during the week :-)
Hello, is there any update to this? We are using the app id in some apps like e.g. Bustle
<developer id="org.freedesktop.Bustle">
<name>The Bustle developers</name>
</developer>
Since the GNOME runtime now has a new enough appstream the app fails at CI.