Is .meta discussed in any spec? I haven’t seen it. One can’t do a GET on them. Are they even files in NSS, or are they something else? Do they get created automatically when a new resource is POSTed or PUT? Or are they created on-the-fly when needed?
I am asking in relation to recursiveCopy - should it be copying .meta files from the source to the destination?
But I am not sure if that answers your question. I believe it should be copied, as it contains relevant and specific information about this resource:
“The metadata (extra RDF triples such as types, titles, comments, and so on) about non-RDF resources (e.g. containers, images, binaries, etc.) will be stored in a corresponding meta resource.”
I don’t think this information is automatically created by the server (except for some defaults maybe), so I would copy it too if possible.
This https://github.com/solid/solid-spec/issues/10 seems to give some clue how .ACL and .meta are accessible through HEADER with the same mechanism using IANA ontology to find the URI (acl or describedBy) and then if it exist you can copy it.
When copying from one pod to an other you must find in the destination HEADER the destination link that can be different from the source (depending from the implementation mechanism)
I can access .meta and .acl with solid-ide in the same way through the Url, but only if it exists and then edit them.
.meta and .acl works in the same way.
if the ressource do not exist it returns 404 error.
if exist you should be able to copy it
From trials, errors and access to the filesystem :
.meta ressource are automatically created when creating a folder with solid-ide then you can edit it with the about UI databrowser.
I did not find a way to create .meta for file ressources
nota : when creating a folder with the databrowser UI .meta are not created. What are the differences ???
Yes, currently if you PUT triples to /container/.meta, they will appear when you do a GET on /container/. These triples can apply to either the container or its contents. The databrowser uses this fact to display a container based on the triples in its metadata file.
My $0.02 - if your question is about how to do something or how the current software behaves, ask here or in the chat. If you want to discuss why things work the way they do or how they should work in the future, the github repos and W3 community group are a better location.