Sylvain Hellegouarch wrote:
Martin Atkins a écrit :
The model we were considering was as follows:
<link rel="related" type="application/atom+xml" href="...">
<entry>
<id>tag:example.com,2009:123545</id>
<title>Some Related Entry</title>
...
</entry>
</link>
Why not using atom:content for that? The inlining you're presenting
really looks like it defeats the point of the atom:link element in the
first place.
atom:content includes the content of the entry. In my example, atom:link
points at some other entry that is related to this entry.
The purpose of atom:link here is to create a relationship between one
entry and another; a non-authoritative subset of the target entry is
included to allow consumers to avoid dereferencing the URL given in the
href attribute if it is appropriate to do so.
Again, this is achieving a similar purpose to the child elements of
atom:source, though in this case the href attribute of the containing
link serves the purpose that a child link rel="self" does in atom:source.
(As an aside, had this been in the spec originally, atom:source could in
theory have been specified as:
<link rel="source" type="application/atom+xml" href="...">
<title>Martin's Blog</title>
...
</link>
)
(Reply-to is set to be only the atom-syntax list, since this discussion
seems off-topic for atom-protocol; in retrospect, I should not have
cross-posted in the first place.)
