Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
SHACL requirements in non-normative parts of the document #57
Comments
|
I don't see anything non-normative in 2.1.5 that is not also covered by 3.6.2.7 which is normative. Please clarify, also be explicit about which other parts you think are misplaced. |
|
3.2.6.7 does not say what is supposed to be done, just that something should be done, and points to 2.1.5 for more information where the actual generation is only in a non-normative section. |
HolgerKnublauch
added a commit
that referenced
this issue
Apr 23, 2017
|
|
HolgerKnublauch |
05544dd
|
HolgerKnublauch
added Editorial (would not change implementations) Waiting for Commenter
labels
Apr 25, 2017
|
The change is fine. This is a non-editorial change in that it places more normative conditions on implementations. That said, the only problem was that the requirement was in a non-normative section of the document so I don't see any reason to hold up further progress because of this issue. |
pfps commentedApr 20, 2017
There are still aspects of SHACL that appear only in non-normative
(informative) sections of the document. For example, a part of Section
2.1.5 labelled as informative states a requirement on the values of
sh:resultMessage in validation results. This requirement is not stated in
any normative part of the document.
This issue has been previously reported.