Changes between Version 4 and Version 5 of Taskforces/CMDI/Meeting20180405


Ignore:
Timestamp:
04/05/18 14:38:23 (6 years ago)
Author:
Twan Goosen
Comment:

notes

Legend:

Unmodified
Added
Removed
Modified
  • Taskforces/CMDI/Meeting20180405

    v4 v5  
    4646== Notes ==
    4747
     48=== !GitBook alternatives ===
     49* HackMD (Susanne)
     50    * Looks quite straightforward
     51    * Everyone has an account, there is a history
     52    * Colour scheme for collaboration.
     53    * View with markdown
     54    * Markdown comments
     55    * Syntax highlighting for code snippets
     56    * Features added in pro version probably not needed
     57    * Publishing: export to Gist
     58    * Might get more messy, no change requests
     59    * Susanne will try to import, publish
     60* !StackEdit (Thomas)
     61    * Google doc syncing worked
     62    * GitHub syncing did not work but should
     63    * Export to HTML (and PDF in 'sponsored' mode)
     64    * Thomas will test some more
     65* New !GitBook
     66 * beta.gitbook.com available now
     67 * books can be converted to new !GitBook
     68 * Twan will test with a fork of our book
     69
     70Susanne, Thomas, Twan will report at the next meeting
     71
     72=== Recommendations ===
     73* Menzo: align with generic concepts (CCR coordinators)
     74* BLAM
     75 * We will get in touch with Felix et al to see if they are interested in discussing this further
     76
     77=== Common approaches section ===
     78
     79Sections that have been worked on:
     80* Modelling for metadata conversion (merge next time?)
     81* Optimising for discoverability (perhaps turn into CAC submission)
     82* Dealing with changes
     83* Multilingual metadata
     84
     85=== Discussions ===
     86
     87* [https://www.gitbook.com/book/cmdi-taskforce/cmdi-best-practices/discussions/24 #24] priority of C13 and C14 has to be aligned (both high), Menzo will take care of this and add some text to indicate that missing concepts should be requested
     88
     89=== Planning ===
     90* 'Release'
     91 * Replace link at https://www.clarin.eu/content/cmdi-best-practice-guide with link to !GitBook (and add PDF)
     92 * Resove in-line notes and TODOs first
     93 * Any notes/todos that cannot be resolved need to be discussed
     94* Next meeting
     95 * [https://doodle.com/poll/ke5u6skkinfh6cx6 Doodle]
     96