Identity namespace

justusranvier
Posts: 7
Joined: Fri Jul 11, 2014 4:07 am
os: linux

Re: Identity namespace

Post by justusranvier » Mon Aug 18, 2014 5:43 pm

John Kenney wrote:Onename are also doing some verifications of websites & social media profiles. We need a way to store these verifications (and others), along with the identity of the verifier. I think that might be best done in a new namespace.
I had some thoughts about a more-general solution for that before. This is probably relevant:

http://bitcoinism.blogspot.com/2013/09/ ... eople.html

John Kenney
Posts: 94
Joined: Sat Mar 29, 2014 2:20 pm
os: linux
Location: Sheffield, England
Contact:

Re: Identity namespace

Post by John Kenney » Tue Aug 19, 2014 2:59 pm

If you can simplify it to just attribute=value, by removing some of the less necessary types & combining them with attributes then it'll make the json much simpler. Need short simple attribute names too. Space is limited & we don't want to add too much overhead. A fairly long list of different attributes isn't a problem & I think some of the types you've listed are unnecessary.

We should add a new namespace for companies, groups & organisations too, that contains information about the organisation & links to the id of it's members. Maybe organisations could be done under id/, but I think they should be separate to people & linked, have namecoin behave more like a relational database, treat each namespace like a table that is linked to the other tables. Maybe I'm just too stuck in my old SQL ways.

I think we should link d/ to id/ (or the new org space) as well, ideally require an id/ to register a d/ & have the id/ of the owner as a required value for the d/, replacing the email value with a link to their namecoin id that has full contact details.

John Kenney
Posts: 94
Joined: Sat Mar 29, 2014 2:20 pm
os: linux
Location: Sheffield, England
Contact:

Re: Identity namespace

Post by John Kenney » Tue Aug 19, 2014 3:26 pm

So, I want to add these attributes to the current spec here... https://wiki.namecoin.info/?title=Identity

address (street)
postcode/zip
website
twitter
facebook
skype
linkedin
nationality
litecoin, primecoin, peercoin, dogecoin (possibly switch to symbols, btc, nmc, ltc, xpm, ppc, doge, etc?)
phone
org (for groups/organisations/companies they're a member of)

and a new namespace for organisations with similar attributes to id.

justusranvier
Posts: 7
Joined: Fri Jul 11, 2014 4:07 am
os: linux

Re: Identity namespace

Post by justusranvier » Tue Aug 19, 2014 3:47 pm

John Kenney wrote:I think some of the types you've listed are unnecessary.
That's fine - the spec shouldn't care at all about how many types can be used, becase applications and users should be able to add their own on the fly.

The only purpose of registering them at all is for improved coordination between applications.
John Kenney wrote:We should add a new namespace for companies, groups & organisations too, that contains information about the organisation & links to the id of it's members.
That's fine, but they should use the same schema regardless.

Actually namespaces are barely important - a trivial implementation detail. Getting the schema right in the beginning is the most important because it's the hardest thing to change in the future.

biolizard89
Posts: 1933
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Identity namespace

Post by biolizard89 » Tue Aug 19, 2014 11:47 pm

John Kenney wrote:and a new namespace for organisations with similar attributes to id.
Why would organizations need their own namespace? Is there a reason why they can't just use id/? I'm already using id/ for an organization I'm affiliated with. Organizations have identities just like people do, and as you say, the attributes stored are pretty much the same. Also, some users may not wish to publicly disclose whether they're an organization or a single person... so why make them choose?
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

Post Reply