The display of h1 headings, being the sh:name of sh:NodeShape entities that have a sh:class can be confusing or seemingly (?) inconsistent. Take the example code below. The form will show a h1 header "Aggregation level", which is nice and fine. However, when now a "Has part" is added, the header "Aggregation level" is not shown for this added shape . Expected behaviour is that it is shown here too, in a design identical to the first appearance.
Desired behaviour can be triggered by adding sh:maxCount 1 to the shape having sh:path mdto:bevatOnderdeel (replace placeholder sh:xxxmaxCount 1). Additionally, this changes the display of "Has part" in a way that makes it more consistent and logical for the user.
The display of
h1
headings, being thesh:name
ofsh:NodeShape
entities that have ash:class
can be confusing or seemingly (?) inconsistent. Take the example code below. The form will show ah1
header "Aggregation level", which is nice and fine. However, when now a "Has part" is added, the header "Aggregation level" is not shown for this added shape . Expected behaviour is that it is shown here too, in a design identical to the first appearance.Desired behaviour can be triggered by adding
sh:maxCount 1
to the shape havingsh:path mdto:bevatOnderdeel
(replace placeholdersh:xxxmaxCount 1
). Additionally, this changes the display of "Has part" in a way that makes it more consistent and logical for the user.