Review Comment:
The paper reads itself like a complete and clearly written manual for data.open.ac.uk (at least up to section 4). This is generally a good thing, as it is a Data Description entry for the SWJ. In the section 3 (Modeling Issues) you discuss design decisions taken for Graphs, URIs and domain modeling. The decisions are mostly grounded on the commonly accepted principles in the LD field. This is good! However I feel you should tell us much more about the technical limits and organizational debates which influenced this decisions. Meaning if you are able to share some details in this regard it might be highly valuable knowledge for other LD creation projects.
You can look back on 4 years of experiences with LD creation. This is a huge success. I especially like the classification in the second last section (rebuilt, update, sync). Again please, instead of repeating known LD principles tell us a bit about tools or at least transformation approaches which worked out for you. This experience can be valuable for other projects.
I am aware that I ask for a bit more than defined for an Data Description entry. Consider weaving in some of this unique experience in the paper. It is an excellent paper which covers the huge LD pool achieved within data.open.ac.uk.
Please correct the minor issues below:
Content
- Section 3.6: I too hate blank nodes (-, but you might base your claim on a reference: “handling blank nodes with other query types still falls short of efficiency.”
Style
- Please use a coherent style for SPARQL queries (upper/lower case) throughout the paper.
- Section 3.4 Listing “Related to”: I guess this means to show a hierarchical structure? Better no elements than as it is currently.
- Table 1, Domain: Tim excused himself once for unnecessary adding two // in the URI scheme. But you should still keep them for now. (-,
- Section 2.2: DiscOU was not introduced up to here?
- Section 4: Missing space before “For example”
Orthographic
- Section 2.1.4: data are collected FROM internal
- Section 6: The DATAARE basically ?
|