You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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).
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?
The text was updated successfully, but these errors were encountered: