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

Grimes (1959) set of sounds and features #10

Open
LinguList opened this issue Sep 13, 2017 · 4 comments
Open

Grimes (1959) set of sounds and features #10

LinguList opened this issue Sep 13, 2017 · 4 comments
Assignees
Milestone

Comments

@LinguList
Copy link
Contributor

This should be metadata, I suppose, as Grimes (1959) lists features for only some 40 sounds relevant for Romance languages. He also describes a metric to define distances between sounds, and this is interesting. Ideally we should also add this data, but the question is: in which form? Distances call for a matrix, but csv is not really apt for matrices, due to the large number of column names. JSON could handle this. In any way, this will call for a custom script to create the data, based on features of Grimes, linkings, some description, a csv file with the sounds and our feature names, and the matrix in JSON. Question is again, how to do this in the most consistent way. We may decide for some json file with metadata that contains the additional information AND the table information for CSV, @xrotwang, is this possible in the current cldf spec?

@LinguList
Copy link
Contributor Author

bildschirmfoto_2017-09-13_10-18-54

This is an example of the data... Feature-based distance calculation is based on getting the difference between vectors (using the integers as numerical values).

@xrotwang
Copy link
Contributor

I'd say csv is still the best choice for a matrix. 40x40 would certainly not be too much.

@LinguList
Copy link
Contributor Author

alright, as long as I don't need to specify column names in the metadata-json, this is okay, but I assume, that this can be handled, right?

@xrotwang
Copy link
Contributor

yes, there's a default naming algo, and column types can also be declared for all columns at once.

@LinguList LinguList changed the title Adding Grimes (1959) set of sounds and features [Transcription Data]: Grimes (1959) set of sounds and features Jan 4, 2018
@LinguList LinguList self-assigned this Jan 4, 2018
@xrotwang xrotwang changed the title [Transcription Data]: Grimes (1959) set of sounds and features Grimes (1959) set of sounds and features May 17, 2018
@xrotwang xrotwang transferred this issue from cldf-clts/clts-legacy Oct 22, 2019
@LinguList LinguList added this to the 1.3 milestone Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants