New post.

diff --git a/blog/data/2017-02-21-ooxml-undefined.txt b/blog/data/2017-02-21-ooxml-undefined.txt
new file mode 100644 (file)
index 0000000..21cb180
--- /dev/null
+++ b/blog/data/2017-02-21-ooxml-undefined.txt
@@ -0,0 +1,25 @@
+Title: Detect OOXML files with undefined behaviour?
+Tags: english, nuug, standard
+Date: 2017-02-21 00:20
+
+<p>I just noticed
+<a href="http://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">the
+new Norwegian proposal for archiving rules in the goverment</a> list
+<a href="http://www.ecma-international.org/publications/standards/Ecma-376.htm">ECMA-376</a>
+/ ISO/IEC 29500 (aka OOXML) as valid formats to put in long term
+storage.  Luckily such files will only be accepted based on
+pre-approval from the National Archive.  Allowing OOXML files to be
+used for long term storage might seem like a good idea as long as we
+forget that there are plenty of ways for a "valid" OOXML document to
+have content with no defined interpretation in the standard, which
+lead to a question and an idea.</p>
+
+<p>Is there any tool to detect if a OOXML document depend on such
+undefined behaviour?  It would be useful for the National Archive (and
+anyone else interested in verifying that a document is well defined)
+to have such tool available when considering to approve the use of
+OOXML.  I'm aware of the
+<a href="https://github.com/arlm/officeotron/">officeotron OOXML
+validator</a>, but do not know how complete it is nor if it will
+report use of undefined behaviour.  Are there other similar tools
+available?  Please send me an email if you know of any such tool.</p>