Clarified question IDs and refreshed data spec documentation
Sep 24, 2021
Shipped6 commits+133−51
- NF
- Question IDs are now the standard term — We updated the README and question files to use **Question ID (qid)** instead of **Data Spec ID**, making the naming more consistent across the project.
- Feed specs now include clearer IDs and examples — Several feed pages were updated with finalized request IDs, example values, and clearer descriptions for commonly used markets such as BTC/USD, ETH/USD, ETH/JPY, and TRB/USD.
Documentation
- Refreshed the README with clearer field definitions, improved request template formatting, and cleaner note/dispute sections.
- Updated multiple data specification pages with finalized Question IDs, request IDs, and example values for feeds including AMPL/USD, USPCE, PolygonBridge, BTC/USD, ETH/USD, ETH/JPY, and TRB/USD.
- Renamed “Data Spec ID” to “Question ID (qid)” in the question files and clarified that file names may be guessed initially before being finalized by the team.
6 commits+133-51
- NF