First draft of shui:readOnlyGraph

[robert-david]

• See this document rendered online here

[danielbeeke]

Looks good to me. I think in the further conversation about it we can talk about conformance. For now I think it is okay.

[smessie]

I had hoped to see this discussion in an issue first, but I can still share my thoughts in this PR.

My primary concern, or rather question, is why we need this feature.
Currently, I understand that we have all the necessary inputs (such as data graphs, shapes graphs, scoring graphs, etc.) as parameters on a software level.
Supporting a read-only graph in the SHACL UI would simply mean adding another input parameter that is a read-only graph.

Could you please clarify the purpose of this additional global configuration parameter?

[danielbeeke]

its a good question.

I think there are at least the following alternatives:

• Add an argument "Read only graphs" to various interfaces that required a list of IRIs such that when quads are handled implementers can check if the quad in question is part of a read only graph
• Add an argument "Read only graphs" to various interfaces that required a list of Graphs (similar to data graph and shapes graph, implementations could use rdfjs store etc.) such that these specific graphs can be only used when we for example are doing autocomplete search.

[edmondchuc]

I am in favour of a read-only graph for the following use cases, some of which have already been mentioned by @robert-david and @danielbeeke in this PR.

A read-only graph would allow applications to use non-editable triples as contextual information, whether that's for autocomplete search, facts produced by reasoning, or contextual information that the user has the permission to read but not edit.

However, I also agree with you, @smessie, that this should probably be another input parameter to the SHACL Renderer rather than a global configuration parameter.

[bergos]

We're overcomplicating this. We should simply define the property and allow each implementation to decide how it's used.

[robert-david]

I had hoped to see this discussion in an issue first, but I can still share my thoughts in this PR.

My primary concern, or rather question, is why we need this feature. Currently, I understand that we have all the necessary inputs (such as data graphs, shapes graphs, scoring graphs, etc.) as parameters on a software level. Supporting a read-only graph in the SHACL UI would simply mean adding another input parameter that is a read-only graph.

Could you please clarify the purpose of this additional global configuration parameter?

Sorry for not opening an issue first. Is was mixed up with #869. I created #1197 for this now.

The reason for the readonly-graph is to have a configuration to point out read-only data to the UI. Given that SHACL only defines a data graph, i think we should specify how such read-only data can be communicated to SHACL UI to keep it uneditable, i.e. manage such data accordingly. The main use case is inferred data, since SHACL defines to be compatible with reasoning, such as defined by the OWL profiles.