home edit page issue tracker

This page pertains to UD version 2.

Metadata harmonisation: align spoken-data fields with UniDive naming conventions

Back to Chinese HK · Back to index

Repo: https://github.com/UniversalDependencies/UD_Chinese-HK

Cross-posting from the UniDive WG1 T1.5 (spoken language guidelines) metadata harmonisation review. We compared UD_Chinese-HK’s current CoNLL-U metadata against the proposed naming conventions (see also the full treebank status table). This is a suggestion for maintainers to review - feel free to push back on anything that doesn’t fit the corpus.

1. Document-level (naming conventions)

No newdoc id exists in the current .conllu. However, the repo’s own README documents exactly 4 distinct sources by sent_id range (matching the parallel UD_Cantonese-HK treebank):

sent_id range Proposed newdoc id Title Source
1-410 missing_days Missing days / 小時光 (film) https://www.youtube.com/watch?v=1qSMiw0vhzU
411-547 tempo_in_temple Tempo in Temple / 廟眾樂樂 (film) https://www.youtube.com/watch?v=8e8Lqd6grTE
548-650 what_day_is_today What day is today / 今日星期幾 (film) https://www.youtube.com/watch?v=bBGwxIDiZ_o
651-1004 legco_president_election_2016 Legislative Council meeting (2016-10-12) https://www.legco.gov.hk/yr16-17/chinese/counmtg/hansard/cm20161012-translate-c.pdf
Field Suggestion
add # newdoc id at sentences 1, 411, 548, and 651, using the proposed ids above (please confirm the slugs; same ranges as the parallel UD_Cantonese-HK treebank)
add # genre (film / legislative-proceedings) per document

2. Speaker-level (naming conventions)

Field Suggestion
no speaker metadata exists; the legislative-council portion (sentences 651-1004) clearly involves multiple speakers - could speaker_id be recovered and tagged?

3. Sentence-level (naming conventions)

Field Suggestion
translit pinyin transcription (added in v2.12) - rename to text_transliteration

This issue was prepared as part of the UniDive WG1 T1.5 spoken language guidelines effort. Happy to help implement these changes ourselves if that’s easier than doing it on your end - just let us know.