On 7/31/07, Eric Scheid <[EMAIL PROTECTED]> wrote: > Now, as to your scenario: > > > Bob wrote an article, and published it as an Atom document. > > Alice published a translation of the article, and Bob wish to include > > a link in his Atom document to point to Alice's translation. > > Bob would put his name into the entry he authored, but not because he wrote > the original article. If a third party (Charles) were to write an entry > linking to Bob's article or Alice's translation, then Charles would be the > author.
I agree. Charles wrote the entry, thus he is the entry's author. But my concern is, can we safely link to any document using atom:link (regardless of @rel), just as we can with html:a and html:link, thus are "normal links" [1]. -OR- @rel may imply certain meaning on relationship (e.g. ownership) between documents that authors/implementers must be careful about. If yes, it seems necessary to make it clear. and atom:[EMAIL PROTECTED], should we treat it as normal / embedded [2] ? [1] http://www.w3.org/DesignIssues/LinkLaw.html#Normal [2] http://www.w3.org/DesignIssues/LinkLaw.html#Embedded > [..] However, rel="related" doesn't > really communicate the relationship between the reference and the referent, > so I'm tempted to propose a new relationship. rel="referent" seems > appropriate. A new precise relation type is fine for new systems. But existing feed readers prefer the first alternate atom:link in feed entry. If service implementers need to compromise, at least they know it's okay to do so. Which is why, I think, the question above is important. Thanks, -- Teo Hui Ming
