Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Description of disjoint for canvas behaviors #2154

Open
tomcrane opened this issue Sep 8, 2022 · 3 comments · May be fixed by #2304
Open

Description of disjoint for canvas behaviors #2154

tomcrane opened this issue Sep 8, 2022 · 3 comments · May be fixed by #2304
Assignees

Comments

@tomcrane
Copy link
Contributor

tomcrane commented Sep 8, 2022

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.

@zimeon
Copy link
Member

zimeon commented Sep 8, 2022

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

@azaroth42
Copy link
Member

Dawn and Rob agree.

@azaroth42
Copy link
Member

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

@kirschbombe kirschbombe self-assigned this Jun 7, 2024
@kirschbombe kirschbombe linked a pull request Jun 9, 2024 that will close this issue
@kirschbombe kirschbombe linked a pull request Jun 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants