|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).
(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 contains a sketch of how the update process of lexvo.org works. More details would be interesting, i.e., how is dealt with deprecated codes especially splits, but maybe in a next paper.
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
* 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. I think it would improve section 3.1.1, where the steps to construct a term URI are given, if a small example was added 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