Resources are supposed to be identifiable with hashes (like https://mypod.store/alice#me), but SemApps never supported that until now.
To support it, we would need to adapt the ldp.resource.get action to look for hash resources sharing the same main URI. If a hash resource is found, we would need to display it like this in Turtle:
<https://srosset.inrupt.net/profile/card>
a foaf:PersonalProfileDocument;
foaf:maker <https://srosset.inrupt.net/profile/card#me>;
foaf:primaryTopic <https://srosset.inrupt.net/profile/card#me>.
<https://srosset.inrupt.net/profile/card#me>
a schema:Person, foaf:Person;
foaf:name "Sébastien".
Resources are supposed to be identifiable with hashes (like https://mypod.store/alice#me), but SemApps never supported that until now.
To support it, we would need to adapt the
ldp.resource.get
action to look for hash resources sharing the same main URI. If a hash resource is found, we would need to display it like this in Turtle:And like this in JSON-LD:
WAC permissions are applied for the whole resource.
Left issues
webacl.resource.hasRight
action ?