the profile module and it's data

[Ken Eucker]

So I am adding a new widget to the seven20 library that will allow remoteStorage devs to display a users profile as well as allow the user to edit their profile information. 

This requires building a profile module and coming up with the data that it should contain. Here is my idea of what profile information is:

Name

Gender pronoun preferred

Birth date

Email 

Location

Phone

Website

Blurb

Anything else you think should go into the model?

[Melvin Carvalho]

public key

--
 
 
 

[Michiel de Jong]

profile picture, very important.

> --
>
>
>

[Ken Eucker]

Woops, yes. Picture is an important one.

Public key?

[Melvin Carvalho]

On 6 October 2012 21:14, Ken Eucker <epi...@gmail.com> wrote:

Woops, yes. Picture is an important one.

Public key?

Are these mandatory fields, optional fields, or the only permissible fields?

I would be interested in storing my public key in a profile.
 

--
 
 
 

[Jan-Christoph Borchardt]

Regarding gender, »preferred pronoun« is a bit formal. And a gender
input is always very weird anyway, but maybe it’s just me. For that
also read http://www.sarahmei.com/blog/2010/11/26/disalienation/ (why
»gender« is an input field in Diaspora)

Anyway, I’d say either there’s an input field for gender, but I’d say
rather nothing at all because it makes everything that uses it feel
like a dating site.

> --
>
>
>

[Jan-Christoph Borchardt]

And btw, shouldn’t it just use the vCard standard attributes?

[Melvin Carvalho]

On 6 October 2012 21:25, Jan-Christoph Borchardt <h...@jancborchardt.net> wrote:

And btw, shouldn’t it just use the vCard standard attributes?

Yes.  Vcard, PoCo, PIM or FOAF.  Unless you want to roll your own format. 
 

--

[Ken Eucker]

I think these would be the fields that the module plans to work with. Just trying to come up with the fields that devs can hope to see from gaining access to this module. But I can easily make the widget able to add more information to the profile as users deem useful.

So the list is:

Name

Picture

Gender pronoun preferred

Birth date

Email 

Location

Phone

Website

Blurb

Public key

[Melvin Carvalho]

On 6 October 2012 21:27, Ken Eucker <epi...@gmail.com> wrote:

I think these would be the fields that the module plans to work with. Just trying to come up with the fields that devs can hope to see from gaining access to this module. But I can easily make the widget able to add more information to the profile as users deem useful.

So the list is:

Name

Picture

Gender pronoun preferred

Birth date

Email 

Location

Phone

Website

Blurb

Public key

It doesnt matter too much if you are going to store this in JSON LD because in the @context you can map any field to any definition, e.g. FOAF PoCo VCard PIM or your own. 

But if you use the same terms as other vocabs it would probably make things cleaner and more readable.
 

--
 
 
 

[Jan-Christoph Borchardt]

Let’s cut gender please. It’s either obvious from the name or picture,
or you don’t want people to know or you don’t give a shit. It’s just
weird. We can still add it once dating sites start using
remotestorage.

Also, address and location should probably be different ones, where
address is more permanent (post address) and location is flexible (for
geolocation).

> --
>
>
>

[Melvin Carvalho]

On 6 October 2012 21:31, Melvin Carvalho <melvinc...@gmail.com> wrote:

On 6 October 2012 21:27, Ken Eucker <epi...@gmail.com> wrote:

I think these would be the fields that the module plans to work with. Just trying to come up with the fields that devs can hope to see from gaining access to this module. But I can easily make the widget able to add more information to the profile as users deem useful.

So the list is:

Name

Picture

Gender pronoun preferred

Birth date

Email 

Location

Phone

Website

Blurb

Public key

It doesnt matter too much if you are going to store this in JSON LD because in the @context you can map any field to any definition, e.g. FOAF PoCo VCard PIM or your own. 

But if you use the same terms as other vocabs it would probably make things cleaner and more readable.

I forgot to mention OpenSocial have a ton of fields for this too.  But they are less well defined.
 

[Ken Eucker]

Originally, Niklas and I talked about going with vCard and I wrote the widget to have a vCard importer. I think it would be important to translate existing formats out there, but I also wanted to make the profile module be simple and easy. vCard is a bit more complex than I think this module needs to be. I will look into the other formats you mentioned.

I think making the Gender field a text field is important, as people will want to identify as many different things. And I think some sites, like social sites, tend to use these. That's why I put it in there, but I can take it out for now. I actually looked to model the same profile information that diaspora included. 

I am hoping to come up with a consensus that we all agree on and then coding towards that.

[Melvin Carvalho]

On 6 October 2012 21:35, Melvin Carvalho <melvinc...@gmail.com> wrote:

