Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Use relative URI notation when updating text/turtle resources

See original GitHub issue

Updating a turtle file do not use relative notation

@timbl @timea-solid

I’m using a mashlib recipe and updated a preference file. The resulting file is not using relative notation nor any @prefix In NSS we were accustomed to this relative notation, which simplify operation like copy or move files on a different server.

And mostly it renders human update much more complicated.

nota : This is also a limitation on any trial to use a dual data sharing between NSS and CSS as a preparation for migration from NSS to CSS

<https://bourgeoa.ga:3000/bourgeoa/settings/prefs.ttl> a <http://www.w3.org/ns/pim/space#ConfigurationFile>;
    <http://purl.org/dc/terms/title> "Preferences file".
<https://bourgeoa.ga:3000/bourgeoa/profile/card#me> a <http://www.w3.org/ns/solid/terms#Developer>, <http://www.w3.org/ns/solid/terms#PowerUser>;
    <http://xmlns.com/foaf/0.1/mbox> <https://bourgeoa.ga:3000/bourgeoa/settings/alain.bourgeois10@gmail.com>;
    <http://www.w3.org/ns/solid/terms#publicTypeIndex> <https://bourgeoa.ga:3000/bourgeoa/settings/publicTypeIndex.ttl>;
    <http://www.w3.org/ns/solid/terms#privateTypeIndex> <https://bourgeoa.ga:3000/bourgeoa/settings/privateTypeIndex.ttl>.

Issue Analytics

State:
Created a year ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

joachimvhcommented, Jul 14, 2022

I am not sure if you are raising the turtle prefix as a separate issue

A partial match since the issue here is about both prefixes and relative URLs.

0reactions

jeff-zuckercommented, Jul 13, 2022

I am not sure if you are raising the turtle prefix as a separate issue or conflating it with this one. While prefixes in turtle files sounds good, it does not in any way solve the problem with absolute URLs. If I create a file on my localhost CSS, a .meta resource gets create with an absolute URL to the resource. If I then copy that folder to my pod, all of the absolute URLs become wrong. If there was a prefix pointing to the same absolute URL, that would not help. What would help is that in .meta had a relative URL to the resource it describes so that when I copy the resource and its .meta to another location, the .meta is still accurate. There is AFAIK no downside to this and many upsides.