Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It would be a lot easier to answer your question if you could show a sample of the data that you're trying to query. I can hypothesise two reasons why you say "in my RDFS file there is no URI":</p> <ul> <li>the URI's in your document are abbreviated so do not look like traditional <code>http://...</code> URI's, for example they may be in the form <code>somePrefix:some-name</code></li> <li>the value you are trying to query is attached to a so-called <em>blank node</em>, or a resource with no URI.</li> </ul> <p>In the first case, it's simply a case of expanding the prefix. In the second case, you have to construct a path to query from a node you can identify (either by name, or by its properties) to the node you are trying to query. Easy to do in either case, but harder to explain in abstract - it will be much easier if you show your actual data.</p> <p>In the comments you asked: "how can I get the URI of my RDF file?". Again I'm going to have to guess, but I presume that you are trying to reference your ontology file by URI in your program (e.g. to load it into a Jena model). There are three possibilities I can think of:</p> <ul> <li><p>you want to reference a <code>file:</code> URI; for example the ontology at <code>c:\User\fred\vocabs\foo.ttl</code> would be <code>file:///c:/User/fred/vocabs/foo.ttl</code>, whereas <code>/home/fred/vocabs/foo.txt</code> would be <code>file:///home/fred/vocabs/foo.txt</code>. Note that there are three forward-slash characters after the <code>file:</code> prefix.</p></li> <li><p>you want to reference the file via a local Apache server or similar; if your ontology is in <code>/home/fred/public_html/vocabs/foo.ttl</code> then the URI would be something like <code>http://localhost:8080/~fred/vocabs/foo.ttl</code> (details may vary depending on how you set up your server)</p></li> <li><p>you host the file in a <a href="http://joseki.sourceforge.net/" rel="nofollow noreferrer">Joseki</a> instance or similar, in which case the URI will be determined by your Joseki configuration, see the Joseki documentation for details.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload