PROPOSAL schema.openid.net for AX (and other extensions)
Recordon, David
drecordon at verisign.com
Fri Apr 6 18:49:50 UTC 2007
As I've stated in the past, I have no problem with using
schema.openid.net to define attributes such as the authoritative URI for
an OpenID URL, i-name, etc.
I do have a problem with using this namespace to define an attribute
such as a First Name. I do not feel that this community should be
dealing with all of the issues such as First Name vs. Given Name, as
that is not where the expertise is, let alone it has been done in the
past. I also strongly believe that due to the number of other
definitions of these attributes, either we as a community should decide
to use one of them or work with a project such as ID Schemas to create a
set of URIs not tied to the OpenID project that solves both our needs
and the needs of others. I do not particularly care where this work
would happen and as I've said in the past, I'd be fine with someone just
buying a domain to do the work to preserve the speed for getting this
bootstrapped while not tying it to OpenID.
First Name:
- http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
- http://xmlns.com/foaf/0.1/firstName
- http://xmlns.com/foaf/0.1/givenname
- http://en.wikipedia.org/wiki/First_name
I'm sure if Paul Trevithick or Mark Whal join this conversation they'd
be able to highlight even more URI definitions of a First Name than I
was in a cursory search. This also isn't including all of the work done
for things such as LDAP, vCard, or others listed at
http://idschemas.idcommons.net/moin.cgi/List_Of_Schemas in defining what
these schema attributes are and mean.
If we want to create URLs for attributes from an existing schema (such
as LDAP or vCard) since easy URLs do not currently exist, then that is
one thing. Creating an entirely new definition of commonly used
attributes IMHO is unacceptable. We should be reusing anything that we
can, not inventing something new especially given the complexity of this
particular task.
I'm not sure what more I can do to urge this community to not reinvent
the wheel in this area.
--David
-----Original Message-----
From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On
Behalf Of Dick Hardt
Sent: Friday, April 06, 2007 10:27 AM
To: OpenID specs list
Subject: PROPOSAL schema.openid.net for AX (and other extensions)
OpenID Attribute Exchange (AX) uses URLs to uniquely identity
attributes. The URLs are resolvable to provide meta data that is both
machine and human readable.
In order to do anything useful with AX, some commons identity attributes
need to be defined.
I would propose that we start off using URLs based off of
schema.openid.net.
The Metadata model has provisions for stating that a given URL is
equivalent to another one, so that if and when a more authoritative
source is available, the schema.openid.net URLs can reference a source
that would be considered more appropriate. ie. we are not locked forever
to the schema.openid.net domain.
Is there a better domain that could be used? Likely, but as a community
we have control over openid.net and we can make this happen now so that
we can move forward with development.
Issues?
-- Dick
_______________________________________________
specs mailing list
specs at openid.net
http://openid.net/mailman/listinfo/specs
More information about the specs
mailing list