Hello! This draft is looking nice, the idea and specification is simple and straightforward. I would like to draw the connection to other discovery approaches.
The introductory example in the draft was this one: GET /.well-known/simple-web-discovery?principal=mailto:[email protected]&service=urn:adatum.com:calendar HTTP/1.1 This returns the following response: { "locations":["http://calendars.proseware.com/calendars/joseph";] } As per my understanding - please correct me if I'm wrong - this should be semantically equivalent to the following: 1) Perform host-meta discovery for example.com, which returns an XRD with the webfinger endpoint. 2) Do webfinger for [email protected]. 3) The final XRD contains the following: <XRD> [...] <Link rel="urn:adatum.com:calendar" href="http://calendars.proseware.com/calendars/joseph"; /> [...] </XRD> Both approaches work, but SWD is a shortcut removes parsing requirements and fetching roundtrips from the client. Thoughts, anyone?! Regards, Lukas Rosenstock 2010/10/27 Mike Jones <[email protected]>: > Yaron Goland and I are submitting this Simple Web Discovery (SWD) draft > (attached and at > http://self-issued.info/docs/draft-jones-simple-web-discovery-00.html) for > consideration by the community to address this need. SWD is simple to > understand and implement, enables different permissions to be applied to > discovery of different services, and is JSON-based. I look forward to > discussing this with many of you next week at IIW. > > > > -- Mike _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