On 6 October 2012 21:31, Melvin Carvalho <melvinc...@gmail.com> wrote:

On 6 October 2012 21:27, Ken Eucker <epi...@gmail.com> wrote:

I think these would be the fields that the module plans to work with. Just trying to come up with the fields that devs can hope to see from gaining access to this module. But I can easily make the widget able to add more information to the profile as users deem useful.

So the list is:

Name

Picture

Gender pronoun preferred

Birth date

Email 

Location

Phone

Website

Blurb

Public key

It doesnt matter too much if you are going to store this in JSON LD because in the @context you can map any field to any definition, e.g. FOAF PoCo VCard PIM or your own. 

But if you use the same terms as other vocabs it would probably make things cleaner and more readable.

I forgot to mention OpenSocial have a ton of fields for this too.  But they are less well defined.

I think opensocial uses these (im not a huge fan of their data model, just posting for reference)

Person
Person:  aboutMe;
Person:  accounts;
Person:  activities;
Person:  addresses;
Person:  age;
Person:  birthday;
Person:  bodyType;
Person:  books;
Person:  cars;
Person:  children;
Person:  currentLocation;
Person:  displayName;
Person:  drinker;
Person:  emails;
Person:  ethnicity;
Person:  fashion;
Person:  food;
Person:  gender;
 

[Melvin Carvalho]

On 6 October 2012 21:39, Ken Eucker <epi...@gmail.com> wrote:

Originally, Niklas and I talked about going with vCard and I wrote the widget to have a vCard importer. I think it would be important to translate existing formats out there, but I also wanted to make the profile module be simple and easy. vCard is a bit more complex than I think this module needs to be. I will look into the other formats you mentioned.

I think making the Gender field a text field is important, as people will want to identify as many different things. And I think some sites, like social sites, tend to use these. That's why I put it in there, but I can take it out for now. I actually looked to model the same profile information that diaspora included. 

I am hoping to come up with a consensus that we all agree on and then coding towards that.

It's tricky there's lots of different views on this ... here's some notes we made in the social web XG some time back.  General consensus was:  PoCo to align to Vcard.  FOAF to align to PoCo.  OpenSocial to be a super set of everything with extra fields.

https://docs.google.com/spreadsheet/ccc?key=0AqtcXb4fZGyCdEtNSVJ0LXdvT3dBTHllOTZEbmZFaFE#gid=0
 

On Saturday, October 6, 2012 11:42:25 AM UTC-7, Ken Eucker wrote:

So I am adding a new widget to the seven20 library that will allow remoteStorage devs to display a users profile as well as allow the user to edit their profile information. 

This requires building a profile module and coming up with the data that it should contain. Here is my idea of what profile information is:

Name

Gender pronoun preferred

Birth date

Email 

Location

Phone

Website

Blurb

Anything else you think should go into the model?

--
 
 
 

[Melvin Carvalho]

On 6 October 2012 20:42, Ken Eucker <epi...@gmail.com> wrote:

The main foaf fields are:

name
title
depiction (depicts)
based_near
age
Organization
nick
mbox
homepage
weblog

Less common fields are

openid
jabberID
mbox_sha1sum
interest
workplaceHomepage
workInfoHomepage
schoolHomepage
publications
currentProject
pastProject
account (eg twitter etc)
logo
 

--
 
 
 

[Melvin Carvalho]

Full list:

Properties: | account | accountName | accountServiceHomepage | age | aimChatID | based_near | birthday | currentProject | depiction | depicts | dnaChecksum | familyName | family_name | firstName | focus | fundedBy | geekcode | gender | givenName | givenname | holdsAccount | homepage | icqChatID | img | interest | isPrimaryTopicOf | jabberID | knows | lastName | logo | made | maker | mbox | mbox_sha1sum | member | membershipClass | msnChatID | myersBriggs | name | nick | openid | page | pastProject | phone | plan | primaryTopic | publications | schoolHomepage | sha1 | skypeID | status | surname | theme | thumbnail | tipjar | title | topic | topic_interest | weblog | workInfoHomepage | workplaceHomepage | yahooChatID |

Sorry for so many posts, hope this helps!
 

 

--
 
 
 

[Ken Eucker]

The main foaf fields are:

name
title
depiction (depicts)
based_near
age
Organization
nick
mbox
homepage
weblog

Less common fields are

openid
jabberID
mbox_sha1sum
interest
workplaceHomepage
workInfoHomepage
schoolHomepage
publications
currentProject
pastProject
account (eg twitter etc)
logo

I like the simplicity of the main foaf fields. I would like to keep it more simple than some of these longer lists. 

 

[Melvin Carvalho]

Sure, pick what you feel is best, or mix and match.  People have been debating this topic for years! :)
 

 

--