UserPreferences

PaceTextShouldBeProvided


Abstract

Encourage interoperability and accessibility by suggesting that key textual constructs be both present and non-empty.

Note: this Pace is now a proper superset of the changes listed in PaceOptionalSummary

Status

Open

Rationale

There are existance proofs of tools that are less useful in the presence of entries without a title, or entries without either a summary or inline textual content. In fact, at least one such tool discards all such entries entirely. This fact, when viewed in isolation, would argue for making such elements mandatory.

Unfortunately, there are also existence proofs of title-only feeds, and entries for which there are no titles. Reluctantly, this leads one to conclude that while these use cases must be allowed, it would be irresponsible for the spec not to warn potential producers of such feeds that by not providing a textual fallback they may face interoperability issues.

Proposal

Make the following changes/addition to the draft-ietf-atompub-format-08 document.

section 3.1.1.1

Change:

To:

section 3.1.1.2

Change:

To:

section 3.1.1.3

Change:

To:

section 4.1.2

Delete:

Add:

Impacts

As these requirements are only SHOULDs, no feeds which are currently valid will become invalid. However, those that follow these suggestions will find that their feeds are useful to a wider audience than they would be otherwise.


CategoryProposals