Warning:
This wiki has been archived and is now read-only.
PRFO3
This is a formal objection to the fact that "SHACL syntax rules make certain shapes ill formed".
Submitted by: Peter Patel-Schneider
Description of the issue
This objection is a repeat of the previously raised CRFO1. The difference from the previously submitted FO is that more examples are given. Some of the examples deal with paths - which is a subject of a separate FO: PRFO2
Submitter is concerned that users will create such shapes in error and since the shapes will be ill formed, different SHACL processors may treat them differently causing interoperability issues. He is further concerned that detecting such ill formed shapes will add to implementation cost.
Relevant information
The syntax rules are stated in the spec clearly and unambiguously. There is no loss of functionality as a result of the rules.
In all cases, SHACL meta-shapes graphs can detect that the syntax rules are violated and shapes are ill formed. Thus, users have a readily available way to identify and fix ill-formed shapes. Implementations can also use SHACL meta-graphs to identify issues.
WG response
Lacking a real-world use case which cannot be addressed by SHACL as currently defined, WG feels that PRFO3 was addressed sufficiently in its prior incarnation as CRFO1.
