OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xri] What is this XRD is for?


Forgetting the whole thing about Alias for a while, you are saying
that we don't have to describe how the Subject refers to the resource?
(e.g., applications should normalize the Subject in a scheme-dependent
fashion)? Of course applications are free to define further
equivalence conditions.

On Fri, Feb 5, 2010 at 08:11, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>
>
>> -----Original Message-----
>> From: Scott Cantor [mailto:cantor.2@osu.edu]
>> Sent: Friday, February 05, 2010 6:03 AM
>> To: Eran Hammer-Lahav; 'Breno de Medeiros'; xri@lists.oasis-open.org
>> Subject: RE: [xri] What is this XRD is for?
>>
>> Eran Hammer-Lahav wrote on 2010-02-05:
>> > Didn't say it is NOT, just that this is not a foregone conclusion. The
>> > XRD might be about the Aliases too, but that is *application* specific
>> > (where the rat hole of resource vs representation lives).
>>
>> Well, you did actually say "not", which is why I was confused, but I'll leave it
>> alone. I'm not intending to debate URI theory, but if you make explicit
>> statements in the spec about the relationship of the XRD content and the
>> subject URI in terms of words like "resource", it's somewhat unavoidable.
>>
>> I think my concern is that you will find that nobody who isn't familiar with that
>> rathole is going to end up treating the Alias in an application-specific manner.
>> They'll do exactly what you'd expect and treat it as "the same thing" for
>> application purposes, and if that's ok, we're fine.
>
> That's ok. And when conflicts arise because not all URI are created equal and not all resolve in the same way, I will simply point that at the XRD level, XRD never said they must be and that the subject is the focus of the XRD and that it is the application's job to resolve how to define the relationship between the alias and the descriptor.
>
> EHL
>



-- 
--Breno

+1 (650) 214-1007 desk
+1 (408) 212-0135 (Grand Central)
MTV-41-3 : 383-A
PST (GMT-8) / PDT(GMT-7)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]