loki issueshttps://gitlab.geist.re/pro/loki/-/issues2017-11-08T15:00:58Zhttps://gitlab.geist.re/pro/loki/-/issues/31ALL: incompatible declaration of DokuWiki methods in plugins2017-11-08T15:00:58ZKrzysztof KuttALL: incompatible declaration of DokuWiki methods in pluginsAfter each page request there are many incompatibility errors for our plugins for DokuWiki, like the one below:
`[Wed Sep 20 11:30:52.372848 2017] [:error] [pid 11575] [client 192.168.1.1:56602] PHP Warning: Declaration of syntax_plugin...After each page request there are many incompatibility errors for our plugins for DokuWiki, like the one below:
`[Wed Sep 20 11:30:52.372848 2017] [:error] [pid 11575] [client 192.168.1.1:56602] PHP Warning: Declaration of syntax_plugin_code_code::handle($match, $state, $pos, &$handler) should be compatible with DokuWiki_Syntax_Plugin::handle($match, $state, $pos, Doku_Handler $handler) in /vhosts/loki_ia_agh_edu_pl/www/wiki/lib/plugins/code/syntax/code.php on line 0, referer: http://loki.ia.agh.edu.pl/wiki/docs:tour`
Probably the issue is with the `&` on the handler attribute that does not appear in the DokuWiki_Syntax_Plugin method. It is important, because it generates a lot of logs, what is not good...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/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`https://gitlab.geist.re/pro/loki/-/issues/28PROV: add xsd types to literals2017-11-08T14:59:18ZKrzysztof KuttPROV: add xsd types to literalsAdd xsd:integer, xsd:decimal, xsd:string types to literals in generated PROV files.
The types specification for literals is available @kkutt (PROV template in PhD).
Also add the xsd prefix definition to the file preamble.Add xsd:integer, xsd:decimal, xsd:string types to literals in generated PROV files.
The types specification for literals is available @kkutt (PROV template in PhD).
Also add the xsd prefix definition to the file preamble.https://gitlab.geist.re/pro/loki/-/issues/27PROV: add semantic metrics2017-11-08T14:59:09ZKrzysztof KuttPROV: add semantic metricsSemantic changes should be written down as triples:
`lokievent:{event}_{$page}_{$newRev}
loki:classesChange "{$val}"; # TODO: how many [category:] statements were added/removed (+/-)
loki:relationsChange "{$val}"; # TODO: h...Semantic changes should be written down as triples:
`lokievent:{event}_{$page}_{$newRev}
loki:classesChange "{$val}"; # TODO: how many [category:] statements were added/removed (+/-)
loki:relationsChange "{$val}"; # TODO: how many relation (to other pages)...
loki:attributesChange "{$val}"; # TODO: how many attributes (to literals)...
loki:statementsChange "{$val}"; # TODO: how many ALL statements...`
`compare_temp_semantic_data` function from commit https://gitlab.geist.re/pro/loki/commit/39e4424eda4c1d38e7ad53da761fbd338795f4f1 may be usefulhttps://gitlab.geist.re/pro/loki/-/issues/26PROV: add testsPassed information2017-11-08T15:01:51ZKrzysztof KuttPROV: add testsPassed informationFollowing triples should be created by the Loki unit tests mechanism (if the PROV plugin is available):
`lokievent:{type}_{$page}_{$newRev} loki:testsPassed
[ loki:valueBefore "{$metric_val}" ;
loki:valueAfter "{$metric_val}"...Following triples should be created by the Loki unit tests mechanism (if the PROV plugin is available):
`lokievent:{type}_{$page}_{$newRev} loki:testsPassed
[ loki:valueBefore "{$metric_val}" ;
loki:valueAfter "{$metric_val}" ] ;`
Do it the same way as revisionsrater does (triples-related code is placed in the PROV plugin and executed from the revisionsrater).https://gitlab.geist.re/pro/loki/-/issues/25PROV: change whatWasDone and whyWasDone into an ontology2017-11-08T15:01:40ZKrzysztof KuttPROV: change whatWasDone and whyWasDone into an ontologywhatWasDone and whyWasDone are currently saved as strings -> change it to ontology concepts with URIs (detailed specification has @kkutt )whatWasDone and whyWasDone are currently saved as strings -> change it to ontology concepts with URIs (detailed specification has @kkutt )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/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/21The page is not visible in the results if the query is placed on it2017-11-08T15:00:26ZKrzysztof KuttThe page is not visible in the results if the query is placed on it**Context:** The query is placed on the page `xxx`. Page `xxx` contains some semantic data.
**Problem:** Semantic data physically below the query does not exist for the query.
**To reproduce:**
1) Create the page:
```
~~NOCACHE~~
...**Context:** The query is placed on the page `xxx`. Page `xxx` contains some semantic data.
**Problem:** Semantic data physically below the query does not exist for the query.
**To reproduce:**
1) Create the page:
```
~~NOCACHE~~
[[category:querytest| ]]
Title: [[test_title:=Some title]]
Some text
Data:
* Year: [[test_year:=dzisiaj]]
* Author: [[test_autor:=Nieznany]]
* Location: [[test_location:=internet]]
* Lang: [[test_lang:=english]]
* Length: [[test_length:=1]]
* Other page: [[test_other_page::tests:loki-queries:page1]]
```
2) Put the query somewhere:
```
{{#ask: [[category:querytest]] |
?test_title=Title |
?test_year=Year |
?test_lang |
?test_location |
?test_length |
?test_other_page |
default=No results! |
mainlabel=Main label |
intro=Text before results |
outro=Text after results
}}
```
3) If the query is placed at the top, the page `xxx` does not appear in the results.
If the query is placed somewhere in the middle of the page, in the results only the annotations above the query appears
(as a result if the query is placed at the bottom everything looks fine).https://gitlab.geist.re/pro/loki/-/issues/20Add unit tests for SPARQL queries from outside2017-11-08T17:18:09ZKrzysztof KuttAdd unit tests for SPARQL queries from outsideSPARQL Endpoint can be queried from outside (using the `?query=[QUERY]&format=html` parameters). Prepare unit test(s) that will check whether it works ok.SPARQL Endpoint can be queried from outside (using the `?query=[QUERY]&format=html` parameters). Prepare unit test(s) that will check whether it works ok.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/15Automatic update link2017-08-20T09:05:12ZKrzysztof KuttAutomatic update link**Automatic update links**:
* Test how does the automatic update works: when DokuWiki shows the info that there is an update for a plugin? (time change in `plugin.info.txt` or maybe only timestamp of the zip?)
* Something like `http://...**Automatic update links**:
* Test how does the automatic update works: when DokuWiki shows the info that there is an update for a plugin? (time change in `plugin.info.txt` or maybe only timestamp of the zip?)
* Something like `http://loki.ia.agh.edu.pl/_media/downloads:loki.zip` or `http://loki.ia.agh.edu.pl/loki.zip` (as a symbolic link to `http://loki.ia.agh.edu.pl/_media/downloads:loki.zip`?)
* Remember to change the date in `plugin.info.txt` file after plugin update
Do this also for other plugins!https://gitlab.geist.re/pro/loki/-/issues/14Loki advertisement on semantic wikis pages2017-11-08T15:04:53ZKrzysztof KuttLoki advertisement on semantic wikis pagesMake Loki notes on semantic wikis pages (e.g. semanticweb.org) -- KnowWE and Semantic MediaWiki are in such catalogues so Loki should also be there :)Make Loki notes on semantic wikis pages (e.g. semanticweb.org) -- KnowWE and Semantic MediaWiki are in such catalogues so Loki should also be there :)https://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/12cat all prolog files -> how to change it? SWI-Prolog RDF library?2017-11-08T15:03:34ZKrzysztof Kuttcat all prolog files -> how to change it? SWI-Prolog RDF library?On every page save and page open (if there is `~~NOCACHE~~` macro) Loki joins all prolog files into one big file that is provided for swi-prolog.
With bigger wiki with more users it will be a problem - it will kill the server...
SWI-...On every page save and page open (if there is `~~NOCACHE~~` macro) Loki joins all prolog files into one big file that is provided for swi-prolog.
With bigger wiki with more users it will be a problem - it will kill the server...
SWI-Prolog has some useful tools for Semantic Web, especially RDF library to store and query RDF graphs -- we are not using it yet. Maybe it is a good time to start? See documentation: http://www.swi-prolog.org/web/
Check how does it work? Is it possible to update the database on-the-fly?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/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/7ASK queries, partial tables --> add next/previous page links2017-11-08T15:06:07ZKrzysztof KuttASK queries, partial tables --> add next/previous page linksASK queries, partial tables --> add `next page` / `previous page` buttons/links that reload the table without reloading the whole page (probably based on JavaScript)ASK queries, partial tables --> add `next page` / `previous page` buttons/links that reload the table without reloading the whole page (probably based on JavaScript)https://gitlab.geist.re/pro/loki/-/issues/6Change unit tests into **automatic** unit tests2017-08-20T09:05:12ZKrzysztof KuttChange unit tests into **automatic** unit testsIs there a possibility to change current unit tests into **automatic** unit tests? E.g. zip with some testing environment or Docker / sth else + put there current loki code = testing environment does everyting and return tests results?Is there a possibility to change current unit tests into **automatic** unit tests? E.g. zip with some testing environment or Docker / sth else + put there current loki code = testing environment does everyting and return tests results?