Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop categories for known source gaps #333

Open
bambooforest opened this issue Mar 29, 2021 · 3 comments
Open

Develop categories for known source gaps #333

bambooforest opened this issue Mar 29, 2021 · 3 comments
Assignees

Comments

@bambooforest
Copy link
Contributor

See #332

@camoverride
Copy link

@bambooforest - will CLDF be the main resource for tracking known issues with the phoible source material? I'm wondering if I should invest time digging into this.

@bambooforest
Copy link
Contributor Author

@camoverride -- it would be great to get some feedback. we do all of our dev work in this repository, so this is the most up-to-date data with corrections, etc.:

https://github.com/phoible/dev/tree/master/data

so you should use this.

when we've made significant changes that warrant a new version, we generate the new version in this repository and generate the CLDF data, which gets archived in Zenodo as CLDF and also here for the website:

https://github.com/cldf-datasets/phoible

@bambooforest
Copy link
Contributor Author

Some things to keep in mind here (not exhaustive):

  • UPSID does not have allophones (but does mark marginals)
  • AusPhon consistently does include any marginals

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants