I think this should be kept in at this point. We'll be moving towards more fine-grained merge strategies in future, and I can see a client wanting to change the image precedence at any point. 

@oli-hall the reason why imagePrecedenceOrdering delegates to the ordering for publisherPrecedenceOrder is that they're the same right now, but a consumer of this data shouldn't know that as they may diverge in the future.