GeezerVison

I can't remember now but does NSS allow non-root path to be storage root? If so, does the code take that into account?

NSS only allow subdomain. Storage starts at root path.

Ok, great. If you review / approve, we should merge this.

@csarven @SarthakDudhe

From https://solidproject.org/TR/protocol#storage-description-statements
I think that root/.meta must include the triple

</> a <http://www.w3.org/ns/pim/space#Storage> .

Which is not actually the case.

If this is correct it implies to

• update default root/.meta
• prepare a migration script for existing servers

In NSS, it'd be (the slash for the storage resource):

</> a <http://www.w3.org/ns/pim/space#Storage> .

I don't understand why a migration script is necessary (although I understand it'd be useful to do).

Thanks yes you are right I have updated above.
Why a migration ? This is because the triple is created at pod creation. On existing server you need to update all existing pods.
We add the same issue when Solid spec introduced pim:storage or solid:oidcIssuer in profile/card

@bourgeoa Could you please confirm if NSS only allows storage root to be / after hostname? If so, that should address my inquiry in my earlier comment.

NSS only allow subdomain pods.

@bourgeoa Anything else remaining besides the migration script to include a pim:Storage in storage description (/.meta)? This PR only covers the storage description link discovery. Could the Storage statement be left for a separate PR?

@SarthakDudhe @csarven
what is missing is updating the templates files

• default-templates/new-account/.meta
• config/templates/new-account/.meta