summaryrefslogtreecommitdiff
path: root/docs/reference
diff options
context:
space:
mode:
authorCarlos Garnacho <carlosg@gnome.org>2021-08-03 17:46:02 +0200
committerCarlos Garnacho <carlosg@gnome.org>2021-08-26 14:04:24 +0200
commite9911c9771f01b701926640320b2f1f8e0b081aa (patch)
treed7c0b9b3e4c166bd2dc03fa0533abb21c46c5477 /docs/reference
parent043de63c47b983fae517be1230a0e05e972dba6e (diff)
downloadtracker-e9911c9771f01b701926640320b2f1f8e0b081aa.tar.gz
docs: Fix image locations
Diffstat (limited to 'docs/reference')
-rw-r--r--docs/reference/libtracker-sparql/tutorial.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/reference/libtracker-sparql/tutorial.md b/docs/reference/libtracker-sparql/tutorial.md
index 6be99511d..cff3d8565 100644
--- a/docs/reference/libtracker-sparql/tutorial.md
+++ b/docs/reference/libtracker-sparql/tutorial.md
@@ -21,7 +21,7 @@ triple of the form:
Or expressed visually:
-![Triple Graph](triple-graph-1.png)
+![Triple Graph](images/triple-graph-1.png)
Subject and object are 2 graph vertices and the predicate is the edge,
the accumulation of those triples form the full graph. For example,
@@ -51,7 +51,7 @@ the following triples:
Would visually generate the following graph:
-![Triple Graph](triple-graph-2.png)
+![Triple Graph](images/triple-graph-2.png)
The dot after each triple is not (just) there for legibility, but is
part of the syntax. The RDF triples in full length are quite
@@ -209,7 +209,7 @@ SELECT ?song ?songTitle ?albumTitle { ?song a nmm:MusicPiece ;
```
Stop a bit to think on the graph pattern expressed in the last query:
-![Graph Pattern](triple-graph-3.png)
+![Graph Pattern](images/triple-graph-3.png)
This pattern on one hand consists of specified data (eg. `?song` must be
a `nmm:MusicPiece`, it must have a `nmm:musicAlbum` and a `nie:title`,