Document dependancies

[simontaurus]

@thomas-topway-it: Please note that the edit feature depends on

• the template KB/Term + related ones and Extension:MwJson to parse templates in the legacy mode
• Extension:MwJson to edit jsondata slots and the world.opensemantic.core page package in the "new" mode

[krabina]

I am not so worried about a dependency on a template that needs setting up. Some other extensions have this, too, e. g. SemanticCite delivers a standard-template than can be customized.

But we should consider the following usecases

1. opensemanticcore is present. Than every thing is fine
2. opensemanticcore is not there. Then it is OK if the edit functionality does not work. We should just consider what is happening when it is not there. Is it automatically switched off. Is there a configuration parameter?
3. oopensemanticcore is not there and editing should be supported with a link. This link could e. g. lead to e PageForms to create a new entity with a parameter you can give it. This way, we could make the extension usable in very common setups where i displays semantic data and wen you want to add/edit anything, you can use PageForms as well.

[simontaurus]

1. / 2. Sounds like a good approach. We already have a (primitive) switch in place regarding the installed version of opensemanticcode (MwJson + OpenSemanticLab) => could be extended to detect general presence
   

   mediawiki-extensions-InteractiveSemanticGraph/modules/ext.InteractiveSemanticGraph/InteractiveSemanticGraph_init.js

   Line 24 in 39a3f7b

   defaultOptions.legacy_mode = mw.config.get( 'wgPageName' ).split(":")[0] === "Term";

2. In general a good idea. But edits in the graph could also cover multiple pages. I guess in this case multiple PageForms need to be prefilled or PageForms tabular editing is used

[gesinn-it-gea]

I wanted to test this extension on MW 1.39 and installed as follows:

wfLoadExtension( 'WikiEditor' );
wfLoadExtension( 'CodeEditor' );
wfLoadExtension( 'CodeMirror' );
wfLoadExtension( 'WSSlots' );
wfLoadExtension( 'MwJson' );
wfLoadExtension( 'InteractiveSemanticGraph' );

CodeMirror 268f838a9c176ef4655b2e2637a81b17963e16c6 wikimedia/mediawiki-extensions-CodeMirror
WSSlots 9a39063a848130030c35944dea047386315051ae Open-CSP/WSSlots
MwJson ec1a32c5d88a8dc44fdfe8cb32c2321e5d8d784b OpenSemanticLab/mediawiki-extensions-MwJson
InteractiveSemanticGraph 39a3f7be98a10642a9e33247afb3302ee0afea79 OpenSemanticLab/mediawiki-extensions-InteractiveSemanticGraph

Now, with a simple test graph, JS console says:

platform: navigator engine error! [Gecko] != [WebKit]
It seems I am running on an unknown OS.

Am I missing something?

[krabina]

You are aware that https://github.com/SemanticMediaWiki/KnowledgeGraph is an extension that was (in the first version) an extension based on what @simontaurus did in this extension, but as a standalone version easier to be used with SMW. Now it is more a complete rewrite based on the idea.

[gesinn-it-gea]

@krabina I'm aware of the KG extension but compared to this one, KG queries the data in PHP first. This makes it somehow "static".

[simontaurus]

@gesinn-it-gea

platform: navigator engine error! [Gecko] != [WebKit]
It seems I am running on an unknown OS.

This unrelated error originates from a legacy wikitext parser lib.

1. can you check for other errors or warnings?
2. In which namespace are your test pages?
3. Do you see at least the root node in the graph?
4. if you right-click on the node, do you see a API request to browse properties in the browser debug tool / network traffic?
5. if you select a property in the right-click menu, do you see a Ask-API request in the browser debug tool / network traffic?

FYI: You can inspect https://demo.open-semantic-lab.org/wiki/Category:OSW0e7fab2262fb4427ad0fa454bc868a0d as a reference

[gesinn-it-gea]

[simontaurus]

@gesinn-it-gea: There was an undeclared variable searchParam - can you test the latest version?