Henry Story wrote:
Just re-reading your mail I think you make a good point that perhaps
translation is the wrong word to use. We would like something more
abstract such as otherLanguageVersion. This made me think that the
word we want is alternate. And then looking at the spec again I
found the
--On December 23, 2005 11:31:22 PM +0100 Henry Story [EMAIL PROTECTED] wrote:
So you can't have a link pointing from an entry to an id, without losing some
very important information. We need something more specific. We need a link
pointing from A to C as shown by the blue line.
Some
David Powell wrote:
link rel=alternate
type=application/atom+xml
hreflang=fr
x:id=french_entry_id /
What do you think?
I assume that there is an href missing from that?
Actually no. At least not necessarily. That was to indicate the special case
where the link was pointing to an entry
FYI...
Original Message
Subject: Re: todo: add language encoding information
Date: Thu, 22 Dec 2005 19:03:25 +0100
From: Henry Story [EMAIL PROTECTED]
To: James M Snell [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Hi James, you forgot to send this to the Atom syntax list,
* James M Snell [EMAIL PROTECTED] [2005-12-22 19:30]:
To indicate that the feeds were translations of one another, a
new translation link rel could be established on the feed
level
feed xml:lang=de
...
link rel=translation
hreflang=fr
A. Pagaltzis wrote:
* James M Snell [EMAIL PROTECTED] [2005-12-22 19:30]:
To indicate that the feeds were translations of one another, a
new translation link rel could be established on the feed
level
Is that even necessary? Wouldn’t @rel='self' already work here?
I would have thought
Yes. That is one solution. But what we are looking for is how one can
state that two entries in the same feed are translations of one another.
Henry
On 22 Dec 2005, at 20:52, James M Snell wrote:
Hmmm.. interesting thought, hadn't considered that.
rel=self should always point to *this*
* James Holderness [EMAIL PROTECTED] [2005-12-22 21:00]:
I would have thought @rel='alternate' (an alternate version of
the resource described by the containing element) slightly more
appropriate than @rel='self' (a resource equivalent to the
containing element). There's also the restriction
In that case, the only viable solution is an extension element. This is
similar to the Thread Extension use case in which replies may appear
within the same feed as the original.
Here's how I would do it:
1. Introduce a new translation element.
translation id=id_of_resource /
2.
Hmmm.. interesting thought, hadn't considered that.
rel=self should always point to *this* document, and never to some
other document, but if the document referenced is the same document just
in a different language, then it is possible? Good thinking but I'm not
sure if it's legal
10 matches
Mail list logo
