* Antone Roundy [EMAIL PROTECTED] [2005-10-25 06:30]:
I'm not sure I understand what you're saying. Are you saying
that one might do this if they want and alternate of a next
link?
link rel=next xml:id=foo ... /
link rel=alternate-enclosure x:alternate-of=foo ... /
No, not at all.
If
* Eric Scheid [EMAIL PROTECTED] [2005-10-25 06:35]:
There's another problem with this:
@encl:mirrors=http://www2.example.com/file.mp3
http://www3.example.com/file.mp3;
... how do you attach @title to each URI,
for example @title=Blah blah -- European Mirror.
You can’t. My
On 24 Oct 2005, at 22:59, A. Pagaltzis wrote:
* Antone Roundy [EMAIL PROTECTED] [2005-10-24 22:35]:
Interesting. Filling an attribute with a list of URIs doesn't
really appeal to me though.
+100 (me and all my co-voting cats)
How about this:
link rel=enclosure type=audio/mpeg
On 25/10/05 4:59 PM, A. Pagaltzis [EMAIL PROTECTED] wrote:
I am asking if is there a generic way for an application to
implement alternate-link processing that gives sensible behaviour
for any type of main link.
link ..
x:alternate ...
/link
couldn't get more generic than that.
read it
On 25/10/05 5:17 PM, Henry Story [EMAIL PROTECTED] wrote:
link rel=enclosure type=audio/mpeg href=http://example.com/
file.mp3 xml:id=x-file
altlink:mirror href=http://www2.example.com/file.mp3; /
altlink:mirror href=http://www3.example.com/file.mp3; /
/link
It¹s a lot more
On 25/10/05 5:06 PM, A. Pagaltzis [EMAIL PROTECTED] wrote:
Is providing a @title an option that a lot of people would use
and/or someone out there cannot do without?
In Atom 1.0 not enough deployment to say
In HTML ... *lots* of current practice of labelling mirrors with the org
name
On Oct 25, 2005, at 12:59 AM, A. Pagaltzis wrote:
I am asking if is there a generic way for an application to
implement alternate-link processing that gives sensible behaviour
for any type of main link. If an implementor has to support
alternative links explicitly for each type of main link,
Hmmm...
Mirrors:
link rel=... href=... type=...
x:mirror href=... title=... /
/link
Alternates:
link rel=... href=... type=... x:group=alternate-group /
link rel=... href=... type=... x:group=alternate-group /
All-in-one example
The x:group attribute links the two alternates into a
On Oct 25, 2005, at 11:04 AM, James M Snell wrote:
All-in-one example
The x:group attribute links the two alternates into a single
grouping; the x:mirror specifies the mirrors for each link.
nf:follow=no is my Atom Link No Follow extension that tells
clients not to automatically
James M Snell wrote:
link rel=enclosure href=http://example.com/softwarepackage.zip;
type=application/zip x:group=software-package nf:follow=no
x:mirror href=http://example2.com/softwarepackage.zip;
title=California Server /
x:mirror href=http://example3.com/softwarepackage.zip;
James Holderness wrote:
James M Snell wrote:
link rel=enclosure href=http://example.com/softwarepackage.zip;
type=application/zip x:group=software-package nf:follow=no
x:mirror href=http://example2.com/softwarepackage.zip;
title=California Server /
x:mirror
On Oct 25, 2005, at 1:16 PM, James M Snell wrote:
Also, assuming the title on the main link is supposed to describe
the download file itself, there appears to be no way to inform the
user of the mirror location of the main URI. Without a location
name of some sort, the user can't make an
I'd like to propose an extension that would allow something very much
like
icon and logo to be added to an entry, the way it currently is
allowed on a feed.
I have been publishing entries like this for over a year now [1], and
so has
James Gosling [2], and other users of BlogEd. It would
I've been wanting to do the same thing for link elements. Let's propose
a single solution:
entry
x:logo type={media-type}{url}/x:logo
x:icon type={media-type}{url}/x:icon
link
x:logo type={media-type}{url}/x:logo
x:icon type={media-type}{url}/x:icon
/link
/entry
Both elements
Oh I think I get it now. You want to specify the logo and icon of a
resource
on the other side of a link.
So generalizing the suggestion:
entry
titleAtom-Powered Robots Run Amok/title
link rel=logo href=/Image5-large.jpeg/
link rel=icon href=/Image5-small.jpeg/
Yep.. the only challenge with your example is that atom:link's should
not contain atom:link's...
Henry Story wrote:
Oh I think I get it now. You want to specify the logo and icon of a
resource
on the other side of a link.
So generalizing the suggestion:
entry
16 matches
Mail list logo
