* 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?
>
>
>
No, not at all.
> If that's what you mean, then sure, the code for that would be
> the same as f
* 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".
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:
http://example.com/
file.mp3" xml:id="
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.
couldn't get more generic than that.
read it as: here is a link (
On 25/10/05 5:17 PM, "Henry Story" <[EMAIL PROTECTED]> wrote:
>>> http://example.com/
>>> file.mp3" xml:id="x-file">
>>> http://www2.example.com/file.mp3"; />
>>> http://www3.example.com/file.mp3"; />
>>>
>>>
>>
>> It¹s a lot more verbose and you have to fiddle with nesting.
>>
>> Wha
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
na
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, whe
Hmmm...
Mirrors:
Alternates:
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
download the enc
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 downlo
James M Snell wrote:
http://example.com/softwarepackage.zip";
type="application/zip" x:group="software-package" nf:follow="no">
http://example2.com/softwarepackage.zip";
title="California Server" />
http://example3.com/softwarepackage.zip"; title="European
Server" />
http://example.com/sof
James Holderness wrote:
James M Snell wrote:
http://example.com/softwarepackage.zip";
type="application/zip" x:group="software-package" nf:follow="no">
http://example2.com/softwarepackage.zip";
title="California Server" />
http://example3.com/softwarepackage.zip";
title="European Server"
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 in
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 be
I've been wanting to do the same thing for link elements. Let's propose
a single solution:
{url}
{url}
{url}
{url}
Both elements should follow the exact same rules as the existing
atom:logo and atom:icon elements.
- James
Henry Story wrote:
I'd like to propose an extensi
On 25 Oct 2005, at 22:08, James M Snell wrote:
I've been wanting to do the same thing for link elements.
Nice :-)
Let's propose a single solution:
{url}
{url}
{url}
{url}
Is the above a single solution, or two solutions? I can't quite tell the
difference.
Would they (it?
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:
Atom-Powered Robots Run Amok
http://example.org/2003/12/13/atom03";>
http://example.org/2003/12/13/
atom0
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:
Atom-Powered Robots Ru
Any chance this specification could be extended to contain meta data
about the replies? Specifically, how many replies that may exist for a
given entry?
I would love a mechanism to be able to recreate:
--- cut here ---
POST TITLE
Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
Donec
+1 to James' +1 of Eric's -1.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of James M Snell
> Sent: Monday, October 24, 2005 8:13 PM
> To: Eric Scheid
> Cc: Atom Syntax
> Subject: Re: Sponsored Links and other link extensions
>
>
> Eric Scheid w
This is a topic that has come up recently in conversations here at Six
Apart that I thought I would share with a broader community to hear your
feedback and thoughts on the subject:
We see a value in representing the following attributes about an author:
* their Display Name (e.g. "Byrne Reese")
On Oct 25, 2005, at 5:02 PM, Byrne Reese wrote:
The above is accomodated by the current spec, but the following is
something we would also like to represent somehow in a standard way:
* their authenticated identity (e.g. "breese") and the authenticating
authority (e.g. "LiveJournal," "TypeKey,
On 26/10/05 4:18 AM, "Antone Roundy" <[EMAIL PROTECTED]> wrote:
> The only thing I would change is the name of x:mirror/@title to make
> it clear that it isn't intended(?) to replace the parent link's
> @title. My current favorite name is "label".
+1
Hmm.. not too sure. It's entirely possible, of course, but I'm not sure
that's it's worthwhile. The slash RSS 1.0 module already has an element
that can be used for this
(http://web.resource.org/rss/1.0/modules/slash/).
Byrne Reese wrote:
Any chance this specification could be extended
23 matches
Mail list logo