The Wagner Triangle is named after its famous creator, Sarah Wagner. The phenomen occurs mainly whenever a semantic model is extended and not remodelled due to acute lazyness of the modelling person. Furthermore it occurs when a subform is talking about a specific use of a thing in a certain context, however connects the context to the thing itself. It is a special problem with semantic modelling in WissKI due to the disambiguation feature of WissKI that specifically clears which concept in a certain path through the ontology is the target of the path.
WissKI has IIIF-Image exchange capabilities if:
- you've installed the iip-server or any other IIIF-Server
- you've installed the wisski_iip_image module
After install of the IIP Image Module you can access the manifest of any entity by changing parameters to the URL. A typical wisski entity url is:
you can simply delete everything up to the numerical entity_id and place /iiif_manifest behind it. Like:
There currently is a drupal bug: If you have your images in the public files directory without any subdirectory (what we all usually do have...) and if you have a convert command in your image style (e.g. convert to jpg - which we all usually do have) then you currently need a patch:
apply in your drupal root with
patch -p1 < 2630230.patch
In order to use this approach, WissKI defines and implements its own storage interface, which supports the loading and writing to any data sources, so-called engines, and processes the data in the usual way according to the specifications of the pathbuilder for Drupal. Thus, all mechanisms provided by Drupal can be used to display, edit and manage entities. WissKI brings a storage interface for triplestores based on SPARQL 1.1.
The focus of the WissKI project was to combine the implementation of the common data storage of the Semantic Web in the form of triples with the functionality of Drupal. An obvious approach would be as Semantic Mediawiki pursues it: all individuals correspond to their own websites and all relations correspond to data fields. If one tries to implement this directly with Drupal, then individuals in Drupal correspond to the entities, concepts to the bundles and relations to the fields.
However, CIDOC CRM itself must be implemented in the Semantic Web in general and in WissKI in particular as a computer-interpretable, formal ontology.
The current version of the WissKI software is based on the most up-to-date version of the content management system Drupal - Drupal 8 -. The functionality of Drupal can be extended and modified by third-party modules. The WissKI system is accordingly a set of subdivided into logical units modules, each bringing encapsulated functionality in the system. The modules rely on all core functionality of Drupal, so that all common features of Drupal such. maintain the user control with detailed