Look through "Awesome Sign Language", etc and add missing items

[cleong110]

Sources

• https://github.com/ZechengLi19/Awesome-Sign-Language
• https://github.com/Skye601/SLR
• https://www.sign-lang.uni-hamburg.de/lrec/project/asllrp.html
• https://www.semanticscholar.org/author/Amit-Moryossef/2300091284?coAuthor%5B0%5D=Amit%20Moryossef&q=moryossef&sort=influence, https://www.semanticscholar.org/author/Amit-Moryossef/2237431969, https://www.semanticscholar.org/author/Amit-Moryossef/73769459
• https://archive.mpi.nl/tla/islandora/object/tla%3A1839_00_0000_0000_0004_DF8D_8

I'm just going to go in reverse order chronologically looking for papers 2022 and after

Things to add

Datasets

• https://tvb-hksl-news.github.io/
• CSL-Daily dataset #13
• Update datasets list with mDGS #3
• DailyMoth70h dataset
• YoutubeASL dataset #12
• BSL-1K dataset
• PopSign ASL dataset #20
• "Sign Language Detection 'In the Wild' with Recurrent Neural Networks" and Signing in the Wild dataset #23
• SignBank+ #28
• SwissSli #29

Sign-Spotting/Corpus-Building

• Read and Attend: Temporal Localisation in Sign Language Videos #17
• Improving Sign Language Translation with Monolingual Data by Sign Back-Translation, (CSL-Daily) #34

PreTraining/Representation learning

• SignBERT+ (and SignBERT) #14
• BEST: BERT Pre-training for Sign Language Recognition with Coupling Tokenization  #19
• Self-Supervised Representation Learning with Spatial-Temporal Consistency for Sign Language Recognition #36

Hmmm it seems that research.sign.mt actually doesn't have many from the past few years

Misc:

• Towards the extraction of robust sign embeddings for low resource sign language recognition #35

Sign Language Translation

• Two-Stream Network for Sign Language Recognition and Translation. NeurIPS 2022. #9
• Conditional Variational Autoencoder for Sign Language Translation with Cross-Modal Alignment here
• LLMs are Good Sign Language Translators #7
• A Simple Multi-Modality Transfer Learning Baseline for Sign Language Translation #10
• Towards Privacy-Aware Sign Language Translation at Scale #11
• WMT Shared Task 22 #33
• WMT Shared task 23 #27

Continuous Sign Language Recognition

• MASA: Motion-aware Masked Autoencoder with Semantic Alignment for Sign Language Recognition #37
• Natural Language-Assisted Sign Language Recognition #38

Sign language retrieval

• Querying A Sign Language Dictionary with Videos Using Dense Vector Search #8
• CiCo: Domain-Aware Sign Language Retrieval via Cross-Lingual Contrastive Learning #16

Sign language production

• Considerations for meaningful sign language machine translation based on glosses #4
• Select and Reorder: A Novel Approach for Neural Sign Language Production. LREC-COLING 2024 #6
• SignLLM: Sign Languages Production Large Language Models #18
• SignBLEU: Automatic Evaluation of Multi-channel Sign Language Translation #21
• Generating Signed Language Instructions in Large-Scale Dialogue Systems #22

Text to Gloss

• Neural Machine Translation Methods for Translating Text to Sign Language Glosses

Isolated sign language recognition

• CVT-SLR: Contrastive Visual-Textual Transformation for Sign Language Recognition with Variational Alignment. adding "Conditional Variational Autoencoder for Sign Language Translation with Cross-Modal Alignment" sign-language-processing/sign-language-processing.github.io#37

[cleong110]

Also, here's a few things I learned from sign-language-processing#37, starting a checklist:

• sync, pull and merge master first!
• Search for the correct citation on Semantic Scholar
• Make a new branch ("You should always branch out from master")
• Add citation to references.bib. If dataset, prepend with dataset:. Exclude wordy abstracts. (better BibTex extension to Zotero can exclude keys)
• Check for egregious {} in the bibtex
• write a summary and add to the appropriate section in index.md.
• Make sure the citation keys match.
• Add a newline after each sentence in a paragraph. Still shows up as one paragraph but makes git stuff easier.
• ChatGPT 3.5 can suggest rewrites and improve writing.
• Check if acronyms are explained
• Copy-Paste into https://dillinger.io/, see if it looks OK
• Make a PR from the branch on my fork to master on the source repo

PR:

• sync master of both forks
• git pull master on local
• git merge master on branch
• git push
• THEN make the PR

Writing/style:

• try to describe what they did, not what the general process is.
• Don't have to describe what's in a repo
• something like "Three Letter Acronym (TLA)" is how you introduce acronyms
• Look through the Style Guide on the README
• Evaluations on X and Y datasets should have a the. Evaluation on the X and Y datasets"

[cleong110]

ChatGPT 4o Prompting Procedure:

If I have access that day, I:

• upload the full text
• use the following prompt

Let's build our prompt:

I am writing a summary of an academic paper. Based on what I have provided below, can you rewrite my first version of the summary to be more concise and professional? Please provide 3 alternative rewrites, and explain your suggested changes, as well as any issues with writing quality or inaccuracy in my original summary. Be sure the summaries you provide are accurate to the figure and the the abstract. If I have missed a key contribution from the paper please note that and suggest additions. If something is not clear request clarification and I can provide additional snippets. Please cite your sources for important details, e.g. "from the abstract" or "based on the full text". My summary is in markdown syntax and contains citations to a BibTex bibliography, the citations begin with "@". Please use the same citation style.

In addition, please follow the following style guide:

STYLE GUIDE
- **Citations**: Use the format `@authorYearKeyword` for inline citations, and `[@authorYearKeyword]` for citations wrapped in parentheses. To include multiple citations ,use a semicolon (;) to separate them (e.g., "@authorYearKeyword;@authorYearKeyword").
- **Background & Related Work**: Use simple past tense to describe previous work (e.g., "@authorYearKeyword used...").
- **Abbreviations**: Define abbreviations in parentheses after the full term (e.g., Langue des Signes Française (LSF)).
- **Percentages**: Use the percent sign (%) with no space between the number and the sign (e.g., 95%).
- **Spacing**: Use a single space after periods and commas.
- **Hyphenation**: Use hyphens (-) for compound adjectives (e.g., video-to-pose).
- **Lists**: Use "-" for list items, followed by a space.
- **Code**: Use backticks (`) for inline code, and triple backticks (```) for code blocks.
- **Numbers**: Spell out numbers less than 10, and use numerals for 10 and greater.
- **Contractions**: Avoid contractions (e.g., use "do not" instead of "don't").
- **Compound Words**: Use a forward slash (/) to separate alternative compound words (e.g., 2D / 3D).
- **Phrasing**: Prefer active voice over passive voice (e.g., "The authors used..." instead of "The work was used by the authors...").
- **Structure**: Present information in a logical order.
- **Capitalization**: Capitalize the first word of a sentence, and proper nouns.
- **Emphasis**: Use italics for emphasis by wrapping a word with asterisks (e.g., *emphasis*).
- **Quote marks**: Use double quotes (").
- **Paragraphs**: When a subsection header starts with ######, add "{-}" to the end of the subsection title to indicate a new paragraph. If it starts with #, ##, ###, ####, or ##### do not add the "{-}".
- **Mathematics**: Use LaTeX math notation (e.g., $x^2$) wrapped in dollar signs ($).


All right, here is information about the paper I am trying to summarize:

Paper Title: ""

Abstract: 
""

Full Text: see attached PDF

My Summary:  
""

All right, remember my initial instructions, please go ahead and provide me the requested concise, professional rewrite suggestions for my summary, with the requested explanations, citations, and following the style guide.

[cleong110]

Additional Checklist for datasets:

When adding a dataset, follow the following steps. This pull request provides an example:

• Fork the repo
• sync forks
• git checkout master
• git pull
• New branch: dataset/something
• Create a JSON along the lines of the schema below. e.g. FOO.json
• Add the JSON to src/datasets. e.g. src/datasets/FOO.json
  • "language" field should not need "sign language". No need to say "American Sign Language", "American" will do.
  • Very concise "samples" field, the table does not have a lot of space to display it.
• Add BibTex to src/references.bib.
  • prepend the citation key with dataset. e.g. dataset:sehyr2021asl
• If there are two citations, the second one in the JSON needs an @
• Commit/push the changes
• Make a pull request!

Schema:

{
  "pub": {
    "name": string, # this gets used as the name of the dataset, e.g. "WLASL"
    "year": integer or null,
    "publication":string or null, # this matches a key in references.bib, e.g. "dataset:joshiISLTranslateDatasetTranslating2023"
    "url": string or null # URL to access it. e.g. "https://www.sign-lang.uni-hamburg.de/dgs-korpus/index.php/welcome.html"
  },
  "#loader": string or null, # the key you would use in the sign language datasets library. e.g. "dgs_corpus". Website will auto-link
  "#items": integer or null, # this is the number of unique signs in the column
  "#samples": string or null, # e.g. "1100 videos" or "8,257 Sentences"
  "#signers": integer or string or null, # number of unique signers
  "features": array of strings, ["feature1","feature2"], # I've seen things like "mouthing", "video:RGB", "pose:Kinect", "pose:OpenPose","text:Polish", "gloss:ASL", "writing:HamNoSys", etc.
  "language": string, # the Sign language or languages, e.g. "American" for American Sign Language (ASL)
  "license": string or null,
  "licenseUrl": string or null
}