Skip to content

Design Rationale

Aidan Sawyer edited this page Jan 6, 2018 · 2 revisions

Prioritizing .json and .xml Output

  • growing universal standard for encoded machine-readable data
  • easily transferable and lightweight
  • human (and non-professional) readability
  • integration with web (and micro-) services
  • easy to learn/intuit with little to no pre-requisite knowledge

Configuration

  • portability/customization (many collection-specific tweaks)
  • ease of use (decrease pre-requisites for use)
  • speed (faster to tweak a config than to fork and edit code)