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

Manifest updates for Ramp interoperability #218

Open
absempere opened this issue Dec 9, 2024 · 1 comment
Open

Manifest updates for Ramp interoperability #218

absempere opened this issue Dec 9, 2024 · 1 comment
Assignees

Comments

@absempere
Copy link

From Sara:

In Ramp testing, 2 more small manifest problems were found:

  1. The manifest id (https://avannotate.github.io/dev-demo/manifest.json) should be the same as the URL it is published at (https://avannotate.github.io/dev-demo/manifests/manifest.json).

(note one has a manifests directory in the URL and the other doesn't)

  1. We need to drop the quotes around the t= value in PointSelectors (they are values, not strings):
    selector": {
    "type": "PointSelector",
    "t": "45"
    }
    becomes
    selector": {
    "type": "PointSelector",
    "t": 45
    }

Ok, apologies, but there's one more change to the manifests (after a long discussion with folks on github).

Instead of using PointSelectors or Range Selectors, we're going to use a media FragmentSelector:

"selector": {
"type": "FragmentSelector",
"conformsTo": "http://www.w3.org/TR/media-frags/",
"value": "t=52,60"
}
(t could also just equal a single value rather than a range) and this time the value is actually in quotes.

We'll need to test this, because it probably doesn't work in all the players, but at least we'll be DOING IT RIGHT.

@SteveMarvin
Copy link

I'm not certain how to test this properly.

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

No branches or pull requests

3 participants