blog/archive/2019/05/05.rss

   1 <?xml version="1.0" encoding="ISO-8859-1"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries from May 2019</title>
   5                 <description>Entries from May 2019</description>
   6                 <link>http://people.skolelinux.org/pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>MIME type &quot;text/vnd.sosi&quot; for SOSI map data</title>
  11                 <link>http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</guid>
  13                 <pubDate>Mon, 20 May 2019 08:35:00 +0200</pubDate>
  14                 <description>&lt;p&gt;As part of my involvement in the work to
  15 &lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard&quot;&gt;standardise
  16 a REST based API for Noark 5&lt;/a&gt;, the Norwegian archiving standard, I
  17 spent some time the last few months to try to register a
  18 &lt;a href=&quot;https://www.iana.org/assignments/media-types/&quot;&gt;MIME type&lt;/a&gt;
  19 and &lt;a href=&quot;https://www.nationalarchives.gov.uk/PRONOM/&quot;&gt;PRONOM
  20 code&lt;/a&gt; for the SOSI file format.  The background is that there is a
  21 set of formats approved for long term storage and archiving in Norway,
  22 and among these formats, SOSI is the only format missing a MIME type
  23 and PRONOM code.&lt;/p&gt;
  24
  25 &lt;p&gt;What is SOSI, you might ask?  To quote Wikipedia: SOSI is short for
  26 Samordnet Opplegg for Stedfestet Informasjon (literally &quot;Coordinated
  27 Approach for Spatial Information&quot;, but more commonly expanded in
  28 English to Systematic Organization of Spatial Information).  It is a
  29 text based file format for geo-spatial vector information used in
  30 Norway.  Information about the SOSI format can be found in English
  31 from &lt;a href=&quot;https://en.wikipedia.org/wiki/SOSI&quot;&gt;Wikipedia&lt;/a&gt;.  The
  32 specification is available in Norwegian from
  33 &lt;a href=&quot;https://www.kartverket.no/geodataarbeid/Standarder/SOSI/&quot;&gt;the
  34 Norwegian mapping authority&lt;/a&gt;.  The SOSI standard, which originated
  35 in the beginning of nineteen eighties, was the inspiration and formed the
  36 basis for the XML based
  37 &lt;a href=&quot;https://en.wikipedia.org/wiki/Geography_Markup_Language&quot;&gt;Geography
  38 Markup Language&lt;/a&gt;.&lt;/p&gt;
  39
  40 &lt;p&gt;I have so far written
  41 &lt;a href=&quot;https://github.com/file/file/pull/67&quot;&gt;a pattern matching
  42 rule&lt;/a&gt; for the file(1) unix tool to recognize SOSI files, submitted
  43 a request to the PRONOM project to have a PRONOM ID assigned to the
  44 format (reference TNA1555078202S60), and today send a request to IANA
  45 to register the &quot;text/vnd.sosi&quot; MIME type for this format (referanse
  46 &lt;a href=&quot;https://tools.iana.org/public-view/viewticket/1143144&quot;&gt;IANA
  47 #1143144&lt;/a&gt;).  If all goes well, in a few months, anyone implementing
  48 the Noark 5 Tjenestegrensesnitt API spesification should be able to
  49 use an official MIME type and PRONOM code for SOSI files.  In
  50 addition, anyone using SOSI files on Linux should be able to
  51 automatically recognise the format and web sites handing out SOSI
  52 files can begin providing a more specific MIME type.  So far, SOSI
  53 files has been handed out from web sites using the
  54 &quot;application/octet-stream&quot; MIME type, which is just a nice way of
  55 stating &quot;I do not know&quot;.  Soon, we will know. :)&lt;/p&gt;
  56
  57 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
  58 activities, please send Bitcoin donations to my address
  59 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  60 </description>
  61         </item>
  62
  63         </channel>
  64 </rss>