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] RE: Linked XRD Processing Rules

Okay, in this case, I propose we abandon both #replace and #see-also

Webfinger and host meta can define how to find other XRDs via
extensions, if and when needed.

On Fri, Sep 18, 2009 at 10:08 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>> - Is there a need for general purpose processing rules to link one XRD
>> to other XRDs?
> I am not sure. It seems like the only real use case we have is host-meta, which bring back our discussion on the 'match' attribute. There are obviously going to be protocols with a need for this, but do we have actual examples other than the current need to delegate host-meta?
> The need for #replace is completely trust related, because without trust (or with the use of HTTPS), HTTP 3xx covers this (and at the moment HTTP is the only transport we have use cases for).
> If host-meta solved its delegation needs some other way, neither will be needed.
> So with the information I have today, I would say no.
>> - If yes, is a #replace directive enough, or do we need #include?
>> - If yes to #include, do we need it today or can we defer it to another
>> spec with more advanced processing rules protocols can use?
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


+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]