api icon indicating copy to clipboard operation
api copied to clipboard

Description of disjoint for canvas behaviors

Open tomcrane opened this issue 3 years ago • 3 comments

In P3 spec the paged behavior is "Valid on Collections, Manifests and Ranges..." (not individual canvases; one canvas can't be paged)

facing-pages and non-paged are valid only on Canvases; they mark an individual canvas as an exception to the behavior of the parent sequence (lower case S).

But...

facing-pages says "Disjoint with paged and non-paged."

and

non-paged says "Disjoint with paged and facing-pages."

...the spec shouldn't say they are disjoint with paged when paged is not permitted on a Canvas, and these two behaviors are only permitted on Canvases.

tomcrane avatar Sep 08 '22 16:09 tomcrane

I agree, it is true in the sense that they can't be used on the same resource, but irrelevant because of that. This description could be fixed in a bugfix release because it isn't changing the spec

zimeon avatar Sep 08 '22 16:09 zimeon

Dawn and Rob agree.

azaroth42 avatar Jun 07 '24 01:06 azaroth42

Should clarify in the spec when non-paged is used - e.g. "page order" etc

azaroth42 avatar Jun 07 '24 01:06 azaroth42