Item:OSWdb485a954a88465287b341d2897a84d6 /
OSW Introduction [OSWdb485a954a88465287b341d2897a84d6] | |
---|---|
ID | OSWdb485a954a88465287b341d2897a84d6 |
UUID | db485a95-4a88-4652-87b3-41d2897a84d6 |
Label | OSW Introduction |
Machine compatible name | OswIntroduction |
Statements (outgoing) | |
Statements (incoming) | |
|
|
Keywords |
Description
Introduction into the open-source software stack OpenSemanticLab: https://github.com/OpenSemanticLab/mediawiki-extensions-OpenSemanticLab
Item | |
---|---|
Type(s)/Category(s) | Tutorial |
CreativeWork |
---|
Article |
---|
Tutorial | |
---|---|
Prerequisites (required) | |
Prerequisites (optional) | |
Follow-up (recommended) | Transcend wikitext to store and edit structured & linked data OSW Python Package OSW Ontology Import Item:OSW92619b0700984fe7913e5fbbd7f194dc |
doi: https://doi.org/10.5281/zenodo.8086418
Background
KIproBatt Project Usecase
Motivation
[Edit]
OpenSemanticWorld Concept
Note: Read Transcend wikitext to store and edit structured & linked data first if you are already familiar with mediawiki
[Edit]
see also https://github.com/OO-LD/schema
[Edit]
Technology Stack
[Edit]
Why (Semantic) MediaWiki?
- already powers large public knowledge bases (Wikipedia, Wikidata)
- Provides fundmental features
- User management, OAuth / OIDC
- Multi-Language / i18n support
- API and botframeworks to automate everything
- Multi-Content-Slots and Revisions / Versioning
- Core database (SQL), multiple Triplestores (SPARQL), ElasticSearch
- One of the most powerful (yet complex) template language
- with visual editing
- other options like mustache and markdown
- > 1000 extensions: UI, data handling, custom content, etc.
- ... but it's just a container, the core JSON-based concept is highly portable
What is different to Vanilla (Semantic) MediaWiki?
- All titles are UUIDs to make same global unique and stable + to allow changing the labels easily
- Requires custom search interface (based on Skin:Citizen)
- Requires replacements for some VE tools (Links, Media, Gallery)
- Additional tools to place custom and inline editable content
- Categories become nestable dataschemas (accessable for third-party tools) and render templates for their instances (also supporting metaschemas)
- All structured data lives in the jsondata slot, templates are only used for rendering
- All semantic annotations are done per json-ld context, which can be processed by many third-party tools without any SMW knowledge
Link to Ontologies
- Ontology classes are just specific schemas / schemas represent "icons" of "real objects"
- Automatic import via python (see: Python Examples)
- Combination with data schemas, e. g. to populate autocomplete fields
- Not just a static documentation: Planned community interaction features
- Comments => Github Issues,
- Edits => Re-export => Github Pull request
Usecases and Applications
jsondata
recommended_successor |
| |||||
---|---|---|---|---|---|---|
type |
| |||||
uuid | "db485a95-4a88-4652-87b3-41d2897a84d6" | |||||
name | "OswIntroduction" | |||||
label |
| |||||
description |
|