Hi

This may have come up earlier but ...

I think Wrap should have a namespace / versioning syntax.
Invariably, it will evolve, and will require version number etc. so, it
seems better to me to have one from the beginning.

e.g.,

wrap_ns=http://whatever/wrap/1.0
wrap_client_id ...


I would go further. Why is underscore '_' is used for the delimiter?
If we make it dot '.', it will improve the future compatibility with OpenID.

So, we could do something like:

openid.ns=http://whatever/wrap/1.0

openid.client_id ...


The same applies for OpenID. For an unknown reason, though OpenID has
namespace so that we write:

openid.ns= http://specs.openid.net/auth/2.0


the prefix "openid" is fixed. We should be able to change it like:

wrap.ns=http://specs.openid.net/auth/2.0


Now, the third point.

Could we not try to harmonize the variable names between the two specs?

OpenID is in use widely, so it is kind of hard to change it, so I would
request Wrap community to come closer.
For example, instead of 'callback', why cannot we use 'return_to'? So, the
Wrap Web App Profile request
will become like:

wrap.ns=http://whatever/wrap/1.0
wrap.return_to=http://example.com/callback_url
wrap.client_state=opaque_string_to_maintain_state
wrap.client_id=the_client_identifier

If we do that, rewriting openid with wrap becomes much more straightforward,
e.g.,

openid.ns=http://specs.openid.net/auth/2.x
openid.return_to=http://example.com/callback_url
openid.mode=checkid_setup
openid.client_id=client_identifier
openid.client_state=opaque_string_to_maintain_state
openid.claimed_id=http://example.com/alice
openid.identity=http://example.com/user/alice
openid.assoc_handle={some_assoc_handle}


where client_id and client_state is a new introduction to openid 2.x and
openid.mode and going forward will be "additional parameters" from the
point of view of Wrap.

IMHO, we should try to harmonize/unite instead of fragmenting.

-- 
Nat Sakimura (=nat)
http://www.sakimura.org/en/
http://twitter.com/_nat_en
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs

Reply via email to