[UI] Possible input combinations to SHACL UI processor

[edmondchuc]

SHACL UI may operate in different modes - such as search or query - to support various UI use cases. Each may require different inputs to the traditional form use case.

This section focuses specifically on the form mode.

At a minimum, a SHACL UI processor requires the following inputs:

• data graph
• shapes graph
• focus node
• node shape

In form mode, SHACL UI uses the focus node as the primary resource to render, and the node shape as the root definition, applying its own constraints - as well as any other connected shapes - to generate the form.

In some scenarios, an application may allow the user to choose which node shape to apply to a form. To support this, the system needs a function that determines which node shapes are valid for, or targets a given focus node, based on the data and shapes graphs. This process may occur before supplying the required inputs to the SHACL UI processor.

Another possible input combination is to provide a data graph, a shapes graph, and a focus node, and let the SHACL UI processor determine the most suitable root node shape to apply to the form. However, this approach might not be feasible in practice, as it introduces significant complexity and places additional burden on UI implementors.

What other input combinations should we consider?

[tfrancart]

What other input combinations should we consider?

In query UI scenario such as sparnatural:

1. There are no focus node as input
2. there can be multiple "entry point" node shapes
3. the "entry point" node shapes are determined automatically by looking for node shapes for which at least one non-deactivated property shape is attached and that are not themselves deactivated
4. having a standardized mechanism to list "entry point" node shapes would be good