odb ODF standard conformance [was: minutes of ESC call ...]

On Thu, Dec 19, 2013 at 08:24:29PM +0000, Michael Meeks wrote:

> * Crashtest update (Markus)
>     + cf. http://dev-builds.libreoffice.org/crashtest/
>       new crash testing result is available (cf. the date & git hash)
>       All files tested, and the results are complete for the 1st time.
>       and that all odb files are not valid according to the validator
>         + need to look at the standard (Lionel)
>             + presumably some silly error ...

Here are the main classes of "low hanging fruit" conformance errors I
see:

1) xlink:href without xlink:type

   Easy to fix if (as I assume) I can always put "simple" in these
   places. I have a patch sitting in my tree to do that.

2) manifest:manifest without version attribute: I have no clue what
   version I should put there. Any hint?

3) ODF mimetype 'application/vnd.oasis.opendocument.base' is invalid

   Well,
   
http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1420388_253892949
   lists this as the "recommended" mimetype but that the
   RFC4288-registration is "in progress". Shouldn't we rather move
   forward on the registration... which has been stalled... why?

I need help on these:

1) fdo36288-2.odb/forms/Obj42/content.xml[2,17145]:  Error: attribute
   "xlink:href" has a bad value: ".uno:FormController/saveRecord" does
   not satisfy the "anyURI" type

   What is the "right" way to put a .uno URI?

2) ooo103006-1.odb/reports/Obj131/content.xml[2,6115]:  Error: element
   "form:hidden" is missing "id" attribute

   This one probably just needs an ID generated. Shall we just call
   something like BASE64ENCODE(RANDOM(give me 9 bytes))? Or is there a
   more structured system in LibreOffice?

These need some "real" investigation:

1) fdo40381-1.odb/content.xml[2,3672]:  Error: uncompleted content model. expecting: <column>

2) srv/crashtestdata/current/home/buildslave/source/bugdocs2/odb/fdo36288-2.odb/content.xml[2,3901]:
   Error: unexpected attribute "db:type-name"

3) ooo103006-1.odb/content.xml[2,42566]:  Error: element "db:order-statement" was found where no 
element may occur

4) ooo103006-1.odb/content.xml[2,42818]:  Error: unexpected attribute "db:help-message"

5) ooo103006-1.odb/forms/Obj21/content.xml[2,121903]:  Error: "control149" is referenced by an 
IDREF, but not defined.

I doubt that these actually come from base-specific code, but who
knows:

1) forms/Obj11/styles.xml:  Error: unexpected attribute "style:layout-grid-snap-to-characters"

2) fdo36288-2.odb/content.xml[2,2887]:  Error: tag name
   "db:font-charset" is not allowed. Possible tag names are:
   <character-set>,<table-settings>

-- 
Lionel