[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: <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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]