After specifying the database schema (bug 56095), we now need to implement it. I propose to do this in two stages:
- first, only data value types that rely on simple equality for queries, that is, string (including URL and CommonsMedia) and EntityId.
- second, data value types that need range- or prefix matching, such as quantity, time and geo.
Whiteboard: query u=dev p=0 c=backend