Matches in ESWC 2020 for { <https://metadata.2020.eswc-conferences.org/rdf/submissions/Paper.102_Review.0> ?p ?o. }
Showing items 1 to 10 of
10
with 100 items per page.
- Paper.102_Review.0 type ReviewVersion.
- Paper.102_Review.0 issued "2001-02-03T05:34:00.000Z".
- Paper.102_Review.0 creator Paper.102_Review.0_Reviewer.
- Paper.102_Review.0 hasRating ReviewRating.1.
- Paper.102_Review.0 hasReviewerConfidence ReviewerConfidence.5.
- Paper.102_Review.0 reviews Paper.102.
- Paper.102_Review.0 issuedAt easychair.org.
- Paper.102_Review.0 issuedFor Conference.
- Paper.102_Review.0 releasedBy Conference.
- Paper.102_Review.0 hasContent "This paper describes a case study of constructing a knowledge graph for the building automation systems (BAS). The proposed work extends the Brick ontology and integrates some other ontologies to define a comprehensive vocabulary to describe various requirements and operations of automatically operating a building, in particular its HVAC system. Positives: + The paper fits very well with the conference. + The paper is well-written and easy to follow. + The examples presented throughout the paper are especially helpful in making the contributions concrete. Negatives: - The paper lacks in-depth technical discussions on the employed vocabularies and techniques. For example, I was really looking forward to seeing a detailed discussion on "transformations and calculations" using SHACL rules in Section 4, as described in the end of Section 2. However, there is no such technical discussions at all. - There is no discussion on the values realised through this proposed knowledge graph, which has apparently been commissioned and deployed in a building. Without this discussion it is hard to evaluate the practical contributions made by this paper. Detailed comments: * The figures are not clear or large enough to be seen clearly. * Many of the figures are used to present fragments of the ontology or the knowledge graph. Instead of showing them as UML-like figures, I suggest actual definitions of these classes, for example in the DL syntax or the Manchester syntax, which is more precise and also appropriate for the ESWC community. * Pg. 5, end of 1st paragraph of Sec. 3.1, "a in the meanwhile" is wrong. * Pg. 6, where are the green arrows that are supposed to represent imports relationship? I can't see them. ====================== I thank the authors for providing the rebuttal. The rebuttal does not really address the questions raised by myself and the other reviewers. It is more a promise of what to add/address in the revision. Hence, I've decided to keep my original score."".