1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from June
2017</title>
5 <description>Entries from June
2017</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Updated sales number for my Free Culture paper editions
</title>
11 <link>http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html
</guid>
13 <pubDate>Mon,
12 Jun
2017 11:
40:
00 +
0200</pubDate>
14 <description><p
>It is pleasing to see that the work we put down in publishing new
15 editions of the classic
<a href=
"http://www.free-culture.cc/
">Free
16 Culture book
</a
> by the founder of the Creative Commons movement,
17 Lawrence Lessig, is still being appreciated. I had a look at the
18 latest sales numbers for the paper edition today. Not too impressive,
19 but some buyers still exist. All the revenue from the books are sent
20 to the
<a href=
"https://creativecommons.org/
">Creative Commons
21 Corporation
</a
>, and they receive the largest cut if you buy directly
22 from Lulu. Most books are sold via Amazon, with Ingram second and
23 only a small fraction directly from Lulu. The ebook edition is
24 available for free from
25 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Github
</a
>.
</p
>
27 <table border=
"0">
28 <tr
><th rowspan=
"2" valign=
"bottom
">Title / language
</th
><th colspan=
"3">Quantity
</th
></tr
>
29 <tr
><th
>2016 jan-jun
</th
><th
>2016 jul-dec
</th
><th
>2017 jan-may
</th
></tr
>
32 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">Culture Libre / French
</a
></td
>
33 <td align=
"right
">3</td
>
34 <td align=
"right
">6</td
>
35 <td align=
"right
">15</td
>
39 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Fri kultur / Norwegian
</a
></td
>
40 <td align=
"right
">7</td
>
41 <td align=
"right
">1</td
>
42 <td align=
"right
">0</td
>
46 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">Free Culture / English
</a
></td
>
47 <td align=
"right
">14</td
>
48 <td align=
"right
">27</td
>
49 <td align=
"right
">16</td
>
53 <td
>Total
</td
>
54 <td align=
"right
">24</td
>
55 <td align=
"right
">34</td
>
56 <td align=
"right
">31</td
>
61 <p
>A bit sad to see the low sales number on the Norwegian edition, and
62 a bit surprising the English edition still selling so well.
</p
>
64 <p
>If you would like to translate and publish the book in your native
65 language, I would be happy to help make it happen. Please get in
71 <title>Release
0.1.1 of free software archive system Nikita announced
</title>
72 <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html
</link>
73 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html
</guid>
74 <pubDate>Sat,
10 Jun
2017 00:
40:
00 +
0200</pubDate>
75 <description><p
>I am very happy to report that the
76 <a href=
"https://github.com/hiOA-ABI/nikita-noark5-core
">Nikita Noark
5
77 core project
</a
> tagged its second release today. The free software
78 solution is an implementation of the Norwegian archive standard Noark
79 5 used by government offices in Norway. These were the changes in
80 version
0.1.1 since version
0.1.0 (from NEWS.md):
84 <li
>Continued work on the angularjs GUI, including document upload.
</li
>
85 <li
>Implemented correspondencepartPerson, correspondencepartUnit and
86 correspondencepartInternal
</li
>
87 <li
>Applied for coverity coverage and started submitting code on
88 regualr basis.
</li
>
89 <li
>Started fixing bugs reported by coverity
</li
>
90 <li
>Corrected and completed HATEOAS links to make sure entire API is
91 available via URLs in _links.
</li
>
92 <li
>Corrected all relation URLs to use trailing slash.
</li
>
93 <li
>Add initial support for storing data in ElasticSearch.
</li
>
94 <li
>Now able to receive and store uploaded files in the archive.
</li
>
95 <li
>Changed JSON output for object lists to have relations in _links.
</li
>
96 <li
>Improve JSON output for empty object lists.
</li
>
97 <li
>Now uses correct MIME type application/vnd.noark5-v4+json.
</li
>
98 <li
>Added support for docker container images.
</li
>
99 <li
>Added simple API browser implemented in JavaScript/Angular.
</li
>
100 <li
>Started on archive client implemented in JavaScript/Angular.
</li
>
101 <li
>Started on prototype to show the public mail journal.
</li
>
102 <li
>Improved performance by disabling Sprint FileWatcher.
</li
>
103 <li
>Added support for
'arkivskaper
',
'saksmappe
' and
'journalpost
'.
</li
>
104 <li
>Added support for some metadata codelists.
</li
>
105 <li
>Added support for Cross-origin resource sharing (CORS).
</li
>
106 <li
>Changed login method from Basic Auth to JSON Web Token (RFC
7519)
108 <li
>Added support for GET-ing ny-* URLs.
</li
>
109 <li
>Added support for modifying entities using PUT and eTag.
</li
>
110 <li
>Added support for returning XML output on request.
</li
>
111 <li
>Removed support for English field and class names, limiting ourself
112 to the official names.
</li
>
113 <li
>...
</li
>
117 <p
>If this sound interesting to you, please contact us on IRC (#nikita
118 on irc.freenode.net) or email
119 (
<a href=
"https://lists.nuug.no/mailman/listinfo/nikita-noark
">nikita-noark
120 mailing list).
</p
>
125 <title>Idea for storing trusted timestamps in a Noark
5 archive
</title>
126 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html
</link>
127 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html
</guid>
128 <pubDate>Wed,
7 Jun
2017 21:
40:
00 +
0200</pubDate>
129 <description><p
><em
>This is a copy of
130 <a href=
"https://lists.nuug.no/pipermail/nikita-noark/
2017-June/
000297.html
">an
131 email I posted to the nikita-noark mailing list
</a
>. Please follow up
132 there if you would like to discuss this topic. The background is that
133 we are making a free software archive system based on the Norwegian
134 <a href=
"https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden
">Noark
135 5 standard
</a
> for government archives.
</em
></p
>
137 <p
>I
've been wondering a bit lately how trusted timestamps could be
139 <a href=
"https://en.wikipedia.org/wiki/Trusted_timestamping
">Trusted
140 timestamps
</a
> can be used to verify that some information
141 (document/file/checksum/metadata) have not been changed since a
142 specific time in the past. This is useful to verify the integrity of
143 the documents in the archive.
</p
>
145 <p
>Then it occured to me, perhaps the trusted timestamps could be
146 stored as dokument variants (ie dokumentobjekt referered to from
147 dokumentbeskrivelse) with the filename set to the hash it is
150 <p
>Given a
"dokumentbeskrivelse
" with an associated
"dokumentobjekt
",
151 a new dokumentobjekt is associated with
"dokumentbeskrivelse
" with the
152 same attributes as the stamped dokumentobjekt except these
153 attributes:
</p
>
157 <li
>format -
> "RFC3161
"
158 <li
>mimeType -
> "application/timestamp-reply
"
159 <li
>formatDetaljer -
> "&lt;source URL for timestamp service
&gt;
"
160 <li
>filenavn -
> "&lt;sjekksum
&gt;.tsr
"
164 <p
>This assume a service following
165 <a href=
"https://tools.ietf.org/html/rfc3161
">IETF RFC
3161</a
> is
166 used, which specifiy the given MIME type for replies and the .tsr file
167 ending for the content of such trusted timestamp. As far as I can
168 tell from the Noark
5 specifications, it is OK to have several
169 variants/renderings of a dokument attached to a given
170 dokumentbeskrivelse objekt. It might be stretching it a bit to make
171 some of these variants represent crypto-signatures useful for
172 verifying the document integrity instead of representing the dokument
175 <p
>Using the source of the service in formatDetaljer allow several
176 timestamping services to be used. This is useful to spread the risk
177 of key compromise over several organisations. It would only be a
178 problem to trust the timestamps if all of the organisations are
179 compromised.
</p
>
181 <p
>The following oneliner on Linux can be used to generate the tsr
182 file. $input is the path to the file to checksum, and $sha256 is the
183 SHA-
256 checksum of the file (ie the
"<sjekksum
>.tsr
" value mentioned
186 <p
><blockquote
><pre
>
187 openssl ts -query -data
"$inputfile
" -cert -sha256 -no_nonce \
188 | curl -s -H
"Content-Type: application/timestamp-query
" \
189 --data-binary
"@-
" http://zeitstempel.dfn.de
> $sha256.tsr
190 </pre
></blockquote
></p
>
192 <p
>To verify the timestamp, you first need to download the public key
193 of the trusted timestamp service, for example using this command:
</p
>
195 <p
><blockquote
><pre
>
196 wget -O ca-cert.txt \
197 https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
198 </pre
></blockquote
></p
>
200 <p
>Note, the public key should be stored alongside the timestamps in
201 the archive to make sure it is also available
100 years from now. It
202 is probably a good idea to standardise how and were to store such
203 public keys, to make it easier to find for those trying to verify
204 documents
100 or
1000 years from now. :)
</p
>
206 <p
>The verification itself is a simple openssl command:
</p
>
208 <p
><blockquote
><pre
>
209 openssl ts -verify -data $inputfile -in $sha256.tsr \
210 -CAfile ca-cert.txt -text
211 </pre
></blockquote
></p
>
213 <p
>Is there any reason this approach would not work? Is it somehow against
214 the Noark
5 specification?
</p
>
219 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
220 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
221 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
222 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
223 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
224 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
225 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
226 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
227 på om den fri oversetterløsningen
228 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
229 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
231 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
234 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
235 rolle og muligheter til å håndtere internasjonale utfordringer, som
236 for eksempel flykningekrisen.
</p
>
238 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
241 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
242 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
247 <p
>Dette oversetter Apertium slik:
</p
>
250 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
251 andre aktørar og høve til å handtera internasjonale utfordringar, som
252 til dømes *flykningekrisen.
</p
>
254 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
258 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
259 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
264 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
265 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
266 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
267 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
268 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
269 det er kanskje flisespikking. Det understreker vel bare at det alltid
270 trengs korrekturlesning etter automatisk oversettelse.
</p
>