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
cldf datasets come with a json metadata file which among other things report which tables within the dataset conform to which standards. It is probable that most cldf-datasets contain a file called "languages.csv", but it is not technically required. It is however required that the json file reports the standards and one of those may be something like:
It would be great if there existed a standardised way in R to get cldf-datasets, specify which standardised table you want and have the function check the json metadata file for which table that is.
Currently I'm doing this the slightly roundabout way over in this script by for-looping through that part of the json, increase the index and then call on the table that way. It may not be the prettiest way of going about it, but it does work :P. It would be very useful for someone like me if there was a more general and robust function for this in a CRAN-package. Such a function could either exist in a package like glottospace, or for example in Simon's rcldf.
The text was updated successfully, but these errors were encountered:
cldf datasets come with a json metadata file which among other things report which tables within the dataset conform to which standards. It is probable that most cldf-datasets contain a file called "languages.csv", but it is not technically required. It is however required that the json file reports the standards and one of those may be something like:
dc:conformsTo == "http://cldf.clld.org/v1.0/terms.rdf#LanguageTable"
It would be great if there existed a standardised way in R to get cldf-datasets, specify which standardised table you want and have the function check the json metadata file for which table that is.
Currently I'm doing this the slightly roundabout way over in this script by for-looping through that part of the json, increase the index and then call on the table that way. It may not be the prettiest way of going about it, but it does work :P. It would be very useful for someone like me if there was a more general and robust function for this in a CRAN-package. Such a function could either exist in a package like glottospace, or for example in Simon's rcldf.
The text was updated successfully, but these errors were encountered: