Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What about file storage? #240

Open
woutermont opened this issue Feb 10, 2022 · 2 comments
Open

What about file storage? #240

woutermont opened this issue Feb 10, 2022 · 2 comments

Comments

@woutermont
Copy link
Contributor

According to the specification, all data seems to be stored in Data Registrations according to Shape Trees. This would seem to preclude us from storing and accessing files like we currently can do with/in a Solid RS.

E.g. (how) would it (still) be possible to use a Solid RS as a file server, next to the differently shaped data I have on it?
E.g. (how) would it (still) be possible to serve a (static) website from a Solid RS?

@justinwb
Copy link
Member

justinwb commented Feb 10, 2022

This is a good topic to work out - glad to see this issue filed @woutermont!

I think we have a few options. We probably need to establish a best practice (at a minimum), but may want a specified avenue so it could be more explicitly supported.

One option is to use a shape tree that's fully permissive (i.e. allows any type of resource)

<#PermissiveTree>
  a st:ShapeTree ;
  st:contains 
    st:NonRDFResourceTree ,
    st:RDFResourceTree ,
    st:ContainerTree .

We could add this tree as a reserved shape tree type in the interop spec, so in a given data registry you can lookup the "open space" via that reserved shape tree and provide access to storage within. We would need to handle the access management a bit more uniquely (vs. per data instance).

Good topic for the next panel session - will include it on the agenda

@elf-pavlik
Copy link
Member

I agree that we should sort out all those issues ASAP. So far sai-js only supports Data Instances that are RDFSources, we need to add support for Non-RDFSources where we describe them via auxiliary resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants