Interval reading in XML should be order based on time irrespective of when data is entered into system
intervalReadings in IntervalBlock needs to be order by time. e.g. @OrderBy("timePeriod.start, timePeriod.duration asc")
While I agree this would be useful, we need to also keep in mind that there is not guarantee that monotonic ordering of the IntervalReadings in import (parsing) of the xml.
Is it suitable to use the suggested @OrderBy only during the export service?
Also, do you feel that a similar ordering of the IntervalBlocks should be put in place?
There are two open questions on this issue:
Is it suitable to use the suggested @OrderBy only during the export service?
Also, do you feel that a similar ordering of the IntervalBlocks should be put in place?
I would like to close this off (and will assume @OrderBy should be placed on all DB references??)
same XML structure and generation process used for both DMD & CMD. User may wants to visualize data in browser, XMLSpy or other XML viewing tool. Then there will be poor readability.