logo       

Re: PaceURINomenclature and PaceOnlyMemberURI: msg#00607

network.syndication.atom.protocol

Subject: Re: PaceURINomenclature and PaceOnlyMemberURI


Thanks for the clarification. Now I understand why self is ambiguous.

-Elias

Joe Gregorio wrote:
> On 8/18/06, Elias Torres <elias-teabWVY4yyH1P9xLtpHBDw@xxxxxxxxxxxxxxxx>
> wrote:
>>
>> I meant from Atom Syntax:
>>
>> """The value "self" signifies that the IRI in the value of the href
>> attribute identifies a resource equivalent to the containing element."""
>>
>> Joe has said that self is ambiguous according to syntax I'd assume and
>> Asbjørn mentioned the following today:
>>
>> """So, if the <link> element with a @rel attribute whose value is 'self'
>> shows up as a child node of <atom:entry>, its @href attribute points to
>> the URI where you can find this exact Atom Entry Document. Thus, 'self'
>> is a perfect link relation to use for "public" GET operations, while
>> 'edit' is the one defined and used by APP."""
>>
>> Is that understanding of self incorrect then? I'm curious. If it's
>> incorrect and ambiguous, are there any proper and useful scenarios to
>> use 'self'?
>
> It is incorrect, but that's mostly because of a small bug in the
> Atom Syndication Format. You see, both an Atom Feed and
> an Atom Entry have the same media type, application/atom+xml.
> So I have no idea if
>
> <link rel="self" type="application/atom+xml" href=""/>
>
> points to an Entry or a Feed. Now for a single Entry I have a
> perfectly good use case for that URI to point to a Feed: The
> feed represents the entry and all of the entries in that
> feed are comments.
>
> -joe
>




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise