UserPreferences

PaceMultipleIssued


Abstract

This pace tries to define the semantics of atom:issued, and defines a method for re-issance of an entry.

Status

Open.

Conflicting paces

This pace is in conflict with the following paces:

This pace is a simpler version of:

This pace is a more advanced version of:

Rationale

What atom:issued actually means, and what date goes into it is of high debate on atom-syntax. This pace tries to define an objective and formal meaning to it, as well as the semantics and mechanism for re-issuing an entry.

Proposal

Replace section 4.13.7 with:

4.13.7 "atom:issued" Element

The "atom:issued" element is a Date construct that indicates the date of formal issuance (e.g., publication) of the resource. atom:entry MUST contain an atom:issued element and MAY contain more than one.

The content of atom:issued MUST contain a time zone, if available.

atom:issued SHOULD be provided by the tool issuing the resource. It SHOULD NOT be provided by the author for other resons than publishing the resource in the future. For this reason, the entry MUST be witheld from publishing until the issue time, and then issued to its intended audience.

atom:issued MAY have a future date within a publishing process (e.g. if the resources in the feed is being reviewed by an editor), but MUST have a date less than or equal to "now" when published.

atom:issued MAY have a date from the past if the resource actually was issued in the past. Example:

If an atom:entry is re-issued, atom:issued MUST NOT be altered. Instead, a new atom:issued element MUST be appended to the atom:entry element, to provide the date of the re-issuance as well as the initial issuance. The order of the atom:issued elements is of no significance. The oldest of the issued dates are to be considered the first, and the newest to be the last.

Impacts

This pace may impact the way tools handle the issued date.

Notes


CategoryProposals