data-interoperability-panel
data-interoperability-panel copied to clipboard
solid
Repository for the Solid Data Interoperability Panel
A section must be added on how the interoperability specification supports various discovery patterns, and what the considerations are (good and bad) for different mechanisms. - Must include legacy support...
Access needs and data grants only support requesting and granting access to a given data registration at the top level of the registered shape tree. However, there are cases where...
Based on question in today's presentation. I think new shape trees shouldn't be added silently, if user doesn't have existing one it should be asked for explicit consent to add...
Hello! I notice that the interoperability vocabulary is currently published here: https://solid.github.io/data-interoperability-panel/specification/interop.ttl based on the (WIP) Inrupt vocabulary guidelines (https://github.com/inrupt/public-documentation/pull/10/files) and the other solid vocabularies I think that it will...
What ontologies should be used when returning a GET on a LDP Container? Currently there are a number of ontologies used, but they are not very satisfactory. Here is an...
Issue created following conversation in December 8th Interop Panel: Suggestion to add a statement `interop:updatedBy` to pair with the existing `interop:updatedAt` statement when a DataRegistration is updated.
I'm keeping coming back to the ODRL Information Model: https://www.w3.org/TR/odrl-model/ . I'm logging this so that we can evaluate ODRL's fit for Solid. Or something pertaining to policies. This is...
Shape Trees Specification defines [discovery of container Shape Tree Metadata](https://shapetrees.github.io/specification/spec#discover) using specific link relation. Solid server would be responsible for naming this resource and managing it as one of auxiliary...
I'm not sure if another panel would be more suitable but defining error messages in RDF possibly with a specific HTTP headers came up a number of times in the...
[3.2. Limiting access by client application](https://solid.github.io/data-interoperability-panel/ecosystem/#client-limit) states > In the case of a strongly identifiable server-side application, the authenticated agent and the client application are the same. The client application...