<HTML>
<HEAD>
<TITLE>Re: Attribute Type URLs (was Re: specs Digest, Vol 40, Issue 11)</TITLE>
</HEAD>
<BODY>
<FONT FACE="Book Antiqua"><SPAN STYLE='font-size:11pt'>I too am a confused about scope. Schemas are usually designed for some purpose. And history shows that the narrower the simpler the schema the higher the likelihood of broad adoption. <BR>
<BR>
On 12/9/09 2:17 AM, "Nat Sakimura" <<a href="n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Book Antiqua"><SPAN STYLE='font-size:11pt'>David,<BR>
<BR>
PoCo seems to be only for contacts. Attributes are not just contacts but<BR>
bunch of other things as well.<BR>
<BR>
Even within the "contacts", it is missing out things like phonetics<BR>
(e.g., furigana), sort order, etc.<BR>
It does not seem to have had a lot of international exposure.<BR>
<BR>
Also, by just briefly scanning, I can point out that current proposal<BR>
does not have email classes like MMS/SMS/mobile phone etc. which are<BR>
very commonly asked attribute in Japan. Many sites refuses to provide<BR>
service without it. I bet there are other things from European point of<BR>
view etc.<BR>
<BR>
IMHO, we should define those attribute URL in an Open Forum with a clear<BR>
process and a lot of international participation.<BR>
<BR>
=nat<BR>
<BR>
(2009/12/09 11:56), David Recordon wrote:<BR>
> Hey Nat,<BR>
> I guess I'm wondering what is missing from the PoCo schema that we've<BR>
> seen the need for within the OpenID ecosystem? It seems really rich<BR>
> already.<BR>
><BR>
> I don't think that IPR is an issue around a schema, but would also be<BR>
> happy to have Facebook do an OWF agreement if it was deemed necessary.<BR>
> That said, we should focus on making sure this solves the problem of<BR>
> profile data adoption first! :)<BR>
><BR>
> --David<BR>
><BR>
> On Tue, Dec 8, 2009 at 5:21 PM, Nat Sakimura<<a href="sakimura@gmail.com">sakimura@gmail.com</a>> wrote:<BR>
> <BR>
>> Looks nice.<BR>
>> What is the process for adding more?<BR>
>> I would like to add more like phonetic field for names and addresses.<BR>
>> (In Japanese, we call them "furigana". Without them, we do not know<BR>
>> how to read in many cases nor the sort order.)<BR>
>> Also, I feel that portablecontacts.net is a bit long...<BR>
>> Is portablecontacts only for the contact data or trying to be a general<BR>
>> schema repository like axschema? Is there any consensus in which direction<BR>
>> we should head to?<BR>
>> What is the IPR implication?<BR>
>> =nat<BR>
>> On Wed, Dec 9, 2009 at 8:32 AM, Chris Messina<<a href="chris.messina@gmail.com">chris.messina@gmail.com</a>><BR>
>> wrote:<BR>
>> <BR>
>>> Done.<BR>
>>> <a href="https://portablecontacts.pbworks.com/schema">https://portablecontacts.pbworks.com/schema</a><BR>
>>><BR>
>>> On Tue, Dec 8, 2009 at 1:45 PM, Joseph Smarr<<a href="joseph@plaxo.com">joseph@plaxo.com</a>> wrote:<BR>
>>> <BR>
>>>> Looks great to me, the only thing missing is sub-fields of complex fields<BR>
>>>> like name, address, organization, and account. I would suggest using another<BR>
>>>> level of slashes, e.g.<BR>
>>>> <a href="http://portablecontacts.net/ns/1.0/address/streetAddress">http://portablecontacts.net/ns/1.0/address/streetAddress</a> and<BR>
>>>> <a href="http://portablecontacts.net/ns/1.0/name/familyName">http://portablecontacts.net/ns/1.0/name/familyName</a> and so on.<BR>
>>>><BR>
>>>> Chris-can you take a stab at adding those missing sub-fields? Then I<BR>
>>>> think we'd be good to go.<BR>
>>>><BR>
>>>> Thanks, js<BR>
>>>> ________________________________<BR>
>>>> From: Chris Messina [<a href="mailto:chris.messina@gmail.com">mailto:chris.messina@gmail.com</a>]<BR>
>>>> Sent: Sunday, December 06, 2009 6:40 PM<BR>
>>>> To: David Recordon<BR>
>>>> Cc: SitG Admin; <a href="openid-specs@lists.openid.net">openid-specs@lists.openid.net</a>; Joseph Smarr<BR>
>>>> Subject: Re: specs Digest, Vol 40, Issue 11<BR>
>>>><BR>
>>>> I've taken a crack at URLizing these attributes for use in Attribute<BR>
>>>> Exchange:<BR>
>>>> <a href="https://portablecontacts.pbworks.com/schema">https://portablecontacts.pbworks.com/schema</a><BR>
>>>> If there are comments or feedback for improving this, let me know. I'm an<BR>
>>>> XML noob.<BR>
>>>> Chris<BR>
>>>><BR>
>>>> On Sun, Dec 6, 2009 at 5:05 PM, David Recordon<<a href="recordond@gmail.com">recordond@gmail.com</a>><BR>
>>>> wrote:<BR>
>>>> <BR>
>>>>> It's missing out on the idea of having a schema which can cross<BR>
>>>>> contexts. Right now each schema – with the exception of AXSchema.org<BR>
>>>>> – has no concept of namespaces and stands alone. We've always wanted<BR>
>>>>> a schema which uses URLs to identify each element, but there haven't<BR>
>>>>> been any. Maybe Portable Contacts wants to take this on since it is<BR>
>>>>> also used by OpenSocial?<BR>
>>>>><BR>
>>>>> --David<BR>
>>>>><BR>
>>>>> On Sun, Dec 6, 2009 at 5:01 PM, Chris Messina<<a href="chris.messina@gmail.com">chris.messina@gmail.com</a>><BR>
>>>>> wrote:<BR>
>>>>> <BR>
>>>>>> I did this in June:<BR>
>>>>>><BR>
>>>>>> <a href="http://spreadsheets.google.com/pub?key=pSGbbhtwI4kN_nJ1GXeQ7Qg&output=html">http://spreadsheets.google.com/pub?key=pSGbbhtwI4kN_nJ1GXeQ7Qg&output=html</a><BR>
>>>>>> I just wish someone would actually use it!<BR>
>>>>>> Chris<BR>
>>>>>><BR>
>>>>>> On Sun, Dec 6, 2009 at 4:02 PM, SitG Admin<BR>
>>>>>> <<a href="sysadmin@shadowsinthegarden.com">sysadmin@shadowsinthegarden.com</a>><BR>
>>>>>> wrote:<BR>
>>>>>> <BR>
>>>>>>>> I'm specifically pointing out that AXSchema reinvents vcard and a<BR>
>>>>>>>> host of<BR>
>>>>>>>> other profile formats, which adds yet another burden for developers<BR>
>>>>>>>> to map<BR>
>>>>>>>> other schema, like Portable Contacts, to the AXSchema.<BR>
>>>>>>>> <BR>
>>>>>>> Could these other profile formats be mapped, on an alias, to a set of<BR>
>>>>>>> AXScheme that collectively mirror each format? As in, "vcard" alias<BR>
>>>>>>> maps to<BR>
>>>>>>> a set of AXSchema that actually just mirror 'vcard' format.<BR>
>>>>>>><BR>
>>>>>>> -Shade<BR>
>>>>>>> <BR>
>>>>>><BR>
>>>>>><BR>
>>>>>> --<BR>
>>>>>> Chris Messina<BR>
>>>>>> Open Web Advocate<BR>
>>>>>><BR>
>>>>>> Personal: <a href="http://factoryjoe.com">http://factoryjoe.com</a><BR>
>>>>>> Follow me on Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a><BR>
>>>>>><BR>
>>>>>> Citizen Agency: <a href="http://citizenagency.com">http://citizenagency.com</a><BR>
>>>>>> Diso Project: <a href="http://diso-project.org">http://diso-project.org</a><BR>
>>>>>> OpenID Foundation: <a href="http://openid.net">http://openid.net</a><BR>
>>>>>><BR>
>>>>>> This email is: [ ] shareable [X] ask first [ ] private<BR>
>>>>>><BR>
>>>>>> _______________________________________________<BR>
>>>>>> specs mailing list<BR>
>>>>>> <a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
>>>>>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
>>>>>><BR>
>>>>>><BR>
>>>>>> <BR>
>>>><BR>
>>>><BR>
>>>> --<BR>
>>>> Chris Messina<BR>
>>>> Open Web Advocate<BR>
>>>><BR>
>>>> Personal: <a href="http://factoryjoe.com">http://factoryjoe.com</a><BR>
>>>> Follow me on Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a><BR>
>>>><BR>
>>>> Citizen Agency: <a href="http://citizenagency.com">http://citizenagency.com</a><BR>
>>>> Diso Project: <a href="http://diso-project.org">http://diso-project.org</a><BR>
>>>> OpenID Foundation: <a href="http://openid.net">http://openid.net</a><BR>
>>>><BR>
>>>> This email is: [ ] shareable [X] ask first [ ] private<BR>
>>>> <BR>
>>><BR>
>>><BR>
>>> --<BR>
>>> Chris Messina<BR>
>>> Open Web Advocate<BR>
>>><BR>
>>> Personal: <a href="http://factoryjoe.com">http://factoryjoe.com</a><BR>
>>> Follow me on Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a><BR>
>>><BR>
>>> Citizen Agency: <a href="http://citizenagency.com">http://citizenagency.com</a><BR>
>>> Diso Project: <a href="http://diso-project.org">http://diso-project.org</a><BR>
>>> OpenID Foundation: <a href="http://openid.net">http://openid.net</a><BR>
>>><BR>
>>> This email is: [ ] shareable [X] ask first [ ] private<BR>
>>><BR>
>>> _______________________________________________<BR>
>>> specs mailing list<BR>
>>> <a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
>>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
>>><BR>
>>> <BR>
>><BR>
>><BR>
>> --<BR>
>> Nat Sakimura (=nat)<BR>
>> <a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><BR>
>><BR>
>> _______________________________________________<BR>
>> specs mailing list<BR>
>> <a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
>><BR>
>><BR>
>> <BR>
> _______________________________________________<BR>
> specs mailing list<BR>
> <a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
> <a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
> <BR>
<BR>
<BR>
--<BR>
Nat Sakimura (<a href="n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>)<BR>
Nomura Research Institute, Ltd.<BR>
Tel:+81-3-6274-1412 Fax:+81-3-6274-1547<BR>
<BR>
_______________________________________________<BR>
specs mailing list<BR>
<a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>