Page MenuHomePhabricator

[Epic] Provide derived values for re-use by third parties (as well as for internal use)
Closed, InvalidPublic

Description

The JSON representation of wikibase data (and perhaps also the bindings in PHP, JS, etc) should support "derived" values. Examples are:

  • ID values expanded to full URIs
  • Quantity values normalized to a base value
  • Time values normalized to an ISO date
  • URLs for sitelinks
  • Terms including language fallback metadata

Such derived values should (optionally) be present in:

  • API output
  • EntityData output
  • JSON dumps

It should not be present in the internal representation used for storage in the database. Normalization depends on global knowledge (such as statements on properties) that can change, and would invalidate the content of the database if recorded there.

Some use cases:

  • ingestion of quantity values for querying needs normalized values (quantity, time, etc)
  • full URIs for references to other vocabularies / authorities makes as a full hub in the LOD web (instead of the dead end we Wikidata currently is).
  • Lua would have access to normalized versions of the data values, e.g. to create sorted lists
  • Gadgets have access to sitelink URLs for linking

Event Timeline

daniel created this task.Sep 14 2015, 4:35 PM
daniel raised the priority of this task from to Needs Triage.
daniel updated the task description. (Show Details)
daniel added a subscriber: daniel.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 14 2015, 4:35 PM
  • Gadgets have access to sitelink URLs for linking

wb.sites.getSites()

Lydia_Pintscher triaged this task as High priority.Dec 18 2015, 10:26 AM
Lydia_Pintscher set Security to None.
Addshore closed this task as Invalid.Jan 23 2019, 12:22 PM
Addshore added a subscriber: Addshore.

Part of the epic has been done, and we have decided to not continue work as specifically described here. (we don't need the epic any more)