solid / solid/data-interoperability-panel
Media resources with various encodings
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
If we take an example of photograph or a video recording. I think for each we would have an RDFSource describing it as creative work. It may include information about who took photo / video, geolocaiton, what it depicts, who appears in the creative work (aka 'tagged in' social feature). Also if someone would like or comment, the would reference that 'crative work' which I would consider RDFSource.
At the same time, each one of those creative works would have multiple encodings. For photos, it could have image/jpeg version or image/png. Also having Responsive images feature, we can expect even more encodings of the same image. Similar for videos we can expect multiple encodings of the same creative work with different codecs and qualities and frame rates (720p60 etc.)
I'd like to clearly define difference between the conceptual creative work and multiple encodings of it each denoted by distinct URI. I think we also should notice that in some cases we want to have meta data for each of the encodings with information like codec used, encoding software which produced it etc.
EDIT: See also:
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the issue's RDFSource discussion and the linked MDN material on responsive images and the HTML source element. Define how one conceptual creative work relates to multiple URI-identified encodings, including where encoding metadata belongs; done means the distinction and metadata model are clearly documented in the specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100