d::gen unpacks as ‘digital generation network’, or ‘data generation network’, and, given the .net domain, for ‘networking in a digital generation’ (hence dgen.net)<\/p>\n\n\n\n
The double colon is derived from both the “scope resolution” operator in C++, and is a nod to the :\/\/ used in URLs.<\/p>\n\n\n\n
We use the :: operator to define n-dimensional tags.<\/p>\n\n\n\n
What does that mean?<\/strong><\/p>\n\n\n\n Well, very much based on the work I did at Virgin Net where we created (at that time, 1997) one of the best events listing services in the world , the brief from the team was “we want to add any parameter” (e.g. number of seats in a cinema, type of popcorn that might be served, not just what’s showing, where and when). This led us down many rabbit holes of how to define open ontologies, beyond simple key-value pairs. We did okay \u2014 the cinema listings service we build was the most accurate in the UK and was sold to Time Out.<\/p>\n\n\n\n It got me thinking and, as ‘tags’ became more of a thing, we tried a few experiments to hack tagging systems by simply taking what was there and adding a ‘::’ in them which we could unpack later.<\/p>\n\n\n\n For example, ‘cinema::name=[name]::seats::disabled=[number]’, ‘location::lat=[lat];long=[long]’, ‘mood::happy’, ‘weather::cloud::light’, ‘event::demonstration::demonstrators=[headcount]’ … the idea being that you can keep going to as granular a level as you wish with as many ‘::’ delimiters as you want (‘event::demonstration::headcount=[headcount]::medianHairColour=pink’).<\/p>\n\n\n\n Lots to think about, how can we make it super easy for anyone to publish some data with no ‘tech knowledge’ that we can pick up with machines later…\u00a0 even if it’s messy and semi-structured, we should be able to reform into something meaningful? <\/p>\n\n\n\n