We have (at least) two options for how to specify ordering
Opened this issue · 2 comments
there are two options for ordering the component resources in an aggregation. Option 1 is a JSON array (i.e. an ordered list) of identifiers specifying a default order. This mirrors the approach taken for W3C Web Publications (ePub for the web). Option 2 is inspired by OAI-ORE and leverages schema.org ItemLists. Option 2 is conceptually and practically far more complex, however it may be more robust, and may more useful for providing information about next & previous components within the files for each component. It remains an open issue as to whether the extra complexity is manageable or necessary.
Also HAX uses JSON outline schema
Relevant comment from Dan Brickley on Twitter https://twitter.com/danbri/status/1087784904065089536