On 8-Apr-07, at 1:01 PM, Mark Wahl wrote: > FYI if you are carrying attribuets in OpenID AX that are equivalent to > LDAP attributes with attribute types being standardized in the > IETF, then > you could use our LDAP schema definition metadata. We have > resolvable > HTTP URIs for each of the widely-deployed attributes, such as > givenName. > > For each LDAP attribute type definition in those RFCs, the schemat > tool generated an OWL DatatypeProperty and a OWL Class. > > The URI of the OWL class generated from an LDAP attribute type > is currently of the form > > http://www.ldap.com/1/schema/rfcNNNN.owl#AttributeType_OID
That's not a bad list, although there are some attributes missing that I would have expected to see given all the sources used to compile the list. Birthday? State/Province, Country? Not to mention I clicked through about 4 different URLs and still couldn't figure out what the data for a particular attribute was supposed to look like :) .. everything is a owl#Class type? (I'm pretty new to this RDF stuff so maybe I just haven't learned to read the docs properly). The main difference I'm seeing is that AX metadata uses rdf:Description while you used owl:DatatypeProperty and owl:Class? And the rdf:type values for AX metadata use the w3 XMLSchema types... If some ID attributes were added to the elements, it would be easier to navigate the document, as the fragment would resolve to something useful in a browser. Would you consider filling in the rdfs:comment elements and adding openid:example elements? I think the elements unique to OpenID AX had been included on the idschemas wiki a while ago, so at least there was some work started there. -Rowan _______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs
