<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> Hi, <div class=""><br class=""> </div> <div class="">Thanks, Stephan for migrating the guide to the Wiki. This is very useful.</div> <div class="">I quickly read though the webpage and I have no immediate suggestion. I guess that the recommendation about language codes is just a recommendation and that we can keep, for example, two-letter codes in case this is established for a certain resource. For example, in OPUS I use them and it would mean a major change in certain scripts to move to 3-letter codes (even though I would probably like that)</div> <div class=""><br class=""> </div> <div class="">About the question with module names: It is correct that I suggested the prefix nlpl at some point and I used that in my modules so far. I don’t know if it make sense and no strong opinion from my side either. My idea was to make a distinction between nlpl-specific modules and the ones that made it into the general repository of module files. It could also flag a bit our activities to make people aware of NLPL.</div> <div class=""><br class=""> </div> <div class="">The downside is that writing the nlpl prefix can be annoying and does not add much of a value.</div> <div class="">But sometimes it makes sense to use this kind of branding. And especially because NLPL is not very established among our colleagues this could actually work to make people aware of our activities?! What’s your opinion?</div> <div class=""><br class=""> </div> <div class="">Otherwise, for me it’s fine to announce the link.</div> <div class="">We also started the software catalogue: <a href="http://wiki.nlpl.eu/index.php/Infrastructure/software/catalogue" class="">http://wiki.nlpl.eu/index.php/Infrastructure/software/catalogue</a></div> <div class="">Would that work as a starting point?</div> <div class=""><br class=""> </div> <div class="">A quick question about the placement of documentation of the OPUS activity on the wiki: I thought about placing it under “large corpora” even though this is actually another activity. But in the long run it probably makes sense to have it as a category below corpora and not on its own. Does that make sense?</div> <div class=""><br class=""> </div> <div class="">By the way, I thought about syncing at least the core XML files from OPUS to abel. Should I do that and how much space am I allowed to fill in that case? I can skip all the derived data sets like bitexts in different formats, word alignments, parsed data etc …</div> <div class=""><br class=""> </div> <div class="">See you soon in Oslo!</div> <div class=""> <div apple-content-edited="true" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""> Jörg</div> <div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""> <br class=""> </div> <div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""> <div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <span class="" style="orphans: 2; widows: 2;">**********************************************************************************************</span><br class="" style="orphans: 2; widows: 2;"> <span class="" style="orphans: 2; widows: 2;">Jörg Tiedemann</span><br class="" style="orphans: 2; widows: 2;"> <span class="" style="orphans: 2; widows: 2;">Department of Modern Languages </span><a href="http://blogs.helsinki.fi/tiedeman/" class="">http://blogs.helsinki.fi/tiedeman/</a></div> <div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div class="" style="orphans: 2; widows: 2;">University of Helsinki <a href="http://blogs.helsinki.fi/language-technology/" class="">http://blogs.helsinki.fi/language-technology/</a></div> <div class="" style="orphans: 2; widows: 2;"><br class=""> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <br class="Apple-interchange-newline"> </div> <br class="Apple-interchange-newline"> <br class="Apple-interchange-newline"> </div> <br class=""> <div> <blockquote type="cite" class=""> <div class="">On 07 Nov 2017, at 12:44, Stephan Oepen <<a href="mailto:oe@ifi.uio.no" class="">oe@ifi.uio.no</a>> wrote:</div> <br class="Apple-interchange-newline"> <div class="">colleagues,<br class=""> <br class=""> the NLPL wiki was down until mid-day yesterday :-(. i am talking to<br class=""> USIT now about avoiding longish downtimes in the future and hosting<br class=""> the wiki (and potentially other NLPL services) in a manner that makes<br class=""> it easier to migrate transparently to a replacement host, if need be.<br class=""> <br class=""> either way, i have now completed migration of the software<br class=""> installation guide to the NLPL wiki:<br class=""> <br class=""> <a href="http://wiki.nlpl.eu/index.php/Infrastructure/installation/guide" class="">http://wiki.nlpl.eu/index.php/Infrastructure/installation/guide</a><br class=""> <br class=""> i would like to announce the link to the team sometime tonight, if<br class=""> possible. martin (and others), would you have a chance to quickly<br class=""> proof-read the updated version?<br class=""> <br class=""> i noted one missing constraints which i thought we had decided to<br class=""> enforce at the kick-off, viz. that all NLPL module definitions be<br class=""> prefixed with ‘nlpl-’, .e.g. ‘nlpl-moses’ for the Moses software. i<br class=""> believe there may have been some follow-up discussion on slack, which<br class=""> i may have missed, and yves so far has omitted the NLPL prefix.<br class=""> <br class=""> i have no strong feelings either way; does anyone? joerg, you had<br class=""> originally made the prefixing proposal, i believe.<br class=""> <br class=""> cheers, oe<br class=""> <br class=""> </div> </blockquote> </div> <br class=""> </div> </body> </html>