The MyData Dictionary by MyData Operators group is licensed under Attribution-NoDerivatives 4.0 International
The MyData Dictionary is an articulation of the key data fields an individual would wish/ expect to see in a data-set/ database that is designed to empower them, and which they control. The MyData Dictionary is looking and built from the perspective of the individual, not from that of organisations.
To bring that to life. There are some 7.8 billion humans on our planet; subject to some known and very specific anomalies, all have:
A sub-set of the above will have some very common add-ons:
This list of fields does not claim or wish to be based on any one particular technology or existing standard. A first release is at this link in JSON-LD format. Clearly there will be anomalies to take into account but we have built for the simpler majority at this stage.
It is worth noting that the list of standardisable fields is only a start point; there are many hundreds of additional data attributes for which the individual is undoubtedly the best originator. We will aim to update and extend the MyData Dictionary monthly. We will maintain release numbering, this initial version is 1.0.
Multiple language support will evolve in parallel.
Any questions or suggestions for future interactions of the MyData Dictionary should be sent to: email@example.com
Note 1: As human-centric data is, by definition, life-long, a general principle applied would be that each entry would have a validity period as metadata. That is to say ‘my employer’ has a start date and potentially an end data. A related point is that, by definition, an individual can have many variants of the same field (e.g. my email address), each with a validity period, and each ideally with tags to help describe/ further delineate.
Note 2: Field definition and descriptions must be precise and carry sufficient detail and pre-work to be unambiguous; i.e. be well defined.
Note 3: at this stage, we are not dealing with derived or concatenated fields; this should be the raw data, low-level individuals fields (so ‘address lines individually rather than combined, and no derivations such as ‘age’ from ‘birth date’.