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

inheritance of behaviors across resources #1612

Closed
stephenwf opened this issue May 19, 2018 · 8 comments
Closed

inheritance of behaviors across resources #1612

stephenwf opened this issue May 19, 2018 · 8 comments
Assignees
Labels
presentation Ready-for-TRC Normative changes ready for TRC review

Comments

@stephenwf
Copy link

In presentation 2, as a viewer, if I come across a manifest with a viewingDirection, I should take that as an intention for the canvases to be displayed accordingly, even if there are multiple sequences. If multiple sequences, each with different viewingDirection properties, they trump the Manifests viewingDirection.

In a way, sequences by default inherit the viewingDirection from the Manifest. Is this true for ranges? If a top level Manifest has a viewingDirection of right-to-left, should that be inherited by each of the Ranges (if they don't have a viewingDirection themselves) or should they default to left-to-right.

Further, in presentation 3, if sequences are now represented as Ranges, their behaviour here will change, and any conversion between presentation 2 and presentation 3 would have to explicitly set the viewing direction, if it was previously implied by the Manifest having the property (if Ranges should not inherit this direction).

@azaroth42
Copy link
Member

Yes, that's all correct. We should be clearer in the spec text that viewingDirection inherits, and also which (if any) behavior values should be inherited. E.g. paged clearly inherits from the Manifest to the Ranges, and can be overridden with non-paged at the Canvas level. On the other hand repeat on the Manifest is not inherited by each individual Range.

@zimeon
Copy link
Member

zimeon commented Jun 26, 2018

A notion of overriding inheritance would, I think, end up with a need to have opposites or complete sets of alternate behaviors including the default. For example, in order to override auto-advance one needs to be able to specify the opposite (default), non-auto-advance, manual-advance, pause-at-end or such. And then there is documentation clarity issue of grouping opposites or complete sets of alternate behaviors so that the idea of how to override is clear.

@workergnome
Copy link

If i being playing a temporal range set to auto-repeat (say a TOC), and then I click into the thumbnail-nav to go to a section (AKA the scrubber), but I have not set the thumbnail-nav range to be auto-repeat, does that viewer then cancel the auto-repeat behavior since I've selected a content resource from another enclosing resource?

@azaroth42 azaroth42 changed the title viewingDirection/renderingDirection inheritance in P2/P3 inheritance of behaviors across resources Jul 11, 2018
@azaroth42
Copy link
Member

Eds call -

  • Collections inherit from Collections.
  • Manifests do not inherit from Collections.
  • Canvases inherit from Manifests, but not from ranges.
  • Ranges inherit from Ranges and from Manifests.

Then we need to specify sets of disjoint behaviors, and define any negation behaviors needed.

@azaroth42 azaroth42 removed the discuss label Oct 2, 2018
@azaroth42 azaroth42 self-assigned this Oct 2, 2018
@azaroth42
Copy link
Member

azaroth42 commented Oct 2, 2018

Initial issue -- if Canvases do not inherit from Ranges, then it seems pointless to have Unordered, Individuals, Continuous and Paged on Ranges. The canvas would always inherit the value from the Manifest, not from the Range. This is the same sort of issue as auto-advance on a Range (#1632) ... it's the presentation of the canvases in the range that matters.

@azaroth42
Copy link
Member

unordered, individuals, continuous and paged are disjoint. They do not need a negation, as you just pick one of the others. individuals is specified as the default if none are provided. They inherit as expected, other than from Range to Canvas.

non-paged, facing-pages and paged are disjoint on a Canvas. The first two are negations of paged. They are dependent on the Manifest having the paged behavior.

sequence, thumbnail-nav and no-nav are disjoint. They do not need negations but the inheritance model of sequence is strange, as only the top level range is a "sequence". Once you have started no-nav you can't negate it down the hierarchy to suddenly have it appear. thumbnail-nav has child ranges with thumbnails, but we can allow them to inherit the thumbnail-nav-ness.

multi-part and together are disjoint, and don't need negations. If there are things in a together group, then just don't put things into it that shouldn't be there. A collection that is in a multi-part collection but isn't itself multi-part ... ... I don't know what that would mean.

auto-advance is not disjoint with anything, and needs a negation (no-auto-advance).
repeat is not disjoint with anything, and needs a negation (no-repeat).

@azaroth42
Copy link
Member

More weirdness notes - If a newspaper article Range is part of a paged Manifest, the article inherits the paged-ness. It should probably be required to have individuals to assert order, but not paged.
But conversely meaning that it's not pointless to have them on Ranges.

@azaroth42 azaroth42 added the Ready-for-Eds Editorial changes ready for Editorial review label Oct 3, 2018
@azaroth42
Copy link
Member

Closed by #1681

@azaroth42 azaroth42 added Ready-for-TRC Normative changes ready for TRC review and removed Ready-for-Eds Editorial changes ready for Editorial review labels Mar 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
presentation Ready-for-TRC Normative changes ready for TRC review
Projects
None yet
Development

No branches or pull requests

4 participants