Review Comment:
This paper is a well written description of lexvo.org, which provides an interesting hub for language-related information in the linked data cloud.
(0) Information on the data set
General information like name, URL, and version date are given, although the specific version is not available for download on the website (http://www.lexvo.org/linkeddata/resources.html).
The license under which the linked data set is available (http://www.lexvo.org/legal.html) should be mentioned in the paper.
For some data sets or code tables the sources are not clear, e.g., the ISO 639-3 code table is downloaded from its Registration Authority (SIL) (see http://www.lexvo.org/linkeddata/references.html) but this is not stated in the paper. The authors could include an overview as given on the website in the paper.
(1) Quality of the data set
Lexvo.org integrates important but scattered data sets and code tables into the linked data cloud. The quality of the source data can vary depending on the origin, the quality of Lexvo.org lies in the mapping from one the other which is sound. Some of the data sets and code tables are updated regularly. The paper currently lacks a description of how Lexvo.org keeps up with those changes, e.g., is there an automatic harvesting process, how long does it take for changes in the source data to be reflected in Lexvo.org, are there provisions for retired codes (as linked resources might still use them)?
(2) Usefulness
The current integrated set of data sources and code tables is very powerful en functions already as a hub between other linguistic data sources. The paper mentions several of these users. Some metrics and statistics on this connectivity will strengthen these claims.
Furthermore some suggestion for additional entry points/data sets:
* many older resources still use SIL Ethnologue 14 (or older) language codes, using the code tables available at http://www.ethnologue.com/ its possible to create mappings from 14 to 15 and thus to ISO 639-3; making version 14 codes available would help link in older data sets
* actually http://www.sil.org/iso639-3/ retains mapping tables for retired codes due to merges, also these codes might help to link in older data sets
* I think an entry point of full @xml:lang tags (see http://tools.ietf.org/html/bcp47), e.g., "sr-Latn-RS" represents Serbian ('sr') written using Latin script ('Latn') as used in Serbia ('RS')" would be valuable to be able to follow the information available on the various parts without the need to understand BCP 47, i.e., it would enable easier linkage to any dataset using @xml:lang
(3) Clarity and completeness of the descriptions
In general the descriptions are clear. Here is some feedback to improve the paper:
* how to group languages into families is an ongoing debate; give the reader a pointer to find the background of this grouping, e.g., http://en.wikipedia.org/wiki/Language_family or http://en.wikipedia.org/wiki/List_of_language_families
* in section 3.1.1 the steps to construct a term URI are given, a small example would help to see what is going on, e.g., just a result URL like http://lexvo.org/id/term/cmn/%E6%9C%8B%E5%8F%8B
* in section 4.5 a reference to the CMU Pronunciation Dictionary is missing
|