Missing support for sh:or, sh:xone, sh:hasValue, sh:qualifiedValueShape, ...

[dennisvang]

The current FDP client has only limited support for generating forms based on metadata-schema definitions in SHACL and DASH.

This is inconvenient, because it forces users to come up with complicated workarounds.

Here are some unsupported features I encountered, but there are probably many more:

• sh:or and sh:xone with propertyshapes
• sh:hasValue (I would expect this to result in a hidden form field with fixed value)
• sh:qualifiedValueShape (in addition to missing form generation support, nested sh:qualifiedValueShapes are not parsed properly on the FDP backend side)
• multiple sh:property values with the same sh:path
• ...?