>> Which means, we need a conformance spec and a couple of test suits >> implementations. This is all good as it shows that the domain is >> maturing … Would be happy to help in any way … > > While I think that a conformance spec. and RI would be very nice for > improving interop, I would guess they would take quite a lot of work > and some agreement among implementations.
A few of us had initially been using Andy Smith's endpoint at http://oauth.term.ie/oauth/example/ as an RI, but it doesn't implement header authorization (or didn't, last time I checked), so it's not a complete solution. > It seemed to me that the original request might be more easily (if > only partially?) satisfied by creating an "implementation guidelines" > document, to which the different library implementers might submit > their "gotchas" and where we could agree "best practices" (not yet > mandatory) such as the ones suggested by JR, and help those who are > implementing their own libraries. +1 Such implementation guidelines would include specific examples that should then be included in the test suites of each respective library. > That could be done by simply creating a wiki page, and adding content. > Such guidelines would be non-binding though, of course. Perhaps this one? http://wiki.oauth.net/TestCases seth --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
