<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
<item>
- <title>Legal to share more than 3000 movies listed on IMDB?</title>
- <link>http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html</guid>
- <pubDate>Sat, 18 Nov 2017 21:20:00 +0100</pubDate>
- <description><p>A month ago, I blogged about my work to
-<a href="http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html">automatically
-check the copyright status of IMDB entries</a>, and try to count the
-number of movies listed in IMDB that is legal to distribute on the
-Internet. I have continued to look for good data sources, and
-identified a few more. The code used to extract information from
-various data sources is available in
-<a href="https://github.com/petterreinholdtsen/public-domain-free-imdb">a
-git repository</a>, currently available from github.</p>
-
-<p>So far I have identified 3186 unique IMDB title IDs. To gain
-better understanding of the structure of the data set, I created a
-histogram of the year associated with each movie (typically release
-year). It is interesting to notice where the peaks and dips in the
-graph are located. I wonder why they are placed there. I suspect
-World Word II caused the dip around 1940, but what caused the peak
-around 2010?</p>
-
-<p align="center"><img src="http://people.skolelinux.org/pere/blog/images/2017-11-18-verk-i-det-fri-filmer.png" /></p>
-
-<p>I've so far identified ten sources for IMDB title IDs for movies in
-the public domain or with a free license. This is the statistics
-reported when running 'make stats' in the git repository:</p>
-
-<pre>
- 249 entries ( 6 unique) with and 288 without IMDB title ID in free-movies-archive-org-butter.json
- 2301 entries ( 540 unique) with and 0 without IMDB title ID in free-movies-archive-org-wikidata.json
- 830 entries ( 29 unique) with and 0 without IMDB title ID in free-movies-icheckmovies-archive-mochard.json
- 2109 entries ( 377 unique) with and 0 without IMDB title ID in free-movies-imdb-pd.json
- 291 entries ( 122 unique) with and 0 without IMDB title ID in free-movies-letterboxd-pd.json
- 144 entries ( 135 unique) with and 0 without IMDB title ID in free-movies-manual.json
- 350 entries ( 1 unique) with and 801 without IMDB title ID in free-movies-publicdomainmovies.json
- 4 entries ( 0 unique) with and 124 without IMDB title ID in free-movies-publicdomainreview.json
- 698 entries ( 119 unique) with and 118 without IMDB title ID in free-movies-publicdomaintorrents.json
- 8 entries ( 8 unique) with and 196 without IMDB title ID in free-movies-vodo.json
- 3186 unique IMDB title IDs in total
-</pre>
-
-<p>The entries without IMDB title ID are candidates to increase the
-data set, but might equally well be duplicates of entries already
-listed with IMDB title ID in one of the other sources, or represent
-movies that lack a IMDB title ID. I've seen examples of all these
-situations when peeking at the entries without IMDB title ID. Based
-on these data sources, the lower bound for movies listed in IMDB that
-are legal to distribute on the Internet is between 3186 and 4713.
-
-<p>It would be great for improving the accuracy of this measurement,
-if the various sources added IMDB title ID to their metadata. I have
-tried to reach the people behind the various sources to ask if they
-are interested in doing this, without any replies so far. Perhaps you
-can help me get in touch with the people behind VODO, Public Domain
-Torrents, Public Domain Movies and Public Domain Review to try to
-convince them to add more metadata to their movie entries?</p>
-
-<p>Another way you could help is by adding pages to Wikipedia about
-movies that are legal to distribute on the Internet. If such page
-exist and include a link to both IMDB and The Internet Archive, the
-script used to generate free-movies-archive-org-wikidata.json should
-pick up the mapping as soon as wikidata is updates.</p>
+ <title>Official MIME type "text/vnd.sosi" for SOSI map data</title>
+ <link>http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html</guid>
+ <pubDate>Tue, 4 Jun 2019 09:20:00 +0200</pubDate>
+ <description><p>Just 15 days ago,
+<ahref="http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html">I
+mentioned</a> my submission to IANA to register an official MIME type
+for the SOSI vector map format. This morning, just an hour ago, I was
+notified that
+<a href="https://www.iana.org/assignments/media-types/text/vnd.sosi">the
+MIME type "text/vnd.sosi"</a> is registered for this format. In
+addition to this registration, my
+<a href="https://github.com/file/file/blob/master/magic/Magdir/sosi">file(1)
+patch for a pattern matching rule for SOSI files</a> has been accepted
+into the official source of that program (pending a new release), and
+I've been told by the team behind
+<a href="https://www.nationalarchives.gov.uk/PRONOM/">PRONOM</a> that
+the SOSI format will be included in the next release of PRONOM, which
+they plan to release this summer around July.</p>
+
+<p>I am very happy to see all of this fall into place, for use by
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">the
+Noark 5 Tjenestegrensesnitt</a> implementations.</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+</description>
+ </item>
+
+ <item>
+ <title>The space rover coquine, or how I ended up on the dark side of the moon</title>
+ <link>http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html</guid>
+ <pubDate>Sun, 2 Jun 2019 23:55:00 +0200</pubDate>
+ <description><p>A while back a college and friend from Debian and the Skolelinux /
+Debian Edu project approached me, asking if I knew someone that might
+be interested in helping out with a technology project he was running
+as a teacher at <a href="https://www.ecolefrancodanoise.dk/">L'école
+franco-danoise</a> - the Danish-French school and kindergarden. The
+kids were building robots, rovers. The story behind it is to build a
+rover for use
+<a href="http://blog.ecolefrancodanoise.dk/first-week-on-the-dark-side">on
+the dark side of the moon</a>, and remote control it. As travel cost
+was a bit high for the final destination, and they wanted to test the
+concept first, he was looking for volunteers to host a rover for the
+kids to control in a foreign country. I ended up volunteering as a
+host, and last week the rover arrived. It took a while to arrive
+after <a href="http://blog.ecolefrancodanoise.dk/model-moms">it was
+built and shipped</a>, because of customs confusion. Luckily we were
+able fix it quickly with help from my colleges at work.</p>
+
+<p>This is what it looked like when the rover arrived. Note the cute
+eyes looking up on me from the wrapping</p>
+
+<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-esken-med-det-rare-i.jpeg" width="32%" style="clear:left"/>
+<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-den-ser-meg.jpeg" width="32%" style="clear:left"/>
+<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-en-skrue-loes.jpeg" width="32%" style="clear:left"/>
+
+<p style="text-align:left">Once the robot arrived, we needed to track
+down batteries and figure out how to build custom firmware for it with
+the appropriate wifi settings. I asked a friend if I could get two
+18650 batteries from his pile of Tesla batteries (he had them from the
+wrack of a crashed Tesla), so now the rover is running on Tesla
+batteries.</p>
+
+<p>Building
+<a href="https://gitlab.com/ecolefrancodanoise/arduino-efd/">the rover
+firmware</a> proved a bit harder, as the code did not work out of the
+box with the Arduino IDE package in Debian Buster. I suspect this is
+due to a unsolved
+<a href="https://github.com/arduino/Arduino/pull/2703"> license problem
+with arduino</a> blocking Debian from upgrading to the latest version.
+In the end we gave up debugging why the IDE failed to find the
+required libraries, and ended up using the Arduino Makefile from the
+<a href="https://tracker.debian.org/pkg/arduino-mk">arduino-mk Debian
+package</a> instead. Unfortunately the camera library is missing from
+the Arduino environment in Debian, so we disabled the camera support
+for the first firmware build, to get something up and running. With
+this reduced firmware, the robot could be controlled via the
+controller server, driving around and measuring distance using its
+internal acoustic sensor.</p>
+
+<p>Next, With some help from my friend in Denmark, which checked in the
+camera library into the gitlab repository for me to use, we were able
+to build a new and more complete version of the firmware, and the
+robot is now up and running. This is what the "commander" web page
+look like after taking a measurement and a snapshot:</p>
+
+<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-commander.png" width="40%" border="1" align="center"/>
+
+<p>If you want to learn more about this project, you can check out the
+<a href="https://hackaday.io/project/164082-the-dark-side-challenge">The
+Dark Side Challenge</a> Hackaday web pages.</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
<item>
- <title>Some notes on fault tolerant storage systems</title>
- <link>http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html</guid>
- <pubDate>Wed, 1 Nov 2017 15:35:00 +0100</pubDate>
- <description><p>If you care about how fault tolerant your storage is, you might
-find these articles and papers interesting. They have formed how I
-think of when designing a storage system.</p>
+ <title>Nikita version 0.4 released - free software archive API server</title>
+ <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html</guid>
+ <pubDate>Wed, 22 May 2019 11:30:00 +0200</pubDate>
+ <description><p>This morning, a new release of
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita
+Noark 5 core project</a> was
+<a href="https://lists.nuug.no/pipermail/nikita-noark/2019-May/000468.html">announced
+on the project mailing list</a>. The Nikita free software solution is
+an implementation of the Norwegian archive standard Noark 5 used by
+government offices in Norway. These were the changes in version 0.4
+since version 0.3, see the email link above for links to a demo site:</p>
<ul>
-<li>USENIX :login; <a
-href="https://www.usenix.org/publications/login/summer2017/ganesan">Redundancy
-Does Not Imply Fault Tolerance. Analysis of Distributed Storage
-Reactions to Single Errors and Corruptions</a> by Aishwarya Ganesan,
-Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi
-H. Arpaci-Dusseau</li>
-
-<li>ZDNet
-<a href="http://www.zdnet.com/article/why-raid-5-stops-working-in-2009/">Why
-RAID 5 stops working in 2009</a> by Robin Harris</li>
-
-<li>ZDNet
-<a href="http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/">Why
-RAID 6 stops working in 2019</a> by Robin Harris</li>
-
-<li>USENIX FAST'07
-<a href="http://research.google.com/archive/disk_failures.pdf">Failure
-Trends in a Large Disk Drive Population</a> by Eduardo Pinheiro,
-Wolf-Dietrich Weber and Luiz André Barroso</li>
-
-<li>USENIX ;login: <a
-href="https://www.usenix.org/system/files/login/articles/hughes12-04.pdf">Data
-Integrity. Finding Truth in a World of Guesses and Lies</a> by Doug
-Hughes</li>
-
-<li>USENIX FAST'08
-<a href="https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/">An
-Analysis of Data Corruption in the Storage Stack</a> by
-L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C.
-Arpaci-Dusseau, and R. H. Arpaci-Dusseau</li>
-
-<li>USENIX FAST'07 <a
-href="https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/">Disk
-failures in the real world: what does an MTTF of 1,000,000 hours mean
-to you?</a> by B. Schroeder and G. A. Gibson.</li>
-
-<li>USENIX ;login: <a
-href="https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/">Are
-Disks the Dominant Contributor for Storage Failures? A Comprehensive
-Study of Storage Subsystem Failure Characteristics</a> by Weihang
-Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky</li>
-
-<li>SIGMETRICS 2007
-<a href="http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf">An
-analysis of latent sector errors in disk drives</a> by
-L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler</li>
-
+ <li>Roll out OData handling to all endpoints where applicable</li>
+ <li>Changed the relation key for "ny-journalpost" to the official one.</li>
+ <li>Better link generation on outgoing links.</li>
+ <li>Tidy up code and make code and approaches more consistent throughout
+ the codebase</li>
+ <li>Update rels to be in compliance with updated version in the
+ interface standard</li>
+ <li>Avoid printing links on empty objects as they can't have links</li>
+ <li>Small bug fixes and improvements</li>
+ <li>Start moving generation of outgoing links to @Service layer so access
+ control can be used when generating links</li>
+ <li>Log exception that was being swallowed so it's traceable</li>
+ <li>Fix name mapping problem</li>
+ <li>Update templated printing so templated should only be printed if it
+ is set true. Requires more work to roll out across entire
+ application.</li>
+ <li>Remove Record->DocumentObject as per domain model of n5v4</li>
+ <li>Add ability to delete lists filtered with OData</li>
+ <li>Return NO_CONTENT (204) on delete as per interface standard</li>
+ <li>Introduce support for ConstraintViolationException exception</li>
+ <li>Make Service classes extend NoarkService</li>
+ <li>Make code base respect X-Forwarded-Host, X-Forwarded-Proto and
+ X-Forwarded-Port</li>
+ <li>Update CorrespondencePart* code to be more in line with Single
+ Responsibility Principle</li>
+ <li>Make package name follow directory structure</li>
+ <li>Make sure Document number starts at 1, not 0</li>
+ <li>Fix isues discovered by FindBugs</li>
+ <li>Update from Date to ZonedDateTime</li>
+ <li>Fix wrong tablename</li>
+ <li>Introduce Service layer tests</li>
+ <li>Improvements to CorrespondencePart</li>
+ <li>Continued work on Class / Classificationsystem</li>
+ <li>Fix feature where authors were stored as storageLocations</li>
+ <li>Update HQL builder for OData</li>
+ <li>Update OData search capability from webpage</li>
+
</ul>
-<p>Several of these research papers are based on data collected from
-hundred thousands or millions of disk, and their findings are eye
-opening. The short story is simply do not implicitly trust RAID or
-redundant storage systems. Details matter. And unfortunately there
-are few options on Linux addressing all the identified issues. Both
-ZFS and Btrfs are doing a fairly good job, but have legal and
-practical issues on their own. I wonder how cluster file systems like
-Ceph do in this regard. After all, there is an old saying, you know
-you have a distributed system when the crash of a computer you have
-never heard of stops you from getting any work done. The same holds
-true if fault tolerance do not work.</p>
-
-<p>Just remember, in the end, it do not matter how redundant, or how
-fault tolerant your storage is, if you do not continuously monitor its
-status to detect and replace failed disks.</p>
-</description>
- </item>
-
- <item>
- <title>Web services for writing academic LaTeX papers as a team</title>
- <link>http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html</guid>
- <pubDate>Tue, 31 Oct 2017 21:00:00 +0100</pubDate>
- <description><p>I was surprised today to learn that a friend in academia did not
-know there are easily available web services available for writing
-LaTeX documents as a team. I thought it was common knowledge, but to
-make sure at least my readers are aware of it, I would like to mention
-these useful services for writing LaTeX documents. Some of them even
-provide a WYSIWYG editor to ease writing even further.</p>
-
-<p>There are two commercial services available,
-<a href="https://sharelatex.com">ShareLaTeX</a> and
-<a href="https://overleaf.com">Overleaf</a>. They are very easy to
-use. Just start a new document, select which publisher to write for
-(ie which LaTeX style to use), and start writing. Note, these two
-have announced their intention to join forces, so soon it will only be
-one joint service. I've used both for different documents, and they
-work just fine. While
-<a href="https://github.com/sharelatex/sharelatex">ShareLaTeX is free
-software</a>, while the latter is not. According to <a
-href="https://www.overleaf.com/help/17-is-overleaf-open-source">a
-announcement from Overleaf</a>, they plan to keep the ShareLaTeX code
-base maintained as free software.</p>
-
-But these two are not the only alternatives.
-<a href="https://app.fiduswriter.org/">Fidus Writer</a> is another free
-software solution with <a href="https://github.com/fiduswriter">the
-source available on github</a>. I have not used it myself. Several
-others can be found on the nice
-<a href="https://alternativeto.net/software/sharelatex/">alterntiveTo
-web service</a>.
-
-<p>If you like Google Docs or Etherpad, but would like to write
-documents in LaTeX, you should check out these services. You can even
-host your own, if you want to. :)</p>
+<p>If free and open standardized archiving API sound interesting to
+you, please contact us on IRC
+(<a href="irc://irc.freenode.net/%23nikita">#nikita on
+irc.freenode.net</a>) or email
+(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
+mailing list</a>).</p>
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
<item>
- <title>Locating IMDB IDs of movies in the Internet Archive using Wikidata</title>
- <link>http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html</guid>
- <pubDate>Wed, 25 Oct 2017 12:20:00 +0200</pubDate>
- <description><p>Recently, I needed to automatically check the copyright status of a
-set of <a href="http://www.imdb.com/">The Internet Movie database
-(IMDB)</a> entries, to figure out which one of the movies they refer
-to can be freely distributed on the Internet. This proved to be
-harder than it sounds. IMDB for sure list movies without any
-copyright protection, where the copyright protection has expired or
-where the movie is lisenced using a permissive license like one from
-Creative Commons. These are mixed with copyright protected movies,
-and there seem to be no way to separate these classes of movies using
-the information in IMDB.</p>
-
-<p>First I tried to look up entries manually in IMDB,
-<a href="https://www.wikipedia.org/">Wikipedia</a> and
-<a href="https://www.archive.org/">The Internet Archive</a>, to get a
-feel how to do this. It is hard to know for sure using these sources,
-but it should be possible to be reasonable confident a movie is "out
-of copyright" with a few hours work per movie. As I needed to check
-almost 20,000 entries, this approach was not sustainable. I simply
-can not work around the clock for about 6 years to check this data
-set.</p>
-
-<p>I asked the people behind The Internet Archive if they could
-introduce a new metadata field in their metadata XML for IMDB ID, but
-was told that they leave it completely to the uploaders to update the
-metadata. Some of the metadata entries had IMDB links in the
-description, but I found no way to download all metadata files in bulk
-to locate those ones and put that approach aside.</p>
-
-<p>In the process I noticed several Wikipedia articles about movies
-had links to both IMDB and The Internet Archive, and it occured to me
-that I could use the Wikipedia RDF data set to locate entries with
-both, to at least get a lower bound on the number of movies on The
-Internet Archive with a IMDB ID. This is useful based on the
-assumption that movies distributed by The Internet Archive can be
-legally distributed on the Internet. With some help from the RDF
-community (thank you DanC), I was able to come up with this query to
-pass to <a href="https://query.wikidata.org/">the SPARQL interface on
-Wikidata</a>:
-
-<p><pre>
-SELECT ?work ?imdb ?ia ?when ?label
-WHERE
-{
- ?work wdt:P31/wdt:P279* wd:Q11424.
- ?work wdt:P345 ?imdb.
- ?work wdt:P724 ?ia.
- OPTIONAL {
- ?work wdt:P577 ?when.
- ?work rdfs:label ?label.
- FILTER(LANG(?label) = "en").
- }
-}
-</pre></p>
-
-<p>If I understand the query right, for every film entry anywhere in
-Wikpedia, it will return the IMDB ID and The Internet Archive ID, and
-when the movie was released and its English title, if either or both
-of the latter two are available. At the moment the result set contain
-2338 entries. Of course, it depend on volunteers including both
-correct IMDB and The Internet Archive IDs in the wikipedia articles
-for the movie. It should be noted that the result will include
-duplicates if the movie have entries in several languages. There are
-some bogus entries, either because The Internet Archive ID contain a
-typo or because the movie is not available from The Internet Archive.
-I did not verify the IMDB IDs, as I am unsure how to do that
-automatically.</p>
-
-<p>I wrote a small python script to extract the data set from Wikidata
-and check if the XML metadata for the movie is available from The
-Internet Archive, and after around 1.5 hour it produced a list of 2097
-free movies and their IMDB ID. In total, 171 entries in Wikidata lack
-the refered Internet Archive entry. I assume the 70 "disappearing"
-entries (ie 2338-2097-171) are duplicate entries.</p>
-
-<p>This is not too bad, given that The Internet Archive report to
-contain <a href="https://archive.org/details/feature_films">5331
-feature films</a> at the moment, but it also mean more than 3000
-movies are missing on Wikipedia or are missing the pair of references
-on Wikipedia.</p>
-
-<p>I was curious about the distribution by release year, and made a
-little graph to show how the amount of free movies is spread over the
-years:<p>
-
-<p><img src="http://people.skolelinux.org/pere/blog/images/2017-10-25-verk-i-det-fri-filmer.png"></p>
-
-<p>I expect the relative distribution of the remaining 3000 movies to
-be similar.</p>
-
-<p>If you want to help, and want to ensure Wikipedia can be used to
-cross reference The Internet Archive and The Internet Movie Database,
-please make sure entries like this are listed under the "External
-links" heading on the Wikipedia article for the movie:</p>
-
-<p><pre>
-* {{Internet Archive film|id=FightingLady}}
-* {{IMDb title|id=0036823|title=The Fighting Lady}}
-</pre></p>
-
-<p>Please verify the links on the final page, to make sure you did not
-introduce a typo.</p>
-
-<p>Here is the complete list, if you want to correct the 171
-identified Wikipedia entries with broken links to The Internet
-Archive: <a href="http://www.wikidata.org/entity/Q1140317">Q1140317</a>,
-<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>,
-<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>,
-<a href="http://www.wikidata.org/entity/Q470560">Q470560</a>,
-<a href="http://www.wikidata.org/entity/Q743340">Q743340</a>,
-<a href="http://www.wikidata.org/entity/Q822580">Q822580</a>,
-<a href="http://www.wikidata.org/entity/Q480696">Q480696</a>,
-<a href="http://www.wikidata.org/entity/Q128761">Q128761</a>,
-<a href="http://www.wikidata.org/entity/Q1307059">Q1307059</a>,
-<a href="http://www.wikidata.org/entity/Q1335091">Q1335091</a>,
-<a href="http://www.wikidata.org/entity/Q1537166">Q1537166</a>,
-<a href="http://www.wikidata.org/entity/Q1438334">Q1438334</a>,
-<a href="http://www.wikidata.org/entity/Q1479751">Q1479751</a>,
-<a href="http://www.wikidata.org/entity/Q1497200">Q1497200</a>,
-<a href="http://www.wikidata.org/entity/Q1498122">Q1498122</a>,
-<a href="http://www.wikidata.org/entity/Q865973">Q865973</a>,
-<a href="http://www.wikidata.org/entity/Q834269">Q834269</a>,
-<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>,
-<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>,
-<a href="http://www.wikidata.org/entity/Q1548193">Q1548193</a>,
-<a href="http://www.wikidata.org/entity/Q499031">Q499031</a>,
-<a href="http://www.wikidata.org/entity/Q1564769">Q1564769</a>,
-<a href="http://www.wikidata.org/entity/Q1585239">Q1585239</a>,
-<a href="http://www.wikidata.org/entity/Q1585569">Q1585569</a>,
-<a href="http://www.wikidata.org/entity/Q1624236">Q1624236</a>,
-<a href="http://www.wikidata.org/entity/Q4796595">Q4796595</a>,
-<a href="http://www.wikidata.org/entity/Q4853469">Q4853469</a>,
-<a href="http://www.wikidata.org/entity/Q4873046">Q4873046</a>,
-<a href="http://www.wikidata.org/entity/Q915016">Q915016</a>,
-<a href="http://www.wikidata.org/entity/Q4660396">Q4660396</a>,
-<a href="http://www.wikidata.org/entity/Q4677708">Q4677708</a>,
-<a href="http://www.wikidata.org/entity/Q4738449">Q4738449</a>,
-<a href="http://www.wikidata.org/entity/Q4756096">Q4756096</a>,
-<a href="http://www.wikidata.org/entity/Q4766785">Q4766785</a>,
-<a href="http://www.wikidata.org/entity/Q880357">Q880357</a>,
-<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>,
-<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>,
-<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>,
-<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>,
-<a href="http://www.wikidata.org/entity/Q1194170">Q1194170</a>,
-<a href="http://www.wikidata.org/entity/Q940014">Q940014</a>,
-<a href="http://www.wikidata.org/entity/Q946863">Q946863</a>,
-<a href="http://www.wikidata.org/entity/Q172837">Q172837</a>,
-<a href="http://www.wikidata.org/entity/Q573077">Q573077</a>,
-<a href="http://www.wikidata.org/entity/Q1219005">Q1219005</a>,
-<a href="http://www.wikidata.org/entity/Q1219599">Q1219599</a>,
-<a href="http://www.wikidata.org/entity/Q1643798">Q1643798</a>,
-<a href="http://www.wikidata.org/entity/Q1656352">Q1656352</a>,
-<a href="http://www.wikidata.org/entity/Q1659549">Q1659549</a>,
-<a href="http://www.wikidata.org/entity/Q1660007">Q1660007</a>,
-<a href="http://www.wikidata.org/entity/Q1698154">Q1698154</a>,
-<a href="http://www.wikidata.org/entity/Q1737980">Q1737980</a>,
-<a href="http://www.wikidata.org/entity/Q1877284">Q1877284</a>,
-<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>,
-<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>,
-<a href="http://www.wikidata.org/entity/Q1199451">Q1199451</a>,
-<a href="http://www.wikidata.org/entity/Q1211871">Q1211871</a>,
-<a href="http://www.wikidata.org/entity/Q1212179">Q1212179</a>,
-<a href="http://www.wikidata.org/entity/Q1238382">Q1238382</a>,
-<a href="http://www.wikidata.org/entity/Q4906454">Q4906454</a>,
-<a href="http://www.wikidata.org/entity/Q320219">Q320219</a>,
-<a href="http://www.wikidata.org/entity/Q1148649">Q1148649</a>,
-<a href="http://www.wikidata.org/entity/Q645094">Q645094</a>,
-<a href="http://www.wikidata.org/entity/Q5050350">Q5050350</a>,
-<a href="http://www.wikidata.org/entity/Q5166548">Q5166548</a>,
-<a href="http://www.wikidata.org/entity/Q2677926">Q2677926</a>,
-<a href="http://www.wikidata.org/entity/Q2698139">Q2698139</a>,
-<a href="http://www.wikidata.org/entity/Q2707305">Q2707305</a>,
-<a href="http://www.wikidata.org/entity/Q2740725">Q2740725</a>,
-<a href="http://www.wikidata.org/entity/Q2024780">Q2024780</a>,
-<a href="http://www.wikidata.org/entity/Q2117418">Q2117418</a>,
-<a href="http://www.wikidata.org/entity/Q2138984">Q2138984</a>,
-<a href="http://www.wikidata.org/entity/Q1127992">Q1127992</a>,
-<a href="http://www.wikidata.org/entity/Q1058087">Q1058087</a>,
-<a href="http://www.wikidata.org/entity/Q1070484">Q1070484</a>,
-<a href="http://www.wikidata.org/entity/Q1080080">Q1080080</a>,
-<a href="http://www.wikidata.org/entity/Q1090813">Q1090813</a>,
-<a href="http://www.wikidata.org/entity/Q1251918">Q1251918</a>,
-<a href="http://www.wikidata.org/entity/Q1254110">Q1254110</a>,
-<a href="http://www.wikidata.org/entity/Q1257070">Q1257070</a>,
-<a href="http://www.wikidata.org/entity/Q1257079">Q1257079</a>,
-<a href="http://www.wikidata.org/entity/Q1197410">Q1197410</a>,
-<a href="http://www.wikidata.org/entity/Q1198423">Q1198423</a>,
-<a href="http://www.wikidata.org/entity/Q706951">Q706951</a>,
-<a href="http://www.wikidata.org/entity/Q723239">Q723239</a>,
-<a href="http://www.wikidata.org/entity/Q2079261">Q2079261</a>,
-<a href="http://www.wikidata.org/entity/Q1171364">Q1171364</a>,
-<a href="http://www.wikidata.org/entity/Q617858">Q617858</a>,
-<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>,
-<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>,
-<a href="http://www.wikidata.org/entity/Q324513">Q324513</a>,
-<a href="http://www.wikidata.org/entity/Q374172">Q374172</a>,
-<a href="http://www.wikidata.org/entity/Q7533269">Q7533269</a>,
-<a href="http://www.wikidata.org/entity/Q970386">Q970386</a>,
-<a href="http://www.wikidata.org/entity/Q976849">Q976849</a>,
-<a href="http://www.wikidata.org/entity/Q7458614">Q7458614</a>,
-<a href="http://www.wikidata.org/entity/Q5347416">Q5347416</a>,
-<a href="http://www.wikidata.org/entity/Q5460005">Q5460005</a>,
-<a href="http://www.wikidata.org/entity/Q5463392">Q5463392</a>,
-<a href="http://www.wikidata.org/entity/Q3038555">Q3038555</a>,
-<a href="http://www.wikidata.org/entity/Q5288458">Q5288458</a>,
-<a href="http://www.wikidata.org/entity/Q2346516">Q2346516</a>,
-<a href="http://www.wikidata.org/entity/Q5183645">Q5183645</a>,
-<a href="http://www.wikidata.org/entity/Q5185497">Q5185497</a>,
-<a href="http://www.wikidata.org/entity/Q5216127">Q5216127</a>,
-<a href="http://www.wikidata.org/entity/Q5223127">Q5223127</a>,
-<a href="http://www.wikidata.org/entity/Q5261159">Q5261159</a>,
-<a href="http://www.wikidata.org/entity/Q1300759">Q1300759</a>,
-<a href="http://www.wikidata.org/entity/Q5521241">Q5521241</a>,
-<a href="http://www.wikidata.org/entity/Q7733434">Q7733434</a>,
-<a href="http://www.wikidata.org/entity/Q7736264">Q7736264</a>,
-<a href="http://www.wikidata.org/entity/Q7737032">Q7737032</a>,
-<a href="http://www.wikidata.org/entity/Q7882671">Q7882671</a>,
-<a href="http://www.wikidata.org/entity/Q7719427">Q7719427</a>,
-<a href="http://www.wikidata.org/entity/Q7719444">Q7719444</a>,
-<a href="http://www.wikidata.org/entity/Q7722575">Q7722575</a>,
-<a href="http://www.wikidata.org/entity/Q2629763">Q2629763</a>,
-<a href="http://www.wikidata.org/entity/Q2640346">Q2640346</a>,
-<a href="http://www.wikidata.org/entity/Q2649671">Q2649671</a>,
-<a href="http://www.wikidata.org/entity/Q7703851">Q7703851</a>,
-<a href="http://www.wikidata.org/entity/Q7747041">Q7747041</a>,
-<a href="http://www.wikidata.org/entity/Q6544949">Q6544949</a>,
-<a href="http://www.wikidata.org/entity/Q6672759">Q6672759</a>,
-<a href="http://www.wikidata.org/entity/Q2445896">Q2445896</a>,
-<a href="http://www.wikidata.org/entity/Q12124891">Q12124891</a>,
-<a href="http://www.wikidata.org/entity/Q3127044">Q3127044</a>,
-<a href="http://www.wikidata.org/entity/Q2511262">Q2511262</a>,
-<a href="http://www.wikidata.org/entity/Q2517672">Q2517672</a>,
-<a href="http://www.wikidata.org/entity/Q2543165">Q2543165</a>,
-<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>,
-<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>,
-<a href="http://www.wikidata.org/entity/Q12126890">Q12126890</a>,
-<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>,
-<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>,
-<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>,
-<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>,
-<a href="http://www.wikidata.org/entity/Q2559509">Q2559509</a>,
-<a href="http://www.wikidata.org/entity/Q2559912">Q2559912</a>,
-<a href="http://www.wikidata.org/entity/Q7760469">Q7760469</a>,
-<a href="http://www.wikidata.org/entity/Q6703974">Q6703974</a>,
-<a href="http://www.wikidata.org/entity/Q4744">Q4744</a>,
-<a href="http://www.wikidata.org/entity/Q7766962">Q7766962</a>,
-<a href="http://www.wikidata.org/entity/Q7768516">Q7768516</a>,
-<a href="http://www.wikidata.org/entity/Q7769205">Q7769205</a>,
-<a href="http://www.wikidata.org/entity/Q7769988">Q7769988</a>,
-<a href="http://www.wikidata.org/entity/Q2946945">Q2946945</a>,
-<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>,
-<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>,
-<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>,
-<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>,
-<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>,
-<a href="http://www.wikidata.org/entity/Q6909175">Q6909175</a>,
-<a href="http://www.wikidata.org/entity/Q7405709">Q7405709</a>,
-<a href="http://www.wikidata.org/entity/Q7416149">Q7416149</a>,
-<a href="http://www.wikidata.org/entity/Q7239952">Q7239952</a>,
-<a href="http://www.wikidata.org/entity/Q7317332">Q7317332</a>,
-<a href="http://www.wikidata.org/entity/Q7783674">Q7783674</a>,
-<a href="http://www.wikidata.org/entity/Q7783704">Q7783704</a>,
-<a href="http://www.wikidata.org/entity/Q7857590">Q7857590</a>,
-<a href="http://www.wikidata.org/entity/Q3372526">Q3372526</a>,
-<a href="http://www.wikidata.org/entity/Q3372642">Q3372642</a>,
-<a href="http://www.wikidata.org/entity/Q3372816">Q3372816</a>,
-<a href="http://www.wikidata.org/entity/Q3372909">Q3372909</a>,
-<a href="http://www.wikidata.org/entity/Q7959649">Q7959649</a>,
-<a href="http://www.wikidata.org/entity/Q7977485">Q7977485</a>,
-<a href="http://www.wikidata.org/entity/Q7992684">Q7992684</a>,
-<a href="http://www.wikidata.org/entity/Q3817966">Q3817966</a>,
-<a href="http://www.wikidata.org/entity/Q3821852">Q3821852</a>,
-<a href="http://www.wikidata.org/entity/Q3420907">Q3420907</a>,
-<a href="http://www.wikidata.org/entity/Q3429733">Q3429733</a>,
-<a href="http://www.wikidata.org/entity/Q774474">Q774474</a></p>
+ <title>MIME type "text/vnd.sosi" for SOSI map data</title>
+ <link>http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</guid>
+ <pubDate>Mon, 20 May 2019 08:35:00 +0200</pubDate>
+ <description><p>As part of my involvement in the work to
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard">standardise
+a REST based API for Noark 5</a>, the Norwegian archiving standard, I
+spent some time the last few months to try to register a
+<a href="https://www.iana.org/assignments/media-types/">MIME type</a>
+and <a href="https://www.nationalarchives.gov.uk/PRONOM/">PRONOM
+code</a> for the SOSI file format. The background is that there is a
+set of formats approved for long term storage and archiving in Norway,
+and among these formats, SOSI is the only format missing a MIME type
+and PRONOM code.</p>
+
+<p>What is SOSI, you might ask? To quote Wikipedia: SOSI is short for
+Samordnet Opplegg for Stedfestet Informasjon (literally "Coordinated
+Approach for Spatial Information", but more commonly expanded in
+English to Systematic Organization of Spatial Information). It is a
+text based file format for geo-spatial vector information used in
+Norway. Information about the SOSI format can be found in English
+from <a href="https://en.wikipedia.org/wiki/SOSI">Wikipedia</a>. The
+specification is available in Norwegian from
+<a href="https://www.kartverket.no/geodataarbeid/Standarder/SOSI/">the
+Norwegian mapping authority</a>. The SOSI standard, which originated
+in the beginning of nineteen eighties, was the inspiration and formed the
+basis for the XML based
+<a href="https://en.wikipedia.org/wiki/Geography_Markup_Language">Geography
+Markup Language</a>.</p>
+
+<p>I have so far written
+<a href="https://github.com/file/file/pull/67">a pattern matching
+rule</a> for the file(1) unix tool to recognize SOSI files, submitted
+a request to the PRONOM project to have a PRONOM ID assigned to the
+format (reference TNA1555078202S60), and today send a request to IANA
+to register the "text/vnd.sosi" MIME type for this format (referanse
+<a href="https://tools.iana.org/public-view/viewticket/1143144">IANA
+#1143144</a>). If all goes well, in a few months, anyone implementing
+the Noark 5 Tjenestegrensesnitt API spesification should be able to
+use an official MIME type and PRONOM code for SOSI files. In
+addition, anyone using SOSI files on Linux should be able to
+automatically recognise the format and web sites handing out SOSI
+files can begin providing a more specific MIME type. So far, SOSI
+files has been handed out from web sites using the
+"application/octet-stream" MIME type, which is just a nice way of
+stating "I do not know". Soon, we will know. :)</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
<item>
- <title>A one-way wall on the border?</title>
- <link>http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html</guid>
- <pubDate>Sat, 14 Oct 2017 22:10:00 +0200</pubDate>
- <description><p>I find it fascinating how many of the people being locked inside
-the proposed border wall between USA and Mexico support the idea. The
-proposal to keep Mexicans out reminds me of
-<a href="http://www.history.com/news/10-things-you-may-not-know-about-the-berlin-wall">the
-propaganda twist from the East Germany government</a> calling the wall
-the “Antifascist Bulwark” after erecting the Berlin Wall, claiming
-that the wall was erected to keep enemies from creeping into East
-Germany, while it was obvious to the people locked inside it that it
-was erected to keep the people from escaping.</p>
-
-<p>Do the people in USA supporting this wall really believe it is a
-one way wall, only keeping people on the outside from getting in,
-while not keeping people in the inside from getting out?</p>
+ <title>PlantUML for text based UML diagram modelling - nice free software</title>
+ <link>http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html</guid>
+ <pubDate>Mon, 25 Mar 2019 09:35:00 +0100</pubDate>
+ <description><p>As part of my involvement with the
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita
+Noark 5 core project</a>, I have been proposing improvements to the
+API specification created by <a href="https://www.arkivverket.no/">The
+National Archives of Norway</a> and helped migrating the text from a
+version control system unfriendly binary format (docx) to Markdown in
+git. Combined with the migration to a public git repository (on
+github), this has made it possible for anyone to suggest improvement
+to the text.</p>
+
+<p>The specification is filled with UML diagrams. I believe the
+original diagrams were modelled using Sparx Systems Enterprise
+Architect, and exported as EMF files for import into docx. This
+approach make it very hard to track changes using a version control
+system. To improve the situation I have been looking for a good text
+based UML format with associated command line free software tools on
+Linux and Windows, to allow anyone to send in corrections to the UML
+diagrams in the specification. The tool must be text based to work
+with git, and command line to be able to run it automatically to
+generate the diagram images. Finally, it must be free software to
+allow anyone, even those that can not accept a non-free software
+license, to contribute.</p>
+
+<p>I did not know much about free software UML modelling tools when I
+started. I have used dia and inkscape for simple modelling in the
+past, but neither are available on Windows, as far as I could tell. I
+came across a nice
+<a href="https://modeling-languages.com/text-uml-tools-complete-list/">list
+of text mode uml tools</a>, and tested out a few of the tools listed
+there. <a href="http://plantuml.com/">The PlantUML tool</a> seemed
+most promising. After verifying that the packages
+<a href="https://tracker.debian.org/pkg/plantuml">is available in
+Debian</a> and found <a href="https://github.com/plantuml/plantuml">its
+Java source</a> under a GPL license on github, I set out to test if it
+could represent the diagrams we needed, ie the ones currently in
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">the
+Noark 5 Tjenestegrensesnitt specification</a>. I am happy to report
+that it could represent them, even thought it have a few warts here
+and there.</p>
+
+<p>After a few days of modelling I completed the task this weekend. A
+temporary link to the complete set of diagrams (original and from
+PlantUML) is available in
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/76">the
+github issue discussing the need for a text based UML format</a>, but
+please note I lack a sensible tool to convert EMF files to PNGs, so
+the "original" rendering is not as good as the original was in the
+publised PDF.</p>
+
+<p>Here is an example UML diagram, showing the core classes for
+keeping metadata about archived documents:</p>
+
+<pre>
+@startuml
+skinparam classAttributeIconSize 0
+
+!include media/uml-class-arkivskaper.iuml
+!include media/uml-class-arkiv.iuml
+!include media/uml-class-klassifikasjonssystem.iuml
+!include media/uml-class-klasse.iuml
+!include media/uml-class-arkivdel.iuml
+!include media/uml-class-mappe.iuml
+!include media/uml-class-merknad.iuml
+!include media/uml-class-registrering.iuml
+!include media/uml-class-basisregistrering.iuml
+!include media/uml-class-dokumentbeskrivelse.iuml
+!include media/uml-class-dokumentobjekt.iuml
+!include media/uml-class-konvertering.iuml
+!include media/uml-datatype-elektronisksignatur.iuml
+
+Arkivstruktur.Arkivskaper "+arkivskaper 1..*" <-o "+arkiv 0..*" Arkivstruktur.Arkiv
+Arkivstruktur.Arkiv o--> "+underarkiv 0..*" Arkivstruktur.Arkiv
+Arkivstruktur.Arkiv "+arkiv 1" o--> "+arkivdel 0..*" Arkivstruktur.Arkivdel
+Arkivstruktur.Klassifikasjonssystem "+klassifikasjonssystem [0..1]" <--o "+arkivdel 1..*" Arkivstruktur.Arkivdel
+Arkivstruktur.Klassifikasjonssystem "+klassifikasjonssystem [0..1]" o--> "+klasse 0..*" Arkivstruktur.Klasse
+Arkivstruktur.Arkivdel "+arkivdel 0..1" o--> "+mappe 0..*" Arkivstruktur.Mappe
+Arkivstruktur.Arkivdel "+arkivdel 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering
+Arkivstruktur.Klasse "+klasse 0..1" o--> "+mappe 0..*" Arkivstruktur.Mappe
+Arkivstruktur.Klasse "+klasse 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering
+Arkivstruktur.Mappe --> "+undermappe 0..*" Arkivstruktur.Mappe
+Arkivstruktur.Mappe "+mappe 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering
+Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Mappe
+Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Dokumentbeskrivelse
+Arkivstruktur.Basisregistrering -|> Arkivstruktur.Registrering
+Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Basisregistrering
+Arkivstruktur.Registrering "+registrering 1..*" o--> "+dokumentbeskrivelse 0..*" Arkivstruktur.Dokumentbeskrivelse
+Arkivstruktur.Dokumentbeskrivelse "+dokumentbeskrivelse 1" o-> "+dokumentobjekt 0..*" Arkivstruktur.Dokumentobjekt
+Arkivstruktur.Dokumentobjekt *-> "+konvertering 0..*" Arkivstruktur.Konvertering
+Arkivstruktur.ElektroniskSignatur -[hidden]-> Arkivstruktur.Dokumentobjekt
+@enduml
+</pre>
+
+<p><a href="http://plantuml.com/class-diagram">The format</a> is quite
+compact, with little redundant information. The text expresses
+entities and relations, and there is little layout related fluff. One
+can reuse content by using include files, allowing for consistent
+naming across several diagrams. The include files can be standalone
+PlantUML too. Here is the content of
+<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+
+<pre>
+@startuml
+class Arkivstruktur.Arkivskaper <Arkivenhet> {
+ +arkivskaperID : string
+ +arkivskaperNavn : string
+ +beskrivelse : string [0..1]
+}
+@enduml
+</pre>
+
+<p>This is what the complete diagram for the PlantUML notation above
+look like:</p>
+
+<p><img width="80%" src="http://people.skolelinux.org/pere/blog/images/2019-03-25-noark5-plantuml-diagrameksempel.png"></p>
+
+<p>A cool feature of PlantUML is that the generated PNG files include
+the entire original source diagram as text. The source (with include
+statements expanded) can be extracted using for example
+<tt>exiftool</tt>. Another cool feature is that parts of the entities
+can be hidden after inclusion. This allow to use include files with
+all attributes listed, even for UML diagrams that should not list any
+attributes.</p>
+
+<p>The diagram also show some of the warts. Some times the layout
+engine place text labels on top of each other, and some times it place
+the class boxes too close to each other, not leaving room for the
+labels on the relationship arrows. The former can be worked around by
+placing extra newlines in the labes (ie "\n"). I did not do it here
+to be able to demonstrate the issue. I have not found a good way
+around the latter, so I normally try to reduce the problem by changing
+from vertical to horizontal links to improve the layout.</p>
+
+<p>All in all, I am quite happy with PlantUML, and very impressed with
+how quickly its lead developer responds to questions. So far I got an
+answer to my questions in a few hours when I send an email. I
+definitely recommend looking at PlantUML if you need to make UML
+diagrams. Note, PlantUML can draw a lot more than class relations.
+Check out the documention for a complete list. :)</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
<item>
- <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
- <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
- <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
- <description><p>At my nearby maker space,
-<a href="http://sonen.ifi.uio.no/">Sonen</a>, I heard the story that it
-was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
-on Windows and MacOS X than Linux, because the software involved had
-to be manually compiled and set up on Linux while premade packages
-worked out of the box on Windows and MacOS X. I found this annoying,
-as the software involved,
-<a href="https://github.com/Ultimaker/Cura">Cura</a>, is free software
-and should be trivial to get up and running on Linux if someone took
-the time to package it for the relevant distributions. I even found
-<a href="https://bugs.debian.org/706656">a request for adding into
-Debian</a> from 2013, which had seem some activity over the years but
-never resulted in the software showing up in Debian. So a few days
-ago I offered my help to try to improve the situation.</p>
-
-<p>Now I am very happy to see that all the packages required by a
-working Cura in Debian are uploaded into Debian and waiting in the NEW
-queue for the ftpmasters to have a look. You can track the progress
-on
-<a href="https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org">the
-status page for the 3D printer team</a>.</p>
-
-<p>The uploaded packages are a bit behind upstream, and was uploaded
-now to get slots in <a href="https://ftp-master.debian.org/new.html">the NEW
-queue</a> while we work up updating the packages to the latest
-upstream version.</p>
-
-<p>On a related note, two competitors for Cura, which I found harder
-to use and was unable to configure correctly for Ultimaker 2+ in the
-short time I spent on it, are already in Debian. If you are looking
-for 3D printer "slicers" and want something already available in
-Debian, check out
-<a href="https://tracker.debian.org/pkg/slic3r">slic3r</a> and
-<a href="https://tracker.debian.org/pkg/slic3r-prusa">slic3r-prusa</a>.
-The latter is a fork of the former.</p>
+ <title>Release 0.3 of free software archive API system Nikita announced</title>
+ <link>http://people.skolelinux.org/pere/blog/Release_0_3_of_free_software_archive_API_system_Nikita_announced.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_3_of_free_software_archive_API_system_Nikita_announced.html</guid>
+ <pubDate>Sun, 24 Mar 2019 14:30:00 +0100</pubDate>
+ <description><p>Yesterday, a new release of
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita
+Noark 5 core project</a> was
+<a href="https://lists.nuug.no/pipermail/nikita-noark/2019-March/000451.html">announced
+on the project mailing list</a>. The free software solution is an
+implementation of the Norwegian archive standard Noark 5 used by
+government offices in Norway. These were the changes in version 0.3
+since version 0.2.1 (from NEWS.md):</p>
+
+<ul>
+ <li>Improved ClassificationSystem and Class behaviour.</li>
+ <li>Tidied up known inconsistencies between domain model and hateaos links.</li>
+ <li>Added experimental code for blockchain integration. </li>
+ <li>Make token expiry time configurable at upstart from properties file.</li>
+ <li>Continued work on OData search syntax.</li>
+ <li>Started work on pagination for entities, partly implemented for Saksmappe.</li>
+ <li>Finalise ClassifiedCode Metadata entity.</li>
+ <li>Implement mechanism to check if authentication token is still
+ valid. This allow the GUI to return a more sensible message to the
+ user if the token is expired.</li>
+ <li>Reintroduce browse.html page to allow user to browse JSON API using
+ hateoas links.</li>
+ <li>Fix bug in handling file/mappe sequence number. Year change was
+ not properly handled.</li>
+ <li>Update application yml files to be in sync with current development.</li>
+ <li>Stop 'converting' everything to PDF using libreoffice. Only
+ convert the file formats doc, ppt, xls, docx, pptx, xlsx, odt, odp
+ and ods.</li>
+ <li>Continued code style fixing, making code more readable.</li>
+ <li>Minor bug fixes.</li>
+
+</ul>
+
+<p>If free and open standardized archiving API sound interesting to
+you, please contact us on IRC
+(<a href="irc://irc.freenode.net/%23nikita">#nikita on
+irc.freenode.net</a>) or email
+(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
+mailing list</a>).</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
<item>
- <title>Mangler du en skrue, eller har du en skrue løs?</title>
- <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</guid>
- <pubDate>Wed, 4 Oct 2017 09:40:00 +0200</pubDate>
- <description>Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike
-skruer. Det siste prosjektet jeg holder på med er å lage
-<a href="https://www.thingiverse.com/thing:676916">en boks til en
-HDMI-touch-skjerm</a> som skal brukes med Raspberry Pi. Boksen settes
-sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan
-få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har
-sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk
-tips for oss som bor i Oslo.
-<a href="http://www.zachskruer.no/">Zachariassen Jernvare AS</a> i
-<a href="http://www.openstreetmap.org/?mlat=59.93421&mlon=10.76795#map=19/59.93421/10.76795">Hegermannsgate
-23A på Torshov</a> har et fantastisk utvalg, og åpent mellom 09:00 og
-17:00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og
-så langt har jeg fått alt jeg har lett etter. De har i tillegg det
-meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg
-håper de har nok kunder til å holde det gående lenge, da dette er en
-butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i
-nabolaget for oss som liker å bygge litt selv. :)</p>
+ <title>Åpen og gjennomsiktig vedlikehold av spesifikasjonen for Noark 5 Tjenestegrensesnitt</title>
+ <link>http://people.skolelinux.org/pere/blog/_pen_og_gjennomsiktig_vedlikehold_av_spesifikasjonen_for_Noark_5_Tjenestegrensesnitt.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/_pen_og_gjennomsiktig_vedlikehold_av_spesifikasjonen_for_Noark_5_Tjenestegrensesnitt.html</guid>
+ <pubDate>Mon, 11 Mar 2019 16:00:00 +0100</pubDate>
+ <description><p>Et virksomhetsarkiv for meg, er et arbeidsverktøy der en enkelt kan
+finne informasjonen en trenger når en trenger det, og der
+virksomhetens samlede kunnskap er tilgjengelig. Det må være greit å
+finne frem i, litt som en bibliotek. Men der et bibliotek gjerne tar
+vare på offentliggjort informasjon som er tilgjengelig flere steder,
+tar et arkiv vare på virksomhetsintern og til tider personlig
+informasjon som ofte kun er tilgjengelig fra et sted.</p>
+
+<p>Jeg mistenker den eneste måten å sikre at arkivet inneholder den
+samlede kunnskapen i en virksomhet, er å bruke det som virksomhetens
+kunnskapslager. Det innebærer å automatisk kopiere (brev, epost,
+SMS-er etc) inn i arkivet når de sendes og mottas, og der filtrere
+vekk det en ikke vil ta vare på, og legge på metadata om det som er
+samlet inn for enkel gjenfinning. En slik bruk av arkivet innebærer at
+arkivet er en del av daglig virke, ikke at det er siste hvilested for
+informasjon ingen lenger har daglig bruk for. For å kunne være en del
+av det daglige virket må arkivet enkelt kunne integreres med andre
+systemer. I disse dager betyr det å tilby arkivet som en
+nett-tjeneste til hele virksomheten, tilgjengelig for både mennesker
+og datamaskiner. Det betyr i tur å både tilby nettsider og et
+maskinlesbart grensesnitt.</p>
+
+<p>For noen år siden erkjente visjonære arkivarer fordelene med et
+standardisert maskinlesbart grensesnitt til organisasjonens arkiv. De
+gikk igang med å lage noe de kalte
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">Noark
+5 Tjenestegrensesnitt</a>. Gjort riktig, så åpner slike maskinlesbare
+grensesnitt for samvirke på tvers av uavhengige programvaresystemer.
+Gjort feil, vil det blokkere for samvirke og bidra til
+leverandørinnlåsing. For å gjøre det riktig så må grensesnittet være
+klart og entydig beskrevet i en spesifikasjon som gjør at
+spesifikasjonen tolkes på samme måte uavhengig av hvem som leser den,
+og uavhengig av hvem som tar den i bruk.</p>
+
+<p>For å oppnå klare og entydige beskrivelser i en spesifikasjon, som
+trengs for å kunne få en fri og åpen standard (se
+<a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">Digistan-definisjon</a>),
+så trengs det en åpen og gjennomsiktig inngangsport med lav terskel,
+der de som forsøker å ta den i bruk enkelt kan få inn korreksjoner,
+etterlyse klargjøringer og rapportere uklarheter i spesifikasjonen.
+En trenger også automatiserte datasystemer som måler og sjekker at et
+gitt grensesnitt fungerer i tråd med spesifikasjonen.</p>
+
+<p>For Noark 5 Tjenestegrensesnittet er det nå etablert en slik åpen
+og gjennomsiktig inngangsport på prosjekttjenesten github. Denne
+inngangsporten består først og fremst av en åpen portal som lar enhver
+se hva som er gjort av endringer i spesifikasjonsteksten over tid, men
+det hører også med et åpent &quot;diskusjonsforum&quot; der en kan
+komme med endringsforslag og forespørsler om klargjøringer. Alle
+registrerte brukere på github kan bidra med innspill til disse
+henvendelsene.</p>
+
+<p>I samarbeide med Arkivverket har jeg fått opprettet et git-depot
+med spesifikasjonsteksten for tjenestegrensesnittet, der det er lagt
+inn historikk for endringer i teksten de siste årene, samt lagt inn
+endringsforslag og forespørsler om klargjøring av teksten. Bakgrunnen
+for at jeg bidro med dette er at jeg er involvert i
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">Nikita-prosjektet</a>,
+som lager en fri programvare-utgave av Noark 5 Tjenestegrensesnitt.
+Det er først når en forsøker å lage noe i tråd med en spesifikasjon at
+en oppdager hvor mange detaljer som må beskrives i spesifikasjonen for
+å sikre samhandling.</p>
+
+<p>Spesifikasjonen vedlikeholdes i et rent tekstformat, for å ha et
+format egnet for versjonskontroll via versjontrollsystemet git. Dette
+gjør det både enkelt å se konkret hvilke endringer som er gjort når,
+samt gjør det praktisk mulig for enhver med github-konto å sende inn
+endringsforslag med formuleringer til spesifikasjonsteksten. Dette
+tekstformatet vises frem som nettsider på github, slik at en ikke
+trenger spesielle verktøy for å se på siste utgave av
+spesifikasjonen.</p>
+
+<p>Fra dette rene tekstformatet kan det så avledes ulike formater, som
+HTML for websider, PDF for utskrift på papir og ePub for lesing med
+ebokleser. Avlednings-systemet (byggesystemet) bruker i dag
+verktøyene pandoc, latex, docbook-xsl og GNU make til
+transformasjonen. Tekstformatet som brukes dag er
+<a href="https://www.markdownguide.org/">Markdown</a>, men det vurderes
+å
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/9">endre
+til formatet RST</a> i fremtiden for bedre styring av utseende på
+PDF-utgaven.</p>
+
+<p>Versjonskontrollsystemet git ble valgt da det er både fleksibelt,
+avansert og enkelt å ta i bruk. Github ble valgt (foran f.eks. Gitlab
+som vi bruker i Nikita), da Arkivverket allerede hadde tatt i bruk
+Github i andre sammenhenger.</p>
+
+<p>Enkle endringer i teksten kan gjøres av priviligerte brukere
+direkte i nettsidene til Github, ved å finne aktuell fil som skal
+endres (f.eks. kapitler/03-konformitet.md), klikke på den lille
+bokstaven i høyre hjørne over teksten. Det kommer opp en nettside der
+en kan endre teksten slik en ønsker. Når en er fornøyd med endringen
+så må endringen &quot;sjekkes inn&quot; i historikken. Det gjøres ved
+å gi en kort beskrivelse av endringen (beskriv helst hvorfor endringen
+trengs, ikke hva som er endret), under overskriften &quot;Commit
+changes&quot;. En kan og bør legge inn en lengre forklaring i det
+større skrivefeltet, før en velger om endringen skal sendes direkte
+til 'master'-grenen (dvs. autorativ utgave av spesifikasjonen) eller
+om en skal lage en ny gren for denne endringen og opprette en
+endringsforespørsel (aka &quot;Pull Request&quot;/PR). Når alt dette
+er gjort kan en velge &quot;Commit changes&quot; for å sende inn
+endringen. Hvis den er lagt inn i &quot;master&quot;-grenen så er den
+en offisiell del av spesifikasjonen med en gang. Hvis den derimot er
+en endringsforespørsel, så legges den inn i
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/pulls">listen
+over forslag til endringer</a> som venter på korrekturlesing og
+godkjenning.</p>
+
+<p>Større endringer (for eksempel samtidig endringer i flere filer)
+gjøres enklest ved å hente ned en kopi av git-depoet lokalt og gjøre
+endringene der før endringsforslaget sendes inn. Denne prosessen er
+godt beskrivet i dokumentasjon fra github. Git-prosjektet som skal
+&quot;klones&quot; er
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/</a>.</p>
+
+<p>For å registrere nye utfordringer (issues) eller kommentere på
+eksisterende utfordringer benyttes nettsiden
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues">https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues</a>.
+I skrivende stund er det 48 åpne og 11 avsluttede utfordringer. Et
+forslag til hva som bør være med når en beskriver en utfordring er
+tilgjengelig som utfordring
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/14">#14</a>.</p>
+
+<p>For å bygge en PDF-utgave av spesifikasjonen så bruker jeg i dag en
+Debian GNU/Linux-maskin med en rekke programpakker installert. Når
+dette er på plass, så holder det å kjøre kommandoen 'make pdf html' på
+kommandolinjen, vente ca. 20 sekunder, før spesifikasjon.pdf og
+spesifikasjon.html ligger klar på disken. Verktøyene for bygging av
+PDF, HTML og ePub-utgave er også tilgjengelig på Windows og
+MacOSX.</p>
+
+<p>Github bidrar med rammeverket. Men for at åpent vedlikehold av
+spesifikasjonen skal fungere, så trengs det folk som bidrar med sin
+tid og kunnskap. Arkivverket har sagt de skal bidra med innspill og
+godkjenne forslag til endringer, men det blir størst suksess hvis alle
+som bruker og lager systemer basert på Noark 5 Tjenestegrensesnitt
+bidrar med sin kunnskap og kommer med forslag til forebedringer. Jeg
+stiller. Blir du med?</p>
+
+<p>Det er viktig å legge til rette for åpen diskusjon blant alle
+interesserte, som ikke krever at en må godta lange kontrakter med
+vilkår for deltagelse. Inntil Arkivverket dukker opp på IRC har vi
+laget en IRC-kanal der interesserte enkelt kan orientere seg og
+diskutere tjenestegrensesnittet. Alle er velkommen til å ta turen
+innom
+<a href="https://webchat.freenode.net/?channels=nikita">#nikita</a>
+(f.eks. via irc.freenode.net) for å møte likesinnede.</p>
+
+<p>Det holder dog ikke å ha en god spesifikasjon, hvis ikke de som tar
+den i bruk gjør en like god jobb. For å automatisk teste om et konkret
+tjenestegrensesnitt følger (min) forståelse av
+spesifikasjonsdokumentet, har jeg skrevet et program som kobler seg
+opp til et Noark 5v4 REST-tjeneste og tester alt den finner for å se
+om det er i henhold til min tolkning av spesifikasjonen. Dette
+verktøyet er tilgjengelig fra
+<a href="https://github.com/petterreinholdtsen/noark5-tester">https://github.com/petterreinholdtsen/noark5-tester</a>,
+og brukes daglig mens vi utvikler Nikita for å sikre at vi ikke
+introduserer nye feil. Hvis en skal sikre samvirke på tvers av ulike
+systemer er det helt essensielt å kunne raskt og automatisk sjekke at
+tjenestegrensesnittet oppfører seg som forventet. Jeg håper andre som
+lager sin utgave av tjenestegrensesnittet vi bruke dette verktøyet,
+slik at vi tidlig og raskt kan oppdage hvor vi har tolket
+spesifikasjonen ulikt, og dermed få et godt grunnlag for å gjøre
+spesifikasjonsteksten enda klarere og bedre.</p>
+
+<p>Dagens beskrivelse av Noark 5 Tjenestegrensesnitt er et svært godt
+utgangspunkt for å gjøre virksomhetens arkiv til et dynamisk og
+sentralt arbeidsverktøy i organisasjonen. Blir du med å gjøre den
+enda bedre?</p>
</description>
</item>
<item>
- <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
- <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
- <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
- <description><p>Every mobile phone announce its existence over radio to the nearby
-mobile cell towers. And this radio chatter is available for anyone
-with a radio receiver capable of receiving them. Details about the
-mobile phones with very good accuracy is of course collected by the
-phone companies, but this is not the topic of this blog post. The
-mobile phone radio chatter make it possible to figure out when a cell
-phone is nearby, as it include the SIM card ID (IMSI). By paying
-attention over time, one can see when a phone arrive and when it leave
-an area. I believe it would be nice to make this information more
-available to the general public, to make more people aware of how
-their phones are announcing their whereabouts to anyone that care to
-listen.</p>
-
-<p>I am very happy to report that we managed to get something
-visualizing this information up and running for
-<a href="http://norwaymakers.org/osf17">Oslo Skaperfestival 2017</a>
-(Oslo Makers Festival) taking place today and tomorrow at Deichmanske
-library. The solution is based on the
-<a href="http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html">simple
-recipe for listening to GSM chatter</a> I posted a few days ago, and
-will show up at the stand of <a href="http://sonen.ifi.uio.no/">Åpen
-Sone from the Computer Science department of the University of
-Oslo</a>. The presentation will show the nearby mobile phones (aka
-IMSIs) as dots in a web browser graph, with lines to the dot
-representing mobile base station it is talking to. It was working in
-the lab yesterday, and was moved into place this morning.</p>
-
-<p>We set up a fairly powerful desktop machine using Debian
-Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
-connected and visualize the visible cell phone towers using an
-<a href="https://github.com/marlow925/hopglass">English version of
-Hopglass</a>. A fairly powerfull machine is needed as the
-grgsm_livemon_headless processes from
-<a href="https://tracker.debian.org/pkg/gr-gsm">gr-gsm</a> converting
-the radio signal to data packages is quite CPU intensive.</p>
-
-<p>The frequencies to listen to, are identified using a slightly
-patched scan-and-livemon (to set the --args values for each receiver),
-and the Hopglass data is generated using the
-<a href="https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output">patches
-in my meshviewer-output branch</a>. For some reason we could not get
-more than four SDRs working. There is also a geographical map trying
-to show the location of the base stations, but I believe their
-coordinates are hardcoded to some random location in Germany, I
-believe. The code should be replaced with code to look up location in
-a text file, a sqlite database or one of the online databases
-mentioned in
-<a href="https://github.com/Oros42/IMSI-catcher/issues/14">the github
-issue for the topic</a>.
-
-<p>If this sound interesting, visit the stand at the festival!</p>
+ <title>Dårlig med sikkerhetsoppdateringer for Ruters billettautomater i Oslo?</title>
+ <link>http://people.skolelinux.org/pere/blog/D_rlig_med_sikkerhetsoppdateringer_for_Ruters_billettautomater_i_Oslo_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/D_rlig_med_sikkerhetsoppdateringer_for_Ruters_billettautomater_i_Oslo_.html</guid>
+ <pubDate>Wed, 13 Feb 2019 10:45:00 +0100</pubDate>
+ <description><p><a href="http://people.skolelinux.org/pere/blog/Er_billettautomatene_til_kollektivtrafikken_i_Oslo_uten_sikkerhetsoppdateringer_.html">For
+syv år siden</a> oppdaget jeg at billettautomater for
+kollektivtrafikken i Oslo kjørte
+<a href="http://en.wikipedia.org/wiki/Windows_2000">Windows 2000
+Professional</a>. Operativsystemet har ikke fått sikkerhetsfikser fra
+Microsoft siden 2010-07-13 i følge dem selv. Den samme versjonen av
+operativsystemet var i bruk
+<a href="http://people.skolelinux.org/pere/blog/Fortsatt_ingen_sikkerhetsoppdateringer_for_billettautomatene_til_kollektivtrafikken_i_Oslo_.html">for
+to og et halvt år siden</a>, og jammen er det ikke også i bruk den dag
+i dag:</p>
+
+<p align="center"><a href="http://people.skolelinux.org/pere/blog/images/2019-02-13-ruter-win2000pro.jpeg"><img width="40%" src="http://people.skolelinux.org/pere/blog/images/2019-02-13-ruter-win2000pro.jpeg" alt="[Bilde av Ruters billettautomat med Windows 2000-feilmelding]"></a></p>
+
+<p>Bildet er tatt i dag av Kirill Miazine og tilgjengelig for bruk med
+bruksvilkårene til
+<a href="http://creativecommons.org/licenses/by/4.0/">Creative
+Commons Attribution 4.0 International (CC BY 4.0)</a>.</p>
+
+<p>Kanskje det hadde vært
+<a href="https://www.aftenposten.no/osloby/i/awqgO/Her-kjorer-du-gratis-trikk-og-buss">bedre
+med gratis kollektivtrafikk</A>, slik at vi slapp å stole på
+datakompetansen til Ruter for å verne våre privatliv samt holde
+personopplysninger og betalingsinformasjon unna uvedkommende. Eneste
+måten å sikre at hvor en befinner seg ikke kan hentes ut fra Ruters
+systemer er å betale enkeltbilletter med kontanter. Jeg vet at Ruter
+har en god historie om hvor personvernvennlige mobil-app og
+RFID-kortene er, men den historien er ikke mulig å uavhengig
+kontrollere uten priviligert tilgang til interne system og blir dermed
+bare nok en god historie basert på tillit til de som forteller
+historien. Det er ikke slik en sikrer privatsfæren. Det gjør en ved
+å sikre at det ikke (kan) registreres informasjon om ens person.</p>
+
+<p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
+det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
+til min adresse
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
<item>
- <title>Easier recipe to observe the cell phones around you</title>
- <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
- <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
- <description><p>A little more than a month ago I wrote
-<a href="http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html">how
-to observe the SIM card ID (aka IMSI number) of mobile phones talking
-to nearby mobile phone base stations using Debian GNU/Linux and a
-cheap USB software defined radio</a>, and thus being able to pinpoint
-the location of people and equipment (like cars and trains) with an
-accuracy of a few kilometer. Since then we have worked to make the
-procedure even simpler, and it is now possible to do this without any
-manual frequency tuning and without building your own packages.</p>
-
-<p>The <a href="https://tracker.debian.org/pkg/gr-gsm">gr-gsm</a>
-package is now included in Debian testing and unstable, and the
-IMSI-catcher code no longer require root access to fetch and decode
-the GSM data collected using gr-gsm.</p>
-
-<p>Here is an updated recipe, using packages built by Debian and a git
-clone of two python scripts:</p>
-
-<ol>
-
-<li>Start with a Debian machine running the Buster version (aka
- testing).</li>
-
-<li>Run '<tt>apt install gr-gsm python-numpy python-scipy
- python-scapy</tt>' as root to install required packages.</li>
-
-<li>Fetch the code decoding GSM packages using '<tt>git clone
- github.com/Oros42/IMSI-catcher.git</tt>'.</li>
-
-<li>Insert USB software defined radio supported by GNU Radio.</li>
-
-<li>Enter the IMSI-catcher directory and run '<tt>python
- scan-and-livemon</tt>' to locate the frequency of nearby base
- stations and start listening for GSM packages on one of them.</li>
-
-<li>Enter the IMSI-catcher directory and run '<tt>python
- simple_IMSI-catcher.py</tt>' to display the collected information.</li>
-
-</ol>
-
-<p>Note, due to a bug somewhere the scan-and-livemon program (actually
-<a href="https://github.com/ptrkrysik/gr-gsm/issues/336">its underlying
-program grgsm_scanner</a>) do not work with the HackRF radio. It does
-work with RTL 8232 and other similar USB radio receivers you can get
-very cheaply
-(<a href="https://www.ebay.com/sch/items/?_nkw=rtl+2832">for example
-from ebay</a>), so for now the solution is to scan using the RTL radio
-and only use HackRF for fetching GSM data.</p>
-
-<p>As far as I can tell, a cell phone only show up on one of the
-frequencies at the time, so if you are going to track and count every
-cell phone around you, you need to listen to all the frequencies used.
-To listen to several frequencies, use the --numrecv argument to
-scan-and-livemon to use several receivers. Further, I am not sure if
-phones using 3G or 4G will show as talking GSM to base stations, so
-this approach might not see all phones around you. I typically see
-0-400 IMSI numbers an hour when looking around where I live.</p>
-
-<p>I've tried to run the scanner on a
-<a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi 2 and 3
-running Debian Buster</a>, but the grgsm_livemon_headless process seem
-to be too CPU intensive to keep up. When GNU Radio print 'O' to
-stdout, I am told there it is caused by a buffer overflow between the
-radio and GNU Radio, caused by the program being unable to read the
-GSM data fast enough. If you see a stream of 'O's from the terminal
-where you started scan-and-livemon, you need a give the process more
-CPU power. Perhaps someone are able to optimize the code to a point
-where it become possible to set up RPi3 based GSM sniffers? I tried
-using Raspbian instead of Debian, but there seem to be something wrong
-with GNU Radio on raspbian, causing glibc to abort().</p>
+ <title>Stortinget vedtar maskinlesbart register over 20% av selskapseierne i Norge</title>
+ <link>http://people.skolelinux.org/pere/blog/Stortinget_vedtar_maskinlesbart_register_over_20__av_selskapseierne_i_Norge.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Stortinget_vedtar_maskinlesbart_register_over_20__av_selskapseierne_i_Norge.html</guid>
+ <pubDate>Thu, 7 Feb 2019 23:55:00 +0100</pubDate>
+ <description><p>Jeg registrerer med glede at Stortinget i dag har
+<a href="https://www.stortinget.no/no/Saker-og-publikasjoner/Saker/Sak/?p=72826">vedtatt
+at det skal vedlikeholdes et åpent og maskinlesbart register over
+reelle rettighetshavere i Norge</a>. Her kan en kanskje få et
+register som kan brukes til å analysere eierskap og kontroll i Norge
+maskinelt og knytte det til internasjonale databaser som
+<a href="https://opencorporates.com/">OpenCorporates</a>. Det liker
+jeg.</p>
+
+<p>Den vedtatte grense på 25 prosents eierandel fikk stor
+oppmerksomhet i debatten. Jeg ser fra enkel analyse av skatteetatens
+eierskapsregister at 80.4% av alle selskapseiere i registeret har
+mindre enn 25% eierandel, mot 73.8% som har mindre enn 5% eierandel.
+En grense på 25% vil altså utelukke 80.4% av selskapseierne fra det
+vedtatte registeret, og en grense på 5% vil skjule 73.8%. En må helt
+ned i registrering av eierandeler over circa 0.002% for å få mer enn
+halvparten av selskapseierne i Norge. Mon tro hvor langt ned en må i
+eierprosent for å få med alle eierskapene til politisk valgte
+representanter?</p>
+
+<p>Jeg biter meg også merke i at Sivert Bjørnstad fra FrP
+tilsynelatende tror at aksjonærregisteret er et eksisterende åpent
+register, på tross av at det så vidt jeg vet kun deles ved personlig
+oppmøte hos skatteetaten og ikke er tilgjengelig i maskinlesbart
+format for enhver, og dermed så langt ikke er importert inn i
+OpenCorporates. Det anser jeg ikke for et spesielt åpent register.
+Debatten ga ellers lite håp om at situasjonen bedrer seg, da
+finansministeren bare henviste til en fraværende næringsministeren og
+ikke ville uttale seg om et skikkelig aksjonærregister snart dukker
+opp.</p>
+
+<p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
+det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
+til min adresse
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
<item>
- <title>Datalagringsdirektivet kaster skygger over Høyre og Arbeiderpartiet</title>
- <link>http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html</guid>
- <pubDate>Thu, 7 Sep 2017 21:35:00 +0200</pubDate>
- <description><p>For noen dager siden publiserte Jon Wessel-Aas en bloggpost om
-«<a href="http://www.uhuru.biz/?p=1821">Konklusjonen om datalagring som
-EU-kommisjonen ikke ville at vi skulle få se</a>». Det er en
-interessant gjennomgang av EU-domstolens syn på snurpenotovervåkning
-av befolkningen, som er klar på at det er i strid med
-EU-lovgivingen.</p>
-
-<p>Valgkampen går for fullt i Norge, og om noen få dager er siste
-frist for å avgi stemme. En ting er sikkert, Høyre og Arbeiderpartiet
-får ikke min stemme
-<a href="http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_gj_r_at_Oslo_H_yre_og_Arbeiderparti_ikke_f_r_min_stemme_i__r.html">denne
-gangen heller</a>. Jeg har ikke glemt at de tvang igjennom loven som
-skulle pålegge alle data- og teletjenesteleverandører å overvåke alle
-sine kunder. En lov som er vedtatt, og aldri opphevet igjen.</p>
-
-<p>Det er tydelig fra diskusjonen rundt grenseløs digital overvåkning
-(eller "Digital Grenseforsvar" som det kalles i Orvellisk nytale) at
-hverken Høyre og Arbeiderpartiet har noen prinsipielle sperrer mot å
-overvåke hele befolkningen, og diskusjonen så langt tyder på at flere
-av de andre partiene heller ikke har det. Mange av
-<a href="https://data.holderdeord.no/votes/1301946411e">de som stemte
-for Datalagringsdirektivet i Stortinget</a> (64 fra Arbeiderpartiet,
-25 fra Høyre) er fortsatt aktive og argumenterer fortsatt for å radere
-vekk mer av innbyggernes privatsfære.</p>
-
-<p>Når myndighetene demonstrerer sin mistillit til folket, tror jeg
-folket selv bør legge litt innsats i å verne sitt privatliv, ved å ta
-i bruk ende-til-ende-kryptert kommunikasjon med sine kjente og kjære,
-og begrense hvor mye privat informasjon som deles med uvedkommende.
-Det er jo ingenting som tyder på at myndighetene kommer til å være vår
-privatsfære.
-<a href="http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html">Det
-er mange muligheter</a>. Selv har jeg litt sans for
-<a href="https://ring.cx/">Ring</a>, som er basert på p2p-teknologi
-uten sentral kontroll, er fri programvare, og støtter meldinger, tale
-og video. Systemet er tilgjengelig ut av boksen fra
-<a href="https://tracker.debian.org/pkg/ring">Debian</a> og
-<a href="https://launchpad.net/ubuntu/+source/ring">Ubuntu</a>, og det
-finnes pakker for Android, MacOSX og Windows. Foreløpig er det få
-brukere med Ring, slik at jeg også bruker
-<a href="https://signal.org/">Signal</a> som nettleserutvidelse.</p>
+ <title>Websocket from Kraken in Valutakrambod</title>
+ <link>http://people.skolelinux.org/pere/blog/Websocket_from_Kraken_in_Valutakrambod.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Websocket_from_Kraken_in_Valutakrambod.html</guid>
+ <pubDate>Fri, 1 Feb 2019 22:25:00 +0100</pubDate>
+ <description><p>Yesterday, the Kraken virtual currency exchange announced
+<a href="https://blog.kraken.com/post/2019/websockets-public-api-launching-soon/">their
+Websocket service</a>, providing a stream of exchange updates to its
+clients. Getting updated rates quickly is a good idea, so I used
+their <a href="https://www.kraken.com/en-us/help/websocket-api">API
+documentation</a> and added Websocket support to the Kraken service in
+Valutakrambod today. The python library can now get updates
+from Kraken several times per second, instead of every time the
+information is polled from the REST API.</p>
+
+<p>If this sound interesting to you, the code for valutakrambod is
+available from
+<a href="http://github.com/petterreinholdtsen/valutakrambod">github</a>.
+Here is example output from the example client displaying rates in a
+curses view:</p>
+
+<p><blockquote><pre>
+ Name Pair Bid Ask Spr Ftcd Age
+ BitcoinsNorway BTCEUR 2959.2800 3021.0500 2.0% 36 nan nan
+ Bitfinex BTCEUR 3087.9000 3088.0000 0.0% 36 37 nan
+ Bitmynt BTCEUR 3001.8700 3135.4600 4.3% 36 52 nan
+ Bitpay BTCEUR 3003.8659 nan nan% 35 nan nan
+ Bitstamp BTCEUR 3008.0000 3010.2300 0.1% 0 1 1
+ Bl3p BTCEUR 3000.6700 3010.9300 0.3% 1 nan nan
+ Coinbase BTCEUR 2992.1800 3023.2500 1.0% 34 nan nan
+ Kraken+BTCEUR 3005.7000 3006.6000 0.0% 0 1 0
+ Paymium BTCEUR 2940.0100 2993.4400 1.8% 0 2688 nan
+ BitcoinsNorway BTCNOK 29000.0000 29360.7400 1.2% 36 nan nan
+ Bitmynt BTCNOK 29115.6400 29720.7500 2.0% 36 52 nan
+ Bitpay BTCNOK 29029.2512 nan nan% 36 nan nan
+ Coinbase BTCNOK 28927.6000 29218.5900 1.0% 35 nan nan
+ MiraiEx BTCNOK 29097.7000 29741.4200 2.2% 36 nan nan
+ BitcoinsNorway BTCUSD 3385.4200 3456.0900 2.0% 36 nan nan
+ Bitfinex BTCUSD 3538.5000 3538.6000 0.0% 36 45 nan
+ Bitpay BTCUSD 3443.4600 nan nan% 34 nan nan
+ Bitstamp BTCUSD 3443.0100 3445.0500 0.1% 0 2 1
+ Coinbase BTCUSD 3428.1600 3462.6300 1.0% 33 nan nan
+ Gemini BTCUSD 3445.8800 3445.8900 0.0% 36 326 nan
+ Hitbtc BTCUSD 3473.4700 3473.0700 -0.0% 0 0 0
+ Kraken+BTCUSD 3444.4000 3445.6000 0.0% 0 1 0
+ Exchangerates EURNOK 9.6685 9.6685 0.0% 36 22226 nan
+ Norgesbank EURNOK 9.6685 9.6685 0.0% 36 22226 nan
+ Bitstamp EURUSD 1.1440 1.1462 0.2% 0 1 2
+ Exchangerates EURUSD 1.1471 1.1471 0.0% 36 22226 nan
+ BitcoinsNorway LTCEUR 1.0009 22.6538 95.6% 35 nan nan
+ BitcoinsNorway LTCNOK 259.0900 264.9300 2.2% 35 nan nan
+ BitcoinsNorway LTCUSD 0.0000 29.0000 100.0% 35 nan nan
+ Norgesbank USDNOK 8.4286 8.4286 0.0% 36 22226 nan
+</pre></blockquote></p>
+
+<p>Yes, I notice the strange negative spread on Hitbtc. I've seen the
+same on Kraken. Another strange observation is that Kraken some times
+announce trade orders a fraction of a second in the future. I really
+wonder what is going on there.</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
projects / homepage.git / blobdiff