Setup wiki pages (in markdown syntax) for basic information as well as KM + schema documentation. Other documentation (e.g. validator, CI) will be added when those thing will be done...

Useful information:

• https://guides.github.com/features/wikis/
• https://guides.github.com/features/mastering-markdown/
• https://help.github.com/articles/about-github-wikis/
• https://github.com/showcases/projects-with-great-wikis

We need a json markup for answers that labels them as "bad" answers. In the web portal such answers can be triggers for users to come back to the question later (visual feedback). This can also be used later to identify immediate problems when judging a DMP.

Design and develop tool for the Knowledge Model validation (now just for chapter files and directory structure, but with ability to extend easily in the future).

Design & development notes:

• use of JSON schema
• interactive for users (provide options, stop at 1st error -> recheck & continue, all at once, ...)
• test cases for CI
• clear but sufficient error/warning messages
• Python 3

Requirements:

• load KM (core & localizations)
• validate chapter files with JSON schema
• check naming conventions (number of chapter in filename, name of folder, ...)
• check references and other stuff that cannot be (or won't be) done via schema
• documentation

dmpbook references are replaced by resourcepage

Write a JSON schema for Knowledge Model chapter JSON files which will fulfill following requirements:

• Single file for both core and localization
• Giving clear error messages (i.e. useful for contributors and other people)
• As much bulletproof as it can be
• Follow DRY principle
• Easily extensible (there may be need to other file "types" than chapter files)

Documentation of this JSON schema and guidelines for extending it may be needed too (in repository wiki).

If I run a copy of the wizard for my organization, I want to be able to pre-fill some answers with the "usual way we do things here" (default answer helping the user), and other answers with "the way we handle certain things in all project (fixed answer, a default the user can not change). This will require an extension to the json schema (e.g. something like a ("selected" : "default" or "selected" : "fixed") attributes for answers. Possibly something similar for text fields and other non-option answers.

Come with official name (maybe also a logo), ownership, license and create standard repository files that we should have:

• README.md
• LICENSE.md (also NOTICE file for Apache License)
• CONTRIBUTING.md

Setup Travis CI with use of repository validator (issue #1) to enable automatic validation of repository (data, schema and validator itself). And of course add badge to README file.

• Config file .travis.yml
• README.md badge (for master branch)
• Info in CONTRIBUTING.md
• Working travis-ci.org/CCMi-FIT/ds-km-core