Hello Dan, The short answer is no. I'm not averse to enhancing this with extensions > as they make sense. > > But the longer answer is that there a couple of SPI services that allow you > to customize the representations, [1], [2]. The default RO representations > are performed by an implementation of [1]. > > Eventually I'm thinking that Isis might provide out-of-the-box > implementations for HAL, Collection+JSON, Siren etc... but you might find > that your client-side (Javascript?) widget UI libraries work best with some > other more "adhoc" representations. > > What these SPI services *don't* allow is for the resources defined by RO > (or their input JSON) to change. I don't see any particular need to > customize this, though. >
I think I saw ContentMappingService being used in ToDoApp. Using those SPIs would work, however while going through the Spiro framework as discussed in the other thread, I saw interesting additional sections in the RO spec v1.1.0 about: 34.4 Minimizing Round-trips (x-ro-follow-links) 34.9 Minimizing Round-trips by supporting table grids I had skimmed through RO v1.0.0 before and afaik, those weren't there yet. Those sections, especially 34.9, addresses our need. 34.2 Sorting (x-ro-sort-by) and 34.3 Pagination (x-ro-page, x-ro-page-size) are also nice to haves.
