Commit 3675e68d authored by Matthias Klumpp's avatar Matthias Klumpp
Browse files

spec: Clarify that ISO 8601 dates in AppStream require the complete date

This resolves #245
parent 5abfc83a
...@@ -648,7 +648,7 @@ ...@@ -648,7 +648,7 @@
<term>date</term> <term>date</term>
<listitem> <listitem>
<para> <para>
The <ulink url="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</ulink> date of when this software was released. The <ulink url="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</ulink> complete date of when this software was released.
</para> </para>
<para> <para>
One of the <literal>unix-timestamp</literal> or <literal>date</literal> fields must be present. One of the <literal>unix-timestamp</literal> or <literal>date</literal> fields must be present.
......
...@@ -414,14 +414,14 @@ ...@@ -414,14 +414,14 @@
<para> <para>
A <literal>release</literal> tag can have the properties <literal>version</literal>, <literal>date</literal> and <literal>timestamp</literal>. A <literal>release</literal> tag can have the properties <literal>version</literal>, <literal>date</literal> and <literal>timestamp</literal>.
The <literal>date</literal> property can have any time in <ulink url="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</ulink> format as its value and The <literal>date</literal> property can have any time in <ulink url="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</ulink> format as its value and
should be present for every release. should be present for every release. At least day-level granularity is required, which means that the ISO 8601 string must contain at least a full date (e.g. 2019-08-12).
The <literal>timestamp</literal> tag contains the release time in the form of a UNIX epoch. This tag should not be used in metainfo files in newly The <literal>timestamp</literal> tag contains the release time in the form of a UNIX epoch. This tag should not be used in metainfo files in newly
written metadata, but will still be parsed in case it is present. The <literal>timestamp</literal> property is mainly used in generated distro-metadata. written metadata, but will still be parsed in case it is present. The <literal>timestamp</literal> property is mainly used in generated distro-metadata.
In case both release-time tags are present, the <literal>timestamp</literal> tag will take precedence over <literal>date</literal>. In case both release-time tags are present, the <literal>timestamp</literal> tag will take precedence over <literal>date</literal>.
</para> </para>
<para> <para>
A <literal>release</literal> tag may also have a <literal>date_eol</literal> property that denotes the date when the release stops to receive A <literal>release</literal> tag may also have a <literal>date_eol</literal> property that denotes the date when the release stops to receive
support from the software developers (end-of-life). Its value can be any time in <ulink url="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</ulink>. support from the software developers (end-of-life). Its value can be any complete date or time in <ulink url="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</ulink>.
</para> </para>
<para> <para>
Optionally, the <code>&lt;release/&gt;</code> tag may also have an <literal>urgency</literal> property, having one of the following values: Optionally, the <code>&lt;release/&gt;</code> tag may also have an <literal>urgency</literal> property, having one of the following values:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment