|Review Comment: |
# Review of the revised version of "A Linked Data Wrapper for CrunchBase"
**Summary: The major issues have all been adressed . Still, the SPARQL endpoint is missing and I don't agree with the reasoning to not provide one. Maybe the editors can clarify whether a SPARQL endpoint is truly optional? Until then, I upgrade my recommendation from reject to minor revision. Version date and number also should be added, as requested in the call.**
## Quality and stability of the dataset
The URL is provided now but version date and number are still missing.
The licensing of the RDF dataset has been clarified.
I do not agree with the the reasoning of why a SPARQL endpoint, which has been requested by all three reviewers, is still not provided.
1. "SPARQL endpoints suffer from availability issues": A non-existent SPARQL endpoint has 0% availability, so any endpoint you provide is better than none at all. I thank the authors for linking the very informative paper "Linked Dataset Description Papers at the Semantic Web Journal: A Critical Assessment" and it indeed highlights common technical issues, but I do not find the suggestion to remove the SPARQL endpoint altogether there, nor do I find this an acceptable solution to the problem.
2. "SPARQL endpoints are prone to complex queries which might affect the SPARQL endpoint performance or even might result in downtimes of the endpoint." This argument is related 1., as it is also concerned with availability issues.
## Clarity and completeness of the descriptions.
> Nowack already provided an RDF wrapper for the CrunchBase API called Semantic CrunchBase in 2008, the service is no longer available.
A (blog entry)[(http://bnode.org/blog/2008/07/29/semantic-web-by-example-semantic-crunch...)] for Semantic CrunchBase states “The initial RDF dataset is not using any known vocabs such as FOAF (or FOAFCorp). (We can INSERT mapping triples later, though.)”.
This is a major issue. According to the above statements, the existing approach could be extended with “mapping tiples” to integrate vocabularies. A thorough motivation, why this existing approach was not extended but a completely new approach was taken, is essential.
### Unproven Statements
The vague and unproven statements have been clarified and provided with sources. While those sources are mailing list posts and text from the Crunch Base web page instead of citable publications, I rate this as acceptable in this cause because this is probably the only way to get this information.
### Factual Errors
#### 5 Star Ranking
The Linked Data vocabulary star rating has been added and correctly applied.
#### JSON to RDF
The missing reference for the papers that transform JSON to RDF has been added.
### Formal Criteria and Writing
The writing is clearer and less verbose now and the paper now adheres to the 10 page limit.