[UI] Support for complex SHACL property paths in edit mode

[edmondchuc]

Within the UI, features such as property paths and widgets can function in view mode, edit mode, or both. The UI Task Force would like to gather feedback from the wider working group on whether complex property paths should be supported in edit mode.

We are considering the following as complex property paths:

• sequence path
• zero-or-more path
• one-or-more path
• zero-or-one path

For background information, see this issue: #534 (comment)

We look forward to your thoughts, use cases, and suggestions on how (or why) these complex property paths should be supported in edit mode.

[HolgerKnublauch]

No, I don't think we can support that. There are usually intermediate nodes needed to walk those paths, and those would need to be edited too. I think it's easy enough to explain to users that only direct and named inverse properties are editable, all others are read-only.

[bergos]

Edit mode can be sub-divided into create new and edit existing. We should keep that in mind, as editing an existing triple is much easier than creating a new one with complex property paths.

Nevertheless, I agree with @HolgerKnublauch proposal. That's what should be defined as MUST. But I guess we don't want to forbid anyone trying to create UIs for complex property paths. It's up to the implementer if the UI is usable at the end or not.