I forgot something, if I want to make an application/xml document (and
whether this is required and what else is permitted, like a <!DOCTYPE ...>
is a bit vague in the ODF specifications, since the XML specification allows
both and requires neither):
- - - - - - -
<?xml version="1.0" encoding="UTF-8" ?>
<!-- Minimum Required ODF 1.0/1.1 Text Document
There is one for each of the main document
types. There is a package equivalent that
has the same office:body in an office:document-
content element in content.xml and has the MIMETYPE
in the special first-item of the package.
For a text template, just change the mimetype.
-->
<o:document
xmlns:o="urn:oasis:names:tc:opendocument:xmlns:office:1.0"
o:mimetype="application/vnd.oasis.opendocument.text"
>
<o:body>
<o:text />
</o:body>
<!-- Singing: I ain't got no body, no body have I ... -->
</o:document>
- - - - - - -
-----Original Message-----
From: Dennis E. Hamilton [mailto:]
Sent: Monday, January 19, 2009 15:19
To:
Cc: ; Bart Hanssens
Subject: RE: [office] ODF 1.2 Single-Level Conformance and Floor << Ceiling
Already
[ ... ]
The following example is ridiculous (and Bart Hanssens will raise his
eyebrows), but it points out the most (or least, depending on perspective)
that any ODF processor has to deal with. Acceptance of all sorts of
additional content must be acceptable, but support for it at the processing
or semantic level is not. This is a far bigger deal for interoperability
than whether or not foreign elements are allowed, with or without some
proviso that the reduction to a conformant document be benign. Keeping in
mind that the world is a mostly-practical, often-realistic, place, and no
one could get a way with this, here is all that the letter of the ODF law
requires.
[ ... ]
