Adding RFC 5005 Paging to an Atom 1.0 Feed Without Breaking Entry Identity
A practical guide to paging an Atom 1.0 feed with RFC 5005 link relations, stable timestamp-plus-ID cursors, and validation checks that preserve entry identity across pages.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A practical guide to paging an Atom 1.0 feed with RFC 5005 link relations, stable timestamp-plus-ID cursors, and validation checks that preserve entry identity across pages.
We run a validation pipeline where a base schema (base.xsd) and a derived XSD 1.1 schema (derived.xsd) coexist. The derived schema uses xs:override to tighten a complexType with an xs:assert , and it also adds a new member to an existing substitution group. Instance documents are produced against derived.xsd, but on a failed deployment we need to re-validate
Goal is to constrain XML documents with namespaces, typed values and co-occurrence rules while keeping validation portable across common XML parsers. DTD is built into XML 1.0 and widely supported, but it lacks namespace awareness and offers only coarse typing. XSD provides typed elements and attributes, occurrence constraints and namespace support, with sch