You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Prefixes incomplete in turtle file added to the server #891
The problems are that I do not have the full URL of :something as the prefix has only # and the prefix c does not have the full IRI as the hostname is missing. Is it possible to get the full IRIs in the prefixes?
Actually, these are relative URIs, and the resolution is done by the parser, or somewhere in the app code. Usually, you will end up setting it relative to the URI of the document. In your case, following the algorithm in RFC3986, the URI of :something would be https://ph_test.solid.community/public/test.ttl#something.
This is actually pretty useful, because it allows you to write Turtle before you know the full URI of the resource that you're writing. You can do the same thing in HTML documents.
Nevertheless, since I think one man's confusion is an opportunity to improve the developer experience, what we should look into is the tool support that helps setting the base URI, if that's clear enough.
Actually, these are relative URIs, and the resolution is done by the parser, or somewhere in the app code. Usually, you will end up setting it relative to the URI of the document. In your case, following the algorithm in RFC3986, the URI of :something would be https://ph_test.solid.community/public/test.ttl#something.
I was thinking that it was something like that, but I was confused about paths starting with # and /, but got it working now (see below).
This is actually pretty useful, because it allows you to write Turtle before you know the full URI of the resource that you're writing. You can do the same thing in HTML documents.
Cool! Hadn't thought about it like that 😄
Nevertheless, since I think one man's confusion is an opportunity to improve the developer experience, what we should look into is the tool support that helps setting the base URI, if that's clear enough.
At the moment I do the GET and parse the file with the N3.Parser to which I provide the baseIRI.
Activity
kjetilk commentedon Oct 29, 2018
Actually, these are relative URIs, and the resolution is done by the parser, or somewhere in the app code. Usually, you will end up setting it relative to the URI of the document. In your case, following the algorithm in RFC3986, the URI of
:somethingwould behttps://ph_test.solid.community/public/test.ttl#something.This is actually pretty useful, because it allows you to write Turtle before you know the full URI of the resource that you're writing. You can do the same thing in HTML documents.
Nevertheless, since I think one man's confusion is an opportunity to improve the developer experience, what we should look into is the tool support that helps setting the base URI, if that's clear enough.
pheyvaer commentedon Oct 30, 2018
I was thinking that it was something like that, but I was confused about paths starting with
#and/, but got it working now (see below).Cool! Hadn't thought about it like that 😄
At the moment I do the GET and parse the file with the
N3.Parserto which I provide the baseIRI.kjetilk commentedon Oct 30, 2018
Right! I think we could make the Turtle a bit more human friendly too! :-)
pheyvaer commentedon Oct 30, 2018
Nice! 😄 Thanks for the clarifications.