Giter VIP home page Giter VIP logo

bodtkhobwa's People

Contributors

chrzyki avatar lingulist avatar monpasang avatar simongreenhill avatar wu-urbanek avatar xrotwang avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

bodtkhobwa's Issues

add partial cognates and morpheme tags

The data is a good example for cldf in extended versions, and it contains:

  • morpheme boundaries, to which morpheme tags are attached (all checked)
  • partial cognates
  • partial alignments

So we should be able to see here how well lexibank can account for these enhanced ways of annotation. And also if we can compute extract these things and convert them to cldf without major efforts.

Fix curation warnings

The REPL spits a number of warnings, e.g.

[WARNING] Problem with row 821 in col 1, expected «<function at 0x7f7279777488>» as datatype but received «249 ? 250» (ROW: pʰ yː + tɕʰ u - + l u ŋ|249 ? 250|cockroach|cockroach|249 685 250|Khoitam|ʨʰu+luŋ|INSECT1 COCKROACH1 COCKROACH2|||570 685 250|i n + i n + i n c|pʰ yː + tɕʰ u + l u ŋ|(pʰyː) ʨʰu-luŋ, entry cogids).

during the makecldf call. This should ideally be addressed before the SDATA submission to make the reproducible run 'more clean'.

write generic code to make a first useful parse for morpheme annotation

With the cross-semantic cognate sets, we can now make rather precise suggestions as to which "tags" we should give to morphemes. So the initial table needs to be refined, and we list only the 900+ morphemes, and we can in fact automatically already define how they should be called, if the occur only for one concept. This reduces the work greatly.

It'll be important to

  • write generic code for this (up to @LinguList)
  • note the steps in our worfklow for later paper on this or blogpost (@monpasang)
  • adjust the howto shell script (@LinguList)

@monpasang should also find about half an hour (more not needed) to explain to @MacyL, what he was doing so far, so she can understand our workflow better, for future analyses of her own.

double-check concept linking

Concepts need to be double-checked, also with new concepts we want to add to concepticon, currently with an asterisk *.

Determine symbol for missing data

The raw file (see here) uses Ø to indicate that a value is missing. The question is here: is this value missing because there is no word for this entry, or is it missing, because it is not cognate with the rest?

We will assume that it is the latter for now, but it may be important, that Tim goes back and adds missing data.

Work on orthography profile

I just created a context sensitive orthography profile. This allows you, @monpasang, to refine potentially problematic IPA characters.

It elicits data according to frequency. You best edit in LibreOffice or other spreadsheet software.

Many cases are unproblematic. In fact, what you have to do is: read the symbol in the first column as the one that we find in the data, and the second column as our preferred way of rendering it. Then you have examples and languages. If we add <?>, this means, we can't interpret the symbol. Most of the time, this means that something's wrong.

However, line 9 is our practice:

  • we render morpheme boundaries with a + character, so you should put a + in there.

Note that $ means "end of word" (so only useful to know) and ^ means "start of word". We don't list them in the second column, as this is just information for us.

Note another question: Do you make a distinction between morpheme boundaries and word boundaries (e.g., by writing "-" and " " = space)? If so, I changed them spaces to _, as this is the way we render spaces in our system.

Diphthongs not accepted by CLTS

Diphthongs in this dataset are not recognized by CLTS:

Dataset Sound Token ID
bodtkhobwa ai 'h ai';'h ai' Khispi-74_burnvi-1;Duhumbi-74_burnvi-1
bodtkhobwa au 'ɲ au';'ɲ au' Rupa-11_afternoon-1;Shergaon-11_afternoon-1
bodtkhobwa ei 'm ei';'a l ej~i/ei' Khispi-29_bamboo-1;Khispi-68_brotherinlaw-1
bodtkhobwa ou 'm ou';'tɕʰ ə tɕʰ ou' Rahung-87_chest-1;Rahung-471_squirrelflying-1
bodtkhobwa ui 'w ui';'h ui' Khispi-5_3sg-1;Khispi-50_blood-1
bodtkhobwa ɔi 'w ɔi';'kʰ ɔi t a m p a' Duhumbi-5_3sg-1;Duhumbi-259_khoitampeople-1
bodtkhobwa ɔu 'd ɔu l a';'ʨʰ ɔu' Duhumbi-32_bastard-1;Duhumbi-588_boil-1
bodtkhobwa ɛi 'm ɛi';'l ɛi s i' Duhumbi-29_bamboo-1;Duhumbi-30_banana-1
bodtkhobwa ɛ̃ĩ 's ɛ̃ĩ';'s ɛ̃ĩ' Khoina-253_iron-1;Jerigaon-253_iron-1
bodtkhobwa ɛ̃ĩː 'h ə r ɛ̃ĩː' Jerigaon-392_rib-1

Wikipedia reference

On Wikipedia (https://en.wikipedia.org/wiki/Kho-Bwa_languages), this CLDF dataset is referred to as:

Johann-Mattis List, Mei Shin Wu, Robert Forkel, & Tiago Tresoldi. (2019). lexibank/bodtkhobwa: Lexical Cognates in Western Kho-Bwa (Version v2.0) [Data set]. Zenodo. doi:10.5281/zenodo.3537604

This should be:

Timotheus A. Bodt, & Johann-Mattis List. (2019). CLDF dataset derived from Bodt's "Lexical Cognates in Western Kho-Bwa" from 2019 (Version v2.0) [Data set]. Zenodo. http://doi.org/10.5281/zenodo.3537604

Workflow for work with Tim

Here is how I envision the work

  • First check of the data
    • convert to a preliminary wordlist for edictor
    • find missing words, so they can be added later (if needed)
    • make a preliminary orthography profile to see where we are with the data (and manually correct it)
  • Work on the language list and link languages to glottolog (so we have their coordinates)
  • link the concepts to concepticon (also to filter out cases where we have, e.g., "run1" and "run2"
  • use the new concepts to make a wordlist for edictor that can then be manually edited
    • apply rudimentary partial cognate detection to it (@monpasang, maybe read our paper with Nathan Hill on this matter, so you understand)
    • refine the partial cognates
  • work (computer-assisted) on the identification of language-internal cognates with edictor (maybe make one automatic investigation first), in order to identify cognates across meanings
  • apply the correspondence pattern detection algorithm, and output the patterns, so this can be used for semi-automatic reconstruction
  • make an initial version of the data for the lexibank repository, so @MacyL can see how we handle conversion to CLDF

In general, this is what I hope we can achieve in the week with @monpasang, but even if it's less, it will be a lot what we can do, as the data is in a good state.

Name of author

My name is Timotheus Adrianus Bodt. Not Timothaeus Adrianus Bodth.

Additional references

This CLDF dataset was also used to come to the following articles, which should be mentioned in the repository on Zenodo:

Bodt, Timotheus Adrianus (accepted, 2021). The Duhumbi perspective on Proto-Western Kho-Bwa onsets. Journal of Historical Linguistics.

Bodt, Timotheus Adrianus. 2019. The Duhumbi perspective on Proto-Western Kho-Bwa rhymes. Die Sprache 52 (2016 / 2017) 2: 141-176.

semi-automatic reconstruction

Ideally, we do this on Friday, have to prepare on Thursday. Once correspondence patterns are determined, we use the workflow of the work with Nathan to produce semi-automatic reconstructions for the data. Ideally we also have the tiers-check prepared, so we can make a first test here with @tresoldi (decision trees not needed yet).

add glottolog code to the languages

If there are no glottocodes, add the coordinates. The filee is here, editing is also possible via github (just press the edit button). Tim Bodt should do this, once he's told me his github account.

new link for edictor

I recommend to use the following link:

http://edictor.digling.org/?remote_dbase=khobwa.sqlite3&file=khobwa&basics=DOCULECT|CONCEPT|VALUE|FORM|TOKENS|STRUCTURE|MORPHEMES|CROSSIDS|ROOTIDS&root_formatter=CROSSIDS&highlight=TOKENS|ALIGNMENT&sampa=SEGMENTS#customize_anchor

or to copy the link from here

http://edictor.digling.org/?remote_dbase=khobwa.sqlite3&file=khobwa&basics=DOCULECT|CONCEPT|VALUE|FORM|TOKENS|STRUCTURE|MORPHEMES|CROSSIDS|ROOTIDS&root_formatter=CROSSIDS&highlight=TOKENS|ALIGNMENT&sampa=SEGMENTS#customize_anchor

and paste it into the browser (google wil also work)

@monpasang, please use this link, and we can even tweak it with more custom settings.

Refine automatic linking of concepts to concepticon

We just automatically linked the concepts of the file by Tim to concepticon. Now they need to be refined. Tim will work on this (approx. about 2 hours of work). The file is here, but this time, it is recommended to work on spreadhseet editor and not online.

Funding agency

This work was funded by

Schweizerischer Nationalfonds zur Förderung der Wissenschaftlichen Forschung: Strategische Zielsetzungen im Subkontinent (100015_138331)

and

Schweizerischer Nationalfonds zur Förderung der Wissenschaftlichen Forschung: ‘Reconstruction of Proto-Western Kho-Bwa’ (Early Postdoc.Mobility-Stipendium Nr. P2BEP1_181779)

among others.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.