Add accessors for Media Fragments URI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
The Media Fragments URI Specification defines how dimensions (spatial, temporal, track, …) can be specified. <img src="foo.png#xywh=10,20,100,40"> would specify to show a cropped version of the actual image (100x40 pixels at a 10x20 pixel offset). <audio src="/audio.ogg#t=5,20"> wouls specify to play the audio file from 5th second till 20th second.
URI('foo.png#xywh=10,20,100,40').mediaFragment() could return {x: 10, y: 20, w:100, height:40}, while URI('foo.png').mediaFragment({y: 20, w:100, x: 10, height:40}) could lead to foo.png#xywh=10,20,100,40.
Things get more interesting with converting different representations of the same information, as the Temporal Dimension notation shows.
Resources
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Media Fragments URI Specification and the linked JavaScript implementation to map spatial, temporal, and track fragment representations. Use the examples in the issue as the initial acceptance cases; done means URI instances can read and write the requested media fragment information, including conversions between equivalent temporal notations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100