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

Recipe #489 : Teaching with a Multimedia Canvas #128

Open
glenrobson opened this issue Aug 21, 2024 · 9 comments
Open

Recipe #489 : Teaching with a Multimedia Canvas #128

glenrobson opened this issue Aug 21, 2024 · 9 comments
Assignees
Labels
Milestone

Comments

@glenrobson
Copy link
Member

Links

Background and Summary

This recipe provides a complex canvas with a video, images and text which are painted on a timeline. It provides a complex use case to test whether viewers can cope with some of the extended posibilities provided by the Presentation API.

Voting and changes

We welcome comments on the recipe and as well as voting +1, confused face or -1 feel free to add comments to this issue. If this issue is approved then the author will take account of the comments before we merge the branch in to the master cookbook branch.

If the recipe is rejected by the TRC then we will make the changes requested and resubmit it to a future TRC meeting. If you feel that your comments are substantial enough that the recipe should be looked at again by the TRC after the changes have been made please vote -1 (thumbs down). A confused face is treated as abstaining.

Changes to the recipe will only be made after the TRC voting process has concluded.

@glenrobson glenrobson added this to the August 2024 milestone Aug 21, 2024
@julsraemy
Copy link

julsraemy commented Aug 26, 2024

I've had a positive experience with the Theseus Viewer, and the JSON-LD serialization looks fine to me.

However, this recipe really shows the limitations of cross-client interoperability. In viewers or players outside of Theseus, the experience is notably poor. I'm wondering if it would be beneficial to include a warning in the Manifest to alert users to these potential issues when IIIF clients that do not - or only partially - support it.

@robcast
Copy link

robcast commented Aug 28, 2024

👍 I made a small note about the duration property in hypothes.is

@triplingual
Copy link

We had some discussion on the call about the title and how it's somehow not quite right. The use case is an imaginary teaching scenario, but the recipe is definitely not just about teaching.

@triplingual
Copy link

Standard comment that I upvoted my own recipe

@kirschbombe
Copy link

Giving a thumbs up, but conditional on a few changes from editors:

  • In the implementation notes: "Once there is an AV resource included on a Canvas, there exists a notional timeline whose duration and time range can then be used in targeting resources to the Canvas." This isn't quite accurate. The duration/timeline exists because it is defined in the Canvas and is technically not dependent on having an AV resource. Can you change the language to reflect that the Canvas duration property is what introduces the timeline feature/functionality?
  • Remove the teaching bits from the title/recipe and rename something like "Rendering multiple media types on a time-based Canvas"

It would also be nice to eventually have two additional recipes for 1) using duration on a Canvas to introduce resources on a timeline and 2) painting an annotation (textual body) onto a canvas. This recipe could be updated later to reference these, but doesn't need to wait for these (and are just suggestions).

@azaroth42
Copy link
Member

Also +1 with the caveats above from Dawn. It's a valuable recipe from the point of view of an "integration test" -- here is how you can put multiple things together on a single temporal canvas, some of which are not themselves temporal. That to me is the functionality that sets this recipe apart from others.

@zimeon
Copy link
Member

zimeon commented Aug 28, 2024

In addition to other issues mentioned there is an "in in" in:

When resources’ appearance on a Manifest are governed in part by time, they can be entered in in the Manifest in any order.

I think this is confusingly written (and first Manifest should be Canvas). I suggest instead:

The order in which resources appear on the Canvas is governed by the time portion of the annotation target when specified, they can be entered in the Manifest in any order.

@glenrobson
Copy link
Member Author

Issue 128 (Recipe #489 : Teaching with a Multimedia Canvas )

+1: 13 [JulieWinchester akrishnan15 glenrobson irv kirschbombe ksclarke mikeapp nfreire regisrob rentonsa robcast triplingual zimeon]
0: 2 [cubap julsraemy]
-1: 0 []
Not TRC: 0 []
Ineligible: 1 [azaroth42]

Result: 13 / 15 = 0.87

Super majority is in favor, issue is approved

@triplingual
Copy link

triplingual commented Sep 27, 2024

  • Duration property mention
  • Title change
  • Revise notional timeline content
  • Revise resource order entry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants