[AppStream] Adding another component specifier for variant

[Richard Hughes]

On Mon, 23 Sep 2019 at 15:42, Matthias Klumpp <matthias at tenstral.net> wrote:
> > There are no such things as dumb questions, only lack of documentation :)
> Hehe ^^ - There might have been documentation here that I didn't find ^^

https://www.fwupd.org/lvfs/docs/metainfo is somewhat helpful
explaining what bits of AppStream we use.

> When I hear "System Update", I immediately think it's an OS update,
> not that firmware is updated (even though the operating system and
> hardware system are both "systems" in a way). Was the name chosen
> because the non-tech user doesn't know what "firmware" is, or does
> this have some deeper roots?

System is for the main board firmware, if it's just a random mouse or
keyboard it would be "Device Update"

> So, I think I do understand the problem now, and I guess we can cover
> this. Not sure if a "variant" toplevel tag is the best name, and how
> this should actually be specified. I assume the "if there are multiple
> components with the same name, the variant string should be appended
> to the component's name in round brackets" may be the besr definition.

Yes, this is fine.

> Maybe a tag name like "flavor" would make sense here

Hmm, I guess variant implies that one is more the "main model" and the
other is a specialism of the generic component (which in my case might
be true). Other words that come to mind are:

<alternative>
<choice>
<distinction>
<option>
<alternate>
<adaptation>
<choice>
<variety>
<subdivision>
<strain>

Richard