Reviews:ValentinaPresutti about NegativePropertyAssertions

ValentinaPresutti about NegativePropertyAssertions (Revision ID: 5769)

Overall suggestion (score): 1 - needs minor revision

Review Summary: This submission has the aim of solving the problem of expressing negative property assertions (NPA) in OWL 1. I have to admit I never consider this problem before, and it can be interesting to identify a way to express NPA in OWL 1, that has not such a primitive.

I think it could be interesting to have this pattern at the workshop but it is very badly described at the moment, it needs major revisions. My main concerns can be summarized as follows:

• are there use case for this? and which are? I can imagine it would be useful to identify such a logical structure in OWL 1 ontologies in order to allow a conversion to OWL 2 that replace them with NPAs.
• the author claims the OWL 1 logical expression is equivalent to the NPA provided by OWL 2. If they are equivalent, I would expect a formal proof, if the OWL 1 expression approximates the OLW 2 NPA, then I would expect at least a detailed explanation of what are the consequences of this approximation. In other words, the submission is not accurate
• the syntax used is not introduced, neither with a simple reference
• the description of the problem is to vague and with no use case,s cenarios
• the pattern is not detailed enough in all its part

Reviewer Confidence: My confidence is medium/good with respect to all aspects. I didn't consider the problem before, but had a look at the OWL 2 spec and believe I understood the logical problem.

Problems: I think that the two logical expressions are not equivalent. To assert that "i1 is not in the class of things that have value i2 for property prop" is a bit different from asserting that "i2 has not the value i2 for property prop", because in the latter case the assertion is explicit. I think that this argument should be clarified and exhaustively discussed in the pattern description. It seems to me that there is a useless bracket

Community Relevance: medium

Relation to Best Practices:

Reusability: The pattern is general as it is a logical pattern. Btw its exposition is poor and clarity is not so good. Also no documentation and use cases are provided, hence it would be not straightforward to reuse it.

Relations to Other Patterns: Not in my knowledge.

Overall Understandability: poor

Clear Problem Description: poor

Clear Relevance and Consequences: poor

Clear Figures and Illustrations: poor

Missing Information: figures, illustration, use cases, scenarios, consequences, proof.