{"action":"created","issue":{"url":"https://api.github.com/repos/openname/specifications/issues/41","labels_url":"https://api.github.com/repos/openname/specifications/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/openname/specifications/issues/41/comments","events_url":"https://api.github.com/repos/openname/specifications/issues/41/events","html_url":"https://github.com/openname/specifications/issues/41","id":66161669,"number":41,"title":"Proposed renaming of Openname","user":{"login":"guylepage3","id":1711854,"avatar_url":"https://avatars.githubusercontent.com/u/1711854?v=3","gravatar_id":"","url":"https://api.github.com/users/guylepage3","html_url":"https://github.com/guylepage3","followers_url":"https://api.github.com/users/guylepage3/followers","following_url":"https://api.github.com/users/guylepage3/following{/other_user}","gists_url":"https://api.github.com/users/guylepage3/gists{/gist_id}","starred_url":"https://api.github.com/users/guylepage3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/guylepage3/subscriptions","organizations_url":"https://api.github.com/users/guylepage3/orgs","repos_url":"https://api.github.com/users/guylepage3/repos","events_url":"https://api.github.com/users/guylepage3/events{/privacy}","received_events_url":"https://api.github.com/users/guylepage3/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":120,"created_at":"2015-04-03T14:59:55Z","updated_at":"2015-04-13T23:13:51Z","closed_at":null,"body":"I'd like to propose the idea of renaming the \"openname\" protocol as I feel there is a fundamental communication issue with the naming convention. I feel there is a better way, a more descriptive way, to communicate the protocol. A clearly identifiable name that developers and users alike will grasp.\r\n\r\nA few services built on top of openname, like Onename (the company I work for), have used terms like \"digital passport\" in their communications. I actually think digital passport very aptly describes the account/profile that users get when they register as a user on the protocol.\r\n\r\nFor this reason, I'd like to explore the idea of renaming the protocol from openname to digital passport. This is a clear, descriptive name that everyone can identify with. The word \"passport\" is one of the most common forms of identification and is easy for everyone to visualize without putting any thought into it. And since the passport (identification) is a virtual form of ID it's only natural to call it a \"digital\" passport. \r\n\r\nWe have been sharing this new concept with others in the community over the past month or so in order to get other's feedback and the idea has been well received. The concepts \"passport\" and \"digital passport\" are very clear to all of the users that we've spoken to. Conversely, the concept of an \"openname\" usually takes some time to communicate. Users are very likely to ask, \"what is openname?\"\r\n\r\nFrom a marketing/communications point of view I could see users adopting, \"I have a digital passport.\" As opposed to, \"I have an openname username.\" Another point to be made is that users mostly used the word \"openname\" to refer to the \"username\". So what do you get when you register on the system? Well, you get a \"digital passport\" i.e., your profile. By using the term \"digital passport,\" it gives the user visual recognition that they can identify as a tangible object in their mind. Something one owns and holds onto for life.\r\n\r\nI hope everyone will consider this change for, what I feel is, the better of the protocol and the community.\r\n\r\nCheers, Guy"},"comment":{"url":"https://api.github.com/repos/openname/specifications/issues/comments/92530774","html_url":"https://github.com/openname/specifications/issues/41#issuecomment-92530774","issue_url":"https://api.github.com/repos/openname/specifications/issues/41","id":92530774,"user":{"login":"jbenet","id":138401,"avatar_url":"https://avatars.githubusercontent.com/u/138401?v=3","gravatar_id":"","url":"https://api.github.com/users/jbenet","html_url":"https://github.com/jbenet","followers_url":"https://api.github.com/users/jbenet/followers","following_url":"https://api.github.com/users/jbenet/following{/other_user}","gists_url":"https://api.github.com/users/jbenet/gists{/gist_id}","starred_url":"https://api.github.com/users/jbenet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbenet/subscriptions","organizations_url":"https://api.github.com/users/jbenet/orgs","repos_url":"https://api.github.com/users/jbenet/repos","events_url":"https://api.github.com/users/jbenet/events{/privacy}","received_events_url":"https://api.github.com/users/jbenet/received_events","type":"User","site_admin":false},"created_at":"2015-04-13T23:13:51Z","updated_at":"2015-04-13T23:13:51Z","body":"> Hm, what about calling the underlying protocol the \"Open Name System (ONS)\" and using passcard to refer to the identity layer that consumers see?\r\n\r\n:+1: "}}