Rename startCanvas to start, allow ref to part of a Canvas

[azaroth42]

Now that Canvases can have a duration, the start of the startCanvas is not necessarily the beginning of the duration. It could be that the interesting part of the content begins on the first canvas, but not at the beginning of its duration. This would let the player initialize to a temporal offset within the Canvas, rather than playing the 10 seconds of silence or 3 minutes of audience noise at the beginning.
For x,y canvases, this would allow scrolling to a region of the Canvas, such as the most interesting part of the 150k px Princeton scroll.

Proposal: startCanvas can also refer to a Canvas with a fragment, in the same way that Ranges can.

[tomcrane]

Agree with the user experience, but is startCanvas is still the best name for this term? It's a simplified highlighting annotation used to initialise a viewer.

"startAt": "http://example.org/iiif/bladerunner/canvas/3#xywh=1000,1000,300,400&t=743.32"

A viewer that can be given a highlighting anno to initialise with can use exactly the same mechanism when the info is provided in the manifest.

I don't mind startCanvas though, for continuity. I'm not proposing startAt, just thinking about how obvious the intent is.

[jpstroop]

start?

[azaroth42]

While we're renaming things ... start is good. Gives us more scope in the future (c.f. contentLayer -> includes)

[tomcrane]

👍 to start

[jpstroop]

I realize it was my suggestion, but I can't think of a reason why start would bother me either. (backhanded 👍 )

[zimeon]

👍 to start

[mikeapp]

👍 to start

[azaroth42]

So new proposal, that I think we're all +1 on...

Proposal: Rename startCanvas to start and clarify that it can also refer to a Canvas with a fragment, in the same way that Ranges can.

[mikeapp]

Community agreement on 12/20

[tomcrane]

Can start point to a range as well? Skip past the audience noise and general hubbub, and start playing at the overture?

Allowing start to point to range makes this simpler to model, and still results in the same thing, player jumps to canvas/fragment. A client would effectively simulate the selection of that range in the UI.

[azaroth42]

I think it should point to either a range or a canvas/part-of-canvas, but not either as then there'd be two ways to accomplish the same thing, forcing a decision on the production side and two implementations on the consumption side. I'd prefer just the Canvas, as there may not be an appropriate range that you'd want to expose. So I'm 👎 on start referencing a Range, unless there's some functionality that a Range would offer us over the Canvas (and then we could have it as /just/ the Range?)