loki issueshttps://gitlab.geist.re/pro/loki/-/issues2017-11-08T15:06:04Zhttps://gitlab.geist.re/pro/loki/-/issues/8PROV: filemtime() error2017-11-08T15:06:04ZKrzysztof KuttPROV: filemtime() errorExemplary error:
`[Mon Jan 18 14:45:10 2016] [error] [client 149.156.96.15] PHP Warning: filemtime(): stat failed for /mnt/vhosts/loki_ia_agh_edu_pl/www/ckexp/csplib/data/attic/jezyk/comet.1453124710.txt.gz in /geist/vhosts/loki_ia_agh_...Exemplary error:
`[Mon Jan 18 14:45:10 2016] [error] [client 149.156.96.15] PHP Warning: filemtime(): stat failed for /mnt/vhosts/loki_ia_agh_edu_pl/www/ckexp/csplib/data/attic/jezyk/comet.1453124710.txt.gz in /geist/vhosts/loki_ia_agh_edu_pl/www/ckexp/csplib/lib/plugins/prov/action/prov.php on line 272, referer: http://loki.ia.agh.edu.pl/ckexp/csplib/jezyk:comet?do=edit`
* Error in line 272 where filemtime() is called?
* It is also generating a lot of `E_WARNING` that are put to the main Apache error.log: catch them or save them in some PROV-related log?https://gitlab.geist.re/pro/loki/-/issues/19PROV: metrics before and after change -- these are the same values?2017-12-03T23:27:31ZKrzysztof KuttPROV: metrics before and after change -- these are the same values?PROV plugin calculates some metrics before and after page change (to see what difference was made by the change). I reviewed some values in the PROV files and it seems that **values before and after change are the same**!
Two options:
1...PROV plugin calculates some metrics before and after page change (to see what difference was made by the change). I reviewed some values in the PROV files and it seems that **values before and after change are the same**!
Two options:
1. I looked only at changes that do not affect semantics (metrics are calculated based on semantics) and everything is ok;
2. metrics before or metrics after are not calculated properly -- which ones and how to fix it?
Needs some investigation.
Edit 11.08.2017: Also, there is no need to calculate the metrics twice for each change. They could be calculated once (in some "critical section" if it is possible on the PHP level), then saved somewhere and compared to the previously saved values.https://gitlab.geist.re/pro/loki/-/issues/24PROV: scale metrics to [1,5] range and add weightedAverage2017-11-08T15:01:33ZKrzysztof KuttPROV: scale metrics to [1,5] range and add weightedAverageProbably the DokuWiki config option will be good for specifying the way how the weightedAverage metric should be calculated (e.g. as string "`-0.5*ENR+AR+CR`" or formulae will be hard-coded and user will only select from the available op...Probably the DokuWiki config option will be good for specifying the way how the weightedAverage metric should be calculated (e.g. as string "`-0.5*ENR+AR+CR`" or formulae will be hard-coded and user will only select from the available options)https://gitlab.geist.re/pro/loki/-/issues/37PROV: selected values are not saved for preview2017-11-08T15:01:11ZKrzysztof KuttPROV: selected values are not saved for previewSelect some values for whatWasDone and whyWasDone and enter some URIs for resources field.
Click "preview".
Preview is loaded, but the PROV options are removed and you have to enter them one more time...Select some values for whatWasDone and whyWasDone and enter some URIs for resources field.
Click "preview".
Preview is loaded, but the PROV options are removed and you have to enter them one more time...https://gitlab.geist.re/pro/loki/-/issues/46provviz: does not work for dokuwiki internal nice URLs2017-12-04T01:33:18ZKrzysztof Kuttprovviz: does not work for dokuwiki internal nice URLshttps://gitlab.geist.re/pro/loki/-/issues/50provviz: does not work with nice URLs2018-03-11T22:05:53ZKrzysztof Kuttprovviz: does not work with nice URLsIf nice URLs are set to `DokuWiki internal`, provviz generates not valid links for images: `WIKI/doku.php/lib/exe/fetch.php?media=provvis:start.svg` instead of `WIKI/lib/exe/fetch.php?media=provvis:start.svg`If nice URLs are set to `DokuWiki internal`, provviz generates not valid links for images: `WIKI/doku.php/lib/exe/fetch.php?media=provvis:start.svg` instead of `WIKI/lib/exe/fetch.php?media=provvis:start.svg`https://gitlab.geist.re/pro/loki/-/issues/40PROV: whatWasDone and whyWasDone -- ideas for usability improvements2017-11-23T22:33:08ZKrzysztof KuttPROV: whatWasDone and whyWasDone -- ideas for usability improvements1. There is no possibility to select many options in one change.
2. Introduction of relations between Change and Goal subclasses in the ontology. E.g. `:TyposOrOtherSmallBugsFixed` are almost always done in order to do `:ErrorsFixing`
3....1. There is no possibility to select many options in one change.
2. Introduction of relations between Change and Goal subclasses in the ontology. E.g. `:TyposOrOtherSmallBugsFixed` are almost always done in order to do `:ErrorsFixing`
3. Recommendation mechanism (e.g. machine learning model or statistical model) that propose actual change and goal based on the characteristics of the change.https://gitlab.geist.re/pro/loki/-/issues/30RDFeditor: in Chrome "Loading" does not disappear after model loading2017-11-08T15:05:37ZKrzysztof KuttRDFeditor: in Chrome "Loading" does not disappear after model loading1. Use Chrome web browser
2. Select "RDF content:"
3. Enter some RDF file
4. Click "Build model"
5. Model is presented after a while, but "Loading" and grey overlay does not disappear
There is no problem in Firefox web browser.1. Use Chrome web browser
2. Select "RDF content:"
3. Enter some RDF file
4. Click "Build model"
5. Model is presented after a while, but "Loading" and grey overlay does not disappear
There is no problem in Firefox web browser.https://gitlab.geist.re/pro/loki/-/issues/53rdfloki does not work when lokiontology plugin is active2018-09-16T15:49:59ZKrzysztof Kuttrdfloki does not work when lokiontology plugin is active"show graph" button (rdfloki) is not displayed when lokiontology plugin is installed and active"show graph" button (rdfloki) is not displayed when lokiontology plugin is installed and activehttps://gitlab.geist.re/pro/loki/-/issues/36rdf:type is not considered a relation for SPARQL queries2017-11-08T15:02:14ZKrzysztof Kuttrdf:type is not considered a relation for SPARQL queriesSPARQL query:
```<pl format="sparql">
SELECT ?page ?rel ?obj
WHERE {
?page ?rel ?obj .
}
</pl>```
should list all triples in the wiki, but it does not list the category statements (`page a category .`).
To gather them, one should...SPARQL query:
```<pl format="sparql">
SELECT ?page ?rel ?obj
WHERE {
?page ?rel ?obj .
}
</pl>```
should list all triples in the wiki, but it does not list the category statements (`page a category .`).
To gather them, one should prepare a query that ask especially for them:
```<pl format="sparql">
SELECT ?page ?obj
WHERE {
?page a ?obj .
}
</pl>```
It is a bug, because category statements should be listed by the first query.https://gitlab.geist.re/pro/loki/-/issues/47Reasoning unit tests description in Loki Tour and Loki manual2017-12-04T01:34:36ZKrzysztof KuttReasoning unit tests description in Loki Tour and Loki manualhttps://gitlab.geist.re/pro/loki/-/issues/33Reasoning unit tests do not wait until the knowledge is updated2017-11-08T14:59:42ZKrzysztof KuttReasoning unit tests do not wait until the knowledge is updatedKnowledge within Loki is updated when page is opened (if you save the page, the page is then opened and knowledge is updated).
Unit tests are executed as a hook just after the page save, so before the knowledge is updated. It's a problem ;)Knowledge within Loki is updated when page is opened (if you save the page, the page is then opened and knowledge is updated).
Unit tests are executed as a hook just after the page save, so before the knowledge is updated. It's a problem ;)https://gitlab.geist.re/pro/loki/-/issues/43Reasoning unit tests results are not saved in PROV file2017-12-04T00:09:22ZKrzysztof KuttReasoning unit tests results are not saved in PROV filehttps://gitlab.geist.re/pro/loki/-/issues/35revisionsrater: all events are named as edited in PROV file2017-11-08T14:54:42ZKrzysztof Kuttrevisionsrater: all events are named as edited in PROV fileEvents are named in PROV files accordingly to the scheme: ``lokievent:[event]_[page]_[timestamp]``, where ``event`` is one of {``created``, ``edited``, ``deleted``}. But even if the evaluated event is ``created`` (what can be seen in the...Events are named in PROV files accordingly to the scheme: ``lokievent:[event]_[page]_[timestamp]``, where ``event`` is one of {``created``, ``edited``, ``deleted``}. But even if the evaluated event is ``created`` (what can be seen in the PROV section related to this event), the revisionsrater generates the triples, where ``event`` is ``edited``.https://gitlab.geist.re/pro/loki/-/issues/23revisionsrater: even if user is logged, he/she is saved in prov file as a guest2017-11-08T15:02:38ZKrzysztof Kuttrevisionsrater: even if user is logged, he/she is saved in prov file as a guesthttps://gitlab.geist.re/pro/loki/-/issues/13Serious integration with HeaRT(Droid)2017-11-26T10:15:53ZKrzysztof KuttSerious integration with HeaRT(Droid)Serious integration with HeaRT as described in papers:
* http://loki.ia.agh.edu.pl/wiki/_media/docs:gjn2011embedding.pdf
* http://loki.ia.agh.edu.pl/wiki/_media/docs:wta2011howtoreason.pdf
[HeaRTDroid](https://glados.kis.agh.edu.pl/doku...Serious integration with HeaRT as described in papers:
* http://loki.ia.agh.edu.pl/wiki/_media/docs:gjn2011embedding.pdf
* http://loki.ia.agh.edu.pl/wiki/_media/docs:wta2011howtoreason.pdf
[HeaRTDroid](https://glados.kis.agh.edu.pl/doku.php?id=pub:software:heartdroid:start) will be a better choice than pure HeaRT? as it is written in Java and is under maintenance?https://gitlab.geist.re/pro/loki/-/issues/9Spaces in attributes names/values2017-11-08T15:25:18ZKrzysztof KuttSpaces in attributes names/valuesAdd to docs:
* Attribute name/value can have a space, and DokuWiki changes it to underscore when creates links, but for prolog space is not equal with underscore!Add to docs:
* Attribute name/value can have a space, and DokuWiki changes it to underscore when creates links, but for prolog space is not equal with underscore!https://gitlab.geist.re/pro/loki/-/issues/32SPARQL DESCRIBE queries describes ALL pages!2017-11-08T15:02:08ZKrzysztof KuttSPARQL DESCRIBE queries describes ALL pages!SPARQL DESCRIBE queries describe ALL pages with semantic annotations! Regardless of what the query is.SPARQL DESCRIBE queries describe ALL pages with semantic annotations! Regardless of what the query is.https://gitlab.geist.re/pro/loki/-/issues/49SPARQL: dot before the FILTER is required in Loki2017-12-04T16:10:18ZKrzysztof KuttSPARQL: dot before the FILTER is required in LokiIf the SPARQL query contains FILTER you have to put the dot right after the last triple before the FILTER. This is not compatible with the SPARQL definition.
```
<pl format="sparql">
PREFIX wiki: <>
SELECT ?page ?lang ?length
WHERE
...If the SPARQL query contains FILTER you have to put the dot right after the last triple before the FILTER. This is not compatible with the SPARQL definition.
```
<pl format="sparql">
PREFIX wiki: <>
SELECT ?page ?lang ?length
WHERE
{
?page a "querytest".
?page wiki:test_lang ?lang.
?page wiki:test_length ?length. <---- THIS DOT IS REQUIRED BY LOKI
FILTER (?lang!='polish')
}
ORDER BY INC(?length)
LIMIT 5
</pl>
```https://gitlab.geist.re/pro/loki/-/issues/29SPARQL SELECT query returns `no` instead of table with results2017-11-08T14:55:11ZKrzysztof KuttSPARQL SELECT query returns `no` instead of table with resultsPage text (saved as `start:xxx`):
```
~~NOCACHE~~
[[category:task| ]]
Tytuł: [[test_title:=Miejsce na twoją reklamę]]
Miejsce na treść twojej reklamy
Dane:
* Rok: [[test_year:=dzisiaj]]
* Autor: [[test_autor:=Nieznany]]
* Loka...Page text (saved as `start:xxx`):
```
~~NOCACHE~~
[[category:task| ]]
Tytuł: [[test_title:=Miejsce na twoją reklamę]]
Miejsce na treść twojej reklamy
Dane:
* Rok: [[test_year:=dzisiaj]]
* Autor: [[test_autor:=Nieznany]]
* Lokalizacja: [[test_location:=internet]]
* Język: [[test_lang:=english]]
* Długość: [[test_length:=1]]
* Inna strona: [[test_other_page::tests:loki-queries:page1]]
```
SPARQL query (in SPARQL Endpoint / within the wiki page):
```
PREFIX wiki: <>
SELECT ?p
WHERE {
?p a "task" .
}
```
Result: **no**
but should return the table with at least one page `start:xxx`