These top level Ranges then embed or reference other Ranges, Canvases or parts of Canvases in the items property.
(Emphasis added)
In 2.1, we were explicit that Canvases MUST be references:
References to canvases, or rectangular parts of a canvas, within the current range. Each included canvas must be referenced via a string containing the canvas’s URI.
If Canvas embedding is allowed, we should be clearer about this.
This isn't strictly necessary, as all the canvases could be in items and then a sequence behavior range would exclude the canvases that aren't in the default order.
Dawn and Rob propose canvases should NOT be embedded, only other ranges. It would make it almost impossible to find the embedded canvas for other ranges or other uses (e.g. content-state)
Prezi3 in the section on Ranges says:
(Emphasis added)
In 2.1, we were explicit that Canvases MUST be references:
If Canvas embedding is allowed, we should be clearer about this.
This isn't strictly necessary, as all the canvases could be in
items
and then asequence
behavior range would exclude the canvases that aren't in the default order.