Commit e271c757 authored by Simon McVittie's avatar Simon McVittie

bundle-metadata: Recommend <custom>, not <metadata>

<metadata> was specific to appstream-glib, whereas <custom> is
implemented in the reference implementation libappstream.

Apertis: default avatarSimon McVittie <>
Reviewed-by: default avatarJustin Kim <>
Differential Revision:
parent dcb73acf
......@@ -431,10 +431,13 @@ separate cache files, for several reasons:
Any metadata keys and values that have not been standardized by the AppStream
project (for example audio roles that might be used to determine a bundle's
audio priority) must be represented using [](#extension-points) within the
AppStream metadata. Until an
[extension point is standardized][AppStream extension points], we recommend
using the `<metadata>` element defined and used by the [appstream-glib]
AppStream metadata. The formal [AppStream specification][AppStream] does
not provide an extension point, but the
[reference implementation][libappstream]
and [appstream-glib] both provide support for a `<custom>` element
with `<value>` children. We recommend using that element for extension
points. See the [Apertis Application Bundle Specification] for
When a store or built-in app-bundle is added, removed or changed,
the Apertis platform must update the corresponding cache file.
......@@ -569,6 +572,7 @@ requester's AppArmor label (part of the AppArmor context).
[ Icon Theme Specification]:
[iOS icon sizes]:
[Namespaces in XML]:
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment