A thought came to mind after watching Meta data embedded in some data content;
Data contents are varied – such as:
- Common known files (such as);
- EXE files – Extra Metadata
- Media files;
- Audio files – artist, album, release date – and so on. For example Metadata in mp3 files, commonly used in the mp3 Meta data is the ID3vX.
- Pictures files – device taken with, GPS coordinates, resolution, etc. For example EXIF information within JPEG files.
- Video files – device taken with, GPS coordinates, resolution, etc. For example Metadata in mp4 files.
- Yet, Meta data entities can be embedded onto other types such as;
- Torrents – shared files location
- Bitcoin – digital money files
- My thought, is that meta data can be presented even by these;
- URL – for example —
https://www.google.co.il/?gws_rd=cr#q=time&start=80
This example shows that we are addressing;
google.com services,
query string = ‘time’
from result number = 80
- URL – for example —
Of course each site got its own URI parameters; yet we can treat these parameters as Meta data for a specific site, just like other data contents.
The idea itself, creating a data content that got additional separated Meta data attach to it. Seems magical to me. Cause of these facts:
- The Meta data attached to this data entity, without the requirement fetching data from an external central server.
- Data entity got its own meaning, without the requirement of the web.
- Data entities can be passed digitally in different forms of storage or communication.
What is magical in that logic, is that the detached Data and Meta data — can be treated as a separated record taken from a given big database storage.
Of course always each file had a certain extra information. Yet, in the beginning of computing the data within the file was commonly technical data as where does a certain packet in the file begins, or what format it is, etc. As far as I recall, if I am not mistaken, as data file progressed through time, more human readable meaningful Meta data was added to files.