Question - Sign Language Datasets
CONTRIBUTOR
Even more complicating - 

As I see it, datasets can have "addons".
For example, the WebNLG dataset is a dataset for data-to-text. However, a work of mine and other works enriched this dataset with text plans / underlying text structures. In that case, I see a need to load the dataset "WebNLG" with "plans" addon.

Same for sign language - if there is a dataset of videos, one addon can be to run OpenPose, another to run ARKit4 pose estimation, and another to run PoseNet, or even just a video embedding addon. (which are expensive to run individually for everyone who wants to use these data)

This is something I dabbled with my own implementation to a [research datasets library](https://github.com/AmitMY/meta-scholar/) and I love to get the discussion going on these topics.
2020-06-26T16:17:38Z
https://github.com/huggingface/datasets/issues/302#issuecomment-650266403
https://api.github.com/repos/huggingface/datasets/issues/302
MDEyOklzc3VlQ29tbWVudDY1MDI2NjQwMw==
https://api.github.com/repos/huggingface/datasets/issues/comments/650266403/reactions
2020-06-26T16:17:38Z
https://api.github.com/repos/huggingface/datasets/issues/comments/650266403
https://avatars.githubusercontent.com/u/5757359?v=4
https://api.github.com/users/AmitMY/events{/privacy}
https://api.github.com/users/AmitMY/followers
https://api.github.com/users/AmitMY/following{/other_user}
https://api.github.com/users/AmitMY/gists{/gist_id}
https://github.com/AmitMY
AmitMY
MDQ6VXNlcjU3NTczNTk=
https://api.github.com/users/AmitMY/orgs
https://api.github.com/users/AmitMY/received_events
https://api.github.com/users/AmitMY/repos
https://api.github.com/users/AmitMY/starred{/owner}{/repo}
https://api.github.com/users/AmitMY/subscriptions
User
https://api.github.com/users/AmitMY
public
MEMBER
This is a really cool idea !
The example for data objects you gave for the RWTH-PHOENIX-Weather 2014 T dataset can totally fit inside the library.

For your point about formats like `ilex`, `eaf`, or `srt`, it is possible to use any library in your dataset script.
However most user probably won't need these libraries, as most datasets don't need them, and therefore it's unlikely that we will have them in the minimum requirements to use `nlp` (we want to keep it as light-weight as possible). If a user wants to load your dataset and doesn't have the libraries you need, an error is raised asking the user to install them.

More generally, we plan to have something like a `requirements.txt` per dataset. This could also be a place for addons as you said. What do you think ?
2020-06-28T21:02:10Z
https://github.com/huggingface/datasets/issues/302#issuecomment-650821258
https://api.github.com/repos/huggingface/datasets/issues/302
MDEyOklzc3VlQ29tbWVudDY1MDgyMTI1OA==
https://api.github.com/repos/huggingface/datasets/issues/comments/650821258/reactions
2020-06-28T21:02:10Z
https://api.github.com/repos/huggingface/datasets/issues/comments/650821258
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
CONTRIBUTOR
Thanks, Quentin, I think a `requirements.txt` per dataset will be a good thing.
I will work on adding this dataset next week, and once we sort all of the kinks, I'll add more.
2020-06-29T07:19:17Z
https://github.com/huggingface/datasets/issues/302#issuecomment-650979736
https://api.github.com/repos/huggingface/datasets/issues/302
MDEyOklzc3VlQ29tbWVudDY1MDk3OTczNg==
https://api.github.com/repos/huggingface/datasets/issues/comments/650979736/reactions
2020-06-29T07:19:17Z
https://api.github.com/repos/huggingface/datasets/issues/comments/650979736
https://avatars.githubusercontent.com/u/5757359?v=4
https://api.github.com/users/AmitMY/events{/privacy}
https://api.github.com/users/AmitMY/followers
https://api.github.com/users/AmitMY/following{/other_user}
https://api.github.com/users/AmitMY/gists{/gist_id}
https://github.com/AmitMY
AmitMY
MDQ6VXNlcjU3NTczNTk=
https://api.github.com/users/AmitMY/orgs
https://api.github.com/users/AmitMY/received_events
https://api.github.com/users/AmitMY/repos
https://api.github.com/users/AmitMY/starred{/owner}{/repo}
https://api.github.com/users/AmitMY/subscriptions
User
https://api.github.com/users/AmitMY
public
An emerging field in NLP is SLP - sign language processing.

I was wondering about adding datasets here, specifically because it's shaping up to be large and easily usable.
The metrics for sign language to text translation are the same.

So, what do you think about (me, or others) adding datasets here?


An example dataset would be [RWTH-PHOENIX-Weather 2014 T](https://www-i6.informatik.rwth-aachen.de/~koller/RWTH-PHOENIX-2014-T/)
For every item in the dataset, the data object includes:
1. video_path - path to mp4 file
2. pose_path - a path to `.pose` file with human pose landmarks
3. openpose_path - a path to a `.json` file with human pose landmarks
4. gloss - string
5. text - string
6. video_metadata - height, width, frames, framerate


------

To make it a tad more complicated - what if sign language libraries add requirements to `nlp`? for example, sign language is commonly annotated using `ilex`, `eaf`, or `srt` files, which are all loadable as text, but there is no reason for the dataset to parse that file by itself, if libraries exist to do so.