WHAT is the KnoMe Personal Data Protocol Project?

The KnoMe Personal Data Protocol Project is currently a proposition for an industry consortium formed to create and foster an open-source, standardized personal data protocol (PDP) as a methodology for improving personal data security, privatization, development, integration, portability, governance, ownership and value.

ABOUT the name and logo

the name

KnoMe Personal Data Protocol ConsortiumThe name, KnoMe, is derived from the idea that a personal dataPersonal Data means any information relating to an identified or identifiable natural person ("data subject"); an identifiable natural person is one who can be identified, directly or indirectly, in particular... More protocol would allow people to have better control of their data, therefore having a more accurate and less inferred dataset about themselves, which would provide the ultimate consumers of the data – the brands, businesses and advertisers – with a more “human” approach to marketing. That more human approach can only come about if the data consumers can “better know” the people they want as clients or customers.

Thus, a personal data protocol would allow marketers to “Know Me” better as a person, rather than as an impersonal statistic or “targeted subject” of a marketing or advertising campaign.

the logo

The logo was created with this in mind;

  • the outer boundaries represent the the various technologies that are currently used and that will be used to unlock the the power of personal data (such as blockchainA blockchain is a continuously growing list of digital transactions (digital ledger) that occur within a nodal network, with the ledger being updated at regularly timed intervals in segments called... More), and thus represent the ability to “know” as part of this idea
  • the 3 inner grey areas are meant to represent your grey matter and the 3 different types of data that make up “you”, or the “me” as part of this idea:
    1. IPIntellectual Property ("IP"), or Personal Intellectual Property ("PIP") is a category of property that includes intangible creations of the human intellect, and primarily encompasses copyrights, patents, and trademarks. It also... More or PIPIntellectual Property ("IP"), or Personal Intellectual Property ("PIP") is a category of property that includes intangible creations of the human intellect, and primarily encompasses copyrights, patents, and trademarks. It also... More – (personal) intellectual propertyIntellectual Property ("IP"), or Personal Intellectual Property ("PIP") is a category of property that includes intangible creations of the human intellect, and primarily encompasses copyrights, patents, and trademarks. It also... More
    2. PII – personally identifiable informationPersonally Identifiable Information (PII), or Sensitive Personal information (SPI), as used in information security and privacy laws, is information that can be used on its own or with other information... More
    3. PAI – personal activity informationPersonal Activity Information (PAI) is a type of personal data that encompasses any type of personally collectable activity related information, including (but not limited to); internet activities, browsing and click... More
  • the 3 dots with the connecting lines are meant to represent the various connections that are made between
    1. data producers (you, me)
    2. data managers (platforms, brokers, agents)
    3. data consumers (advertisers, marketers, researchers)

WHY build the KnoMe standard protocol?

  • increased performance:
    lightens the load on blockchain, cloud and application network performance at large scale by reducing API integration and transaction processing requirements while reducing overall data transfer
  • ease of use:
    standardized formatting and transfer greatly simplifies; cross-platform integration, data utility and overall development processes
  • better security:
    makes personal data security much easier to develop, integrate, regulate, monitor and trust
  • greater privacy:
    makes data privacy controls much easier to develop and integrate into clear, understandable user management tools and processes
  • international compliance:
    makes regulation and enforcement much easier for companies and individuals to understand and comply with across borders
  • data democracy / sovereignty:
    allows for greater individual control, understanding, management and utility of one’s own personal data
  • clearer governance:
    makes implementing policies, procedures and standards for information assets much easier for organizations as well as for personal management and utility
  • healthier competition:
    provides lower barrier to entry, creates larger markets and incentivizes competitive advantages that benefit consumers and commercial end users alike

WHO should get involved?

many people, many perspectives:

All interested parties in the many fields of personal data; capture, storage, analysis, processing, software, privacy, management, utility, brokerage, sales, services, devices or development, whether interested in contributing time or resources, or just staying informed about the project. Join the newsletter »

developers and advisors:

Individual developers as well as strategic advisors in all fields are welcomed to contribute their expertise; admins and executive will be nominated and elected. Learn more »

donations and memberships:

Corporate sponsorship support through donations or annual membership is welcomed and appreciated. Learn more »

executive board and committees:

Nominations and elections for executive board and advisory committee positions will be made after the initial proof-of-interest period. (see “HOW” section below).

When will this happen?

introduction:

Consortium / Protocol Introduction: Monday, April 2nd, 2018
(begins proof-of-interest period)

validation:

Consortium / Protocol Validation: Tuesday, May 15th, 2018
(ends proof-of-interest period)

inception:

Consortium / Protocol Inception: Wednesday, May 16th, 2018
(see “HOW” section below)

WHERE will this be happening?

communication:

Communication channels to be agreed to by consensus of early members within 15 days of consortium inception.

development:

Development channels to be agreed to by consensus of early members within 15 days of consortium inception.

HOW – Proposed Execution

The following methodology is merely a suggestion. Further suggestions for improvements, enhancements, edits and/or changes to this strategic approach are welcomed for group consideration. We also welcome initial proposals for protocol formatting and transfer policies and models.

STAGE 1

proof-of-interest

1A: 50 member minimum in 45 days to initiate Stage 2 – consortium and protocol inception
(April 2nd to May 15th, 2018)

STAGE 2

inception and elections

2A: consortium and protocol inception upon proof-of-interest validation
2B: nominations for short-term board and committee members
2C: elect and promote short-term board and committee members

STAGE 3

suggestions

3A: suggestions for protocol formatting and transfer policies and models
3B: suggestions for developer consensus policies and mechanisms
3C: suggestions for development and communications channels

STAGE 4

consensus / acceptance

4A: primary protocol architecture and policy models
4B: development consensus mechanisms and policies
4C: development and communication channels

STAGE 5

protocol development

5A: initial proof-of-concept protocol prototype developed for validation and integration testing
5B: further protocol components proposed and consensus reached
5C: initial protocol prototype further developed and tested for performance and scaling

STAGE 6

testing and integration

6A: enroll enterprise partners for validation and integration testing
6B: validate and test scaling and performance
6C: testing completed, proven validation, enterprise acceptance

STAGE 7

release

7A: public, open-source protocol release
7B: community advocation for developer and enterprise adoption
7C: protocol reaches critical adoption threshold

STAGE 8

elections

8A: nominations for long-term board and committee members
8B: elect and promote long-term board and committee members

STAGE 9

iteration

9A: bug fixes, enhancements made to protocols
9B: further protocol components proposed and consensus reached
9C: iteration completion released