|Review Comment: |
The paper is much easier to read and my main concerns have been addressed. I've only a few minor points/questions.
The text says "Table 6 lists the 10 data sets … along with the used link predicate …" - table 6 has only the counts, not the predicates.
Table 8 - incoming links to what?
Fig. 9 - for consistency - caption should state units for both bars or none - as is, implies counts are also in GB
A few grammatical errors - should be picked up with a proof-read or auto-check.
******* Questions about responses to review
Point about improvement with use of Scala - response says rewritten - the paragraph is identical to the previous version (bar the footnote pointing to the timeline).
Re - status code 509 - my point appears to have been misunderstood - the issue isn't the code, but that it would be useful to mention in the text why this is appropriate. Only providing a URL pointing to code definitions just increases the reader's load. This is something authors (myself included) are often guilty of - forgetting that what is obvious to you, especially when you're very involved with your work, is not necessarily so to your readers.
FYI - HTTP status codes at w3 - http://www.w3.org/Protocols/HTTP/HTRESP.html
Fig 2 - my question was why the mapping example for Greek contains BOTH Greek and English labels for the mappings - I would expect them all to be Greek?
Table 7 is referenced before 6 - should therefore come before it. - response says this has been addressed - it's still the same.
Suggested references for  FREyA - rather than URL
Danica Damljanovic, Milan Agatonovic, Hamish Cunningham. (2010) Natural Language Interfaces to Ontologies: Combining Syntactic Analysis and Ontology-Based Lookup through the User Interaction. ESWC (1) 2010: 106-120
Danica Damljanovic, Milan Agatonovic, Hamish Cunningham. (2011) FREyA: An Interactive Way of Querying Linked Data Using Natural Language, In The Semantic Web: ESWC 2011 Workshops, LNCS Volume 7117, pp 125-138