|Interface "Notices" is constituted by properties...||...having values|
You can override settings in Vagrantfile included in the box with settings specified in
|Application "dataspects"||In order to reduce complexity, the following NOT_ selectors only select pages if all but the leftmost arguments match.
I.e. for a page to be selected by
If you want to select pages which "don't have FIELD_VALUE in FIELD_NAME" because they don't have FIELD_NAME to begin with, you have to use
|Architecture "dataspects Search"||Entities DO have annotations!|
|BlueSpice||This page lists knowledge subjects in connection with BlueSpice. It is structured based on the Ontology "BlueSpice Helpdesk Ontology".|
|Community Service "SMW Testing System (SMWTESTING)"||Please note that Community Service "SMW Testing System (SMWTESTING)" is one of my workspaces for my SMW/Cargo ontology engineering and therefore subject to sudden redesign. (You can check out part of its underlying commented/highlighted ontology blueprint on its Talk page.) But you should always be able to find your way around. URLs will not change.|
|Concept "Compiling Dataspects::Entity annotations"|
|Concept "Ontology Management Script"||Application Command "smw-cindykate content manage" makes the following variables available to ontology management scripts
|Concept "Top-Level-Ontology"||For example, the |
There is more explanation on this in Discuss UseCase "Manage MediaWiki-centric enterprise knowledge management" Use Case.
|Concept "content-/process-reference"||This will use https://www.mediawiki.org/wiki/API:Categorymembers.|
|DSKIMUnitTest||Overview "Testing smw-cindykate"|
|Domain "SMWCKMain:Factory"||This page is under heavy construction.|
|Goal "Shorten the time it takes for your new employees to get productive"||Check out our blog article Knowledge Management: Flying only got successful once people stopped imitating birds (in German)|
|Idea "MWStake Trusted Web of Colleagues (TWebC)"||Please note that the following very rudimentary assertions are examples for my constantly evolving TWebC terminological ontology. Concepts here undergo regular dramatic change! :)|
|KIM/SMW Academy Literature||The mindmaps shown below have been created and are managed by myself (thus they do not reflect the corresponding authors' conceptual/mental prioritization or organization). They serve as:
|Ontology Management Script "manage_DMP.rb"||OMS contain instructions to run in accordance with UseCase "Programmatically manage SMW pages' content/wikitext and metadata".|
|Overview "Testing smw-cindykate"||The following pages serve as unit test scripts and corresponding test objects/pages requested from within the RSpec Ruby code by API calls to this MediaWiki. While this mechanism turns these pages into a comfortable documentation about smw-cindykate's functionality, it also makes testing prohibitively slow.
The idea is to compile these pages into a YAML package dumped into smw-cindykate's RSpec testing suite before running them.
|Practice Pattern/Workflow "Keywording"||Practice Pattern/Workflow "Keywording" will substantially change when adding Elasticsearch by mid-2016. That's why these explanations are rudimentary for the time being.|
|Recipe "DNA and genesis of a Vagrant Box ("VBubuntu") ready for hosting a SMW"||This is pragmatic behaviour. Of course these aspects shall be solved and moved into the Packer build context.|
|Recipe "How to create, configure, export and import GnuPG keys"||
944CBA14 is the key-id
|Recipe "How to install the VirtualBox Guest Additions"||
|Recipe "How to turn an idea into a certified SMW extension"||The following instructions have been tested on Ubuntu 16.04 64bit.
Instructions for other platforms are under construction.|
At the end of this process your VBox VM "MediaWiki Vagrant" is ready for the next steps. If you want to log into the VM's XFCE desktop, see below Log into the VM's XFCE desktop.
These instructions are under construction.
|SMW Facet Profile "SMW CindyKate Main Terminological Ontology (SMWCK-MTO)"||This graph visualizes SMW CindyKate's ontology on April 1st 2016 (i.e. not real-time) based on component type properties. It is programmatically generated using mermaid.|
|Setup "Develop dataspects on a VirtualBox VM on another computer"||MySharedFolderSHARENAME must be different from MySharedFolder!|
|Setup "Dropbox headless client as a service"||Solution Hint "Set ForwardX11 to "no" when starting Dropbox daemon through SSH connection"|
|Showcase "Using Cargo and mermaid to derive NASA's FPIP from SMW-managed semantic data"||For the time being, it seems that Firefox is rendering mermaid graphs/charts reliably.|
The tool used is mermaid's online graph editor.
You see that we semanticize data using both SMW and Cargo. The reason for this is explained further down.
Also, the abstraction structure is not optimal yet, but remember Donald Knuth's Principle "Premature optimization is the root of all evil". :)
|Technique "Vector Quantization"||See Publication "How to create a mind", page 135.|
|TestsAreRunBy||Overview "Testing smw-cindykate"|
|Type "Facet/Interface"||For example, the facet/aspect "safety" of a car cannot be instantiated like "This is safety A and that is safety B.". But the facet/aspect "safety" can enfold the instantiations of seatbelt model 24 and airbag RT45.|
|UseCase "Flexibly select SMW pages by content reference"||UseCase "Flexibly select SMW pages by content reference" is part of Application "dataspects".|
|UseCase "Inject SMW pages from text files"||UseCase "Inject SMW pages from text files" is part of Application "dataspects".|
|UseCase "Programmatically manage SMW pages' content/wikitext and metadata"||UseCase "Programmatically manage SMW pages' content/wikitext and metadata" is part of Application "dataspects".|
|UseCase "Set up BlueSpice MediaWiki Enterprise Distribution"||These instructions install the entire BlueSpice stack onto a MediaWiki 1.27 on an Ubuntu Server 14.04.01.|
|Workflow "How to model a business domain in SMW from scratch"||Your attitudes are equally important as your skills are.|
A documentation is not a document, but it can be.
Be object oriented before being class oriented.