assemblee-virtuelle
Use Solid recommended metadata for uploads
Instead of the non-standard predicates of semapps:File, use the ones recommended by Solid:
https://solidproject.org/ED/protocol#contained-resource-metadata
What may be difficult to handle is that the URI of the class will depend on the IANA Media Type.
http://www.w3.org/ns/iana/media-types/{+iana-media-type}#Resource
So basically we can have thousands of different classes...
i am ok for main issue but I don't see an equivalent to the semapps:file class . Only predicat and not class...What's more, I have the impression that this chapter applies to the container and not to a subject contained in the container, but it's OK to use the same predicates.
i am ok for main issue but I don't see an equivalent to the semapps:file class . Only predicat and not class...
The rdf:type is the class. It is equivalent to @type in JSON-LD and a in Turtle.
i am ok for main issue but I don't see an equivalent to the semapps:file class . Only predicat and not class...
The
rdf:typeis the class. It is equivalent to@typein JSON-LD andain Turtle.
ok, my bad. Indeed, if you need a specific class for each media type, I find that unnecessarily complex. Aren't these classes inherited from a common class to generalise?
There are more informations about URI Templates in this RFC.
You can find a description of this particular URI Template in the namespace: https://www.w3.org/ns/iana/media-types/
Example for image/png: https://www.w3.org/ns/iana/media-types/image/png#Resource
I don't really understand the Turtle description, but it doesn't seem there is a parent class. We could use the semapps:File in addition to these classes in order to more easily identify binaries.
Are you perhaps looking or something like: application/octet-stream ?
- https://www.w3.org/ns/iana/media-types/application/octet-stream#Resource
- https://www.iana.org/assignments/media-types/application/octet-stream
Another issue to consider: https://github.com/solid/solid-spec/issues/197