Why are so many different link relations used with Atom? -
Why are so many different link relations used with Atom? -
my colleagues , working on building atom feed. paginating feed on many individual atom documents, , adding links each document allow consumers traverse entire feed.
we're wondering link relations should take indicate links next , previous documents in feed. rest in practice uses "next-archive" , "previous-archive". atompub uses "next" , "previous". "prev" accepted alias "previous".
<?xml version="1.0"> <feed xmlns="http://www.w3.org/2005/atom"> <id>urn:uuid:ff31a040-75bc-11e2-bcfd-0800200c9a66</id> <link rel="next" href="http://example.com/documents/4" /> <link rel="prev" href="http://example.com/documents/2" /> <entry>..</entry> <entry>..</entry> <entry>..</entry> </feed> is there reason take 1 set of relations on others? understood consumers. why there such diversity?
here reason numerous link relations:
well-defined relation types can registered tokens convenience and/or promote reuse other applications. specification establishes iana registry of such relation types; see section 6.2.
machines utilize them way of asserting relationships between urls.
here different utilize cases:
next-archive , previous-archive specific feed urls next , previous generic urls references
link relations
rfc5988: web linking
rfc5005: feed paging , archiving
atom publishing format , protocol
atom
Comments
Post a Comment