Re: [xri] <uri>element in <link> of XRD

[Nat Sakimura <n-sakimura@nri.co.jp>]

Hi Brian, what do you think.

I think it is almost imperative to have <Subject> at the link level
for the trust purpose.

=nat

--------------------------------------------------
From: "Eran Hammer-Lahav" <eran@hueniverse.com>
Sent: Friday, January 30, 2009 2:36 PM
To: "Sakimura Nat" <n-sakimura@nri.co.jp>; "XRI TC" 
<xri@lists.oasis-open.org>
Subject: RE: [xri] <uri>element in <link> of XRD

> It is (a) which does not guarantee that the descriptor of the resource 
> identified by the <URI> will have the value of the <URI> as its subject. I 
> know Brian has a similar requirement for his trust proposal.
>
> Since this seems like a trust-related requirement, I will wait until we 
> have a more complete trust solution to comment on that.
>
> We still have an open question if the <ResourceType> element at the <XRD> 
> level should be called ResourceType or Type. At the <Link> level we agreed 
> on ResourceType.
>
> EHL
>
>> -----Original Message-----
>> From: Nat Sakimura [mailto:n-sakimura@nri.co.jp]
>> Sent: Thursday, January 29, 2009 7:28 PM
>> To: XRI TC
>> Subject: [xri] <uri>element in <link> of XRD
>>
>> Accroding to today's dicussion, it looks like XRD would look something
>> like:
>>
>> <XRD sig="URI of the signature file"
>> sigalg="http://www.w3.org/2000/09/xmldsig#rsa-sha1"; certuri="pem file
>> location">
>>   <Subject>Unique_identifier</Subject>
>>   <SignerID>Unique_identifier</SignerID>
>>   <ResourceType>...</ResourceType>
>>   <link>
>>     <rel>My OpenID Provider</rel>
>>     <localid>mylocalid</localid>
>>
>> <ResourceType>http://specs.openid.net/auth/2.0/signon</ResourceType>
>>     <ResourceType>http://specs.openid.net/cx/1.0</ResourceType>
>>     <URI>https://example.com/server</URI>
>>   </link>
>>   <link>
>>     <rel>my age verification service</rel>
>>     <localid>...</localid>
>>     <ProviderID>https://sts.equifax.com/#20081203000000</ProviderID>
>>     <ResourceType>http://schemas.informationcard.net/@ics/age-18-or-
>> over/2008-11</ResourceType>
>>     <URI>https://sts.equifax.com/</URI>
>>   </link>
>> </XRD>
>>
>>
>> My question is
>>
>> (1) Does <URI> points to
>>       (a) Service Endpoint
>>       (b) XRD address of the Service
>>       (c) <Subject> in the XRD of the Service.
>>
>> If it is not (c), then it would be really nice to have
>> something like <Subject> at the <link> level so that
>> we can potentially test that the destination really is the
>> intended destination.
>>
>> =nat
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>