Skip to content

Invalid Atom Feed for Tracking RFC Drafts #4566

@Saklad5

Description

@Saklad5

Describe the issue

The Atom feed offered for fetching changes to a user's tracked drafts is not valid. It fails W3C's Feed Validator in many ways, but the main problem is that it does not have actual URLs for the entries.

This manifests itself by making it impossible to open updated drafts from within feed readers such as NetNewsWire: as an example, the article URL for a recent draft revision in my feed is /doc/draft-ietf-dnssd-srp/, rather than https://datatracker.ietf.org/doc/draft-ietf-dnssd-srp/17/.

This doesn't make the feed useless, as it still serves to let me know that changes to drafts I'm interested in have occurred. It does make it considerably more annoying to use, though, as I have to manually navigate to the revised drafts to view them.


While not necessarily a bug, I also feel that the feed (or an alternative version thereof) could stand to benefit from some deduplication. Each revision of each draft generates three distinct "articles" in the Atom feed: one marking the upload of a new revision, one marking the acceptance of a new revision, and one marking the availability of a new revision. Omitting the first two events (unless they somehow fail to lead to the third) would make the Atom feed easier to browse.

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions