OASIS Open Document Format for Office Applications (OpenDocument) TC

 View Only
  • 1.  What is the correct value of dsig:version on element

    Posted 03-04-2024 15:48

    Dear ODF TC

     

    In reviewing Part 2, I realise that the generated text for elements and attributes in the 'dsig' namespace has not been updated. I believe that the only update for ODF 1.4, if any, is to the fixed value of the dsig:version attribute on element <dsig:document-signatures>. My understanding is that the value should be the same as the ODF version number, i.e. "1.4".

     

    In the published OASIS standard for ODF 1.3 the fixed value of the dsig:version attribute is stated in the schema to be "1.3", but in the Part 2 specification it is stated to be "1.2", including in the generated text box (which clearly wasn't re-generated). This conflict between schema and Part 2 looks to me like a fairly serious error.

     

    I'd appreciate your guidance on fixing this for ODF 1.4. We may eventually have to consider proposing an Erratum to fix this in ODF 1.3.

     

    Kind regards,

     

    Francis



  • 2.  RE: What is the correct value of dsig:version on element

    Posted 03-05-2024 05:09
    hello Francis,

    i wasn't even aware that there is a version attribute in the dsig
    schema, but you are right, the value needs to be updated and the text
    must be consistent with the schema - i see it as an editorial issue.

    do you think we could get this fixed in the ISO submission?

    regards,
    michael

    --
    Michael Stahl
    Senior Software-Entwickler LibreOffice
    ?????????
    allotropia software GmbH
    Versmannstr. 4
    20457 Hamburg
    Germany
    ?????????
    michael.stahl@allotropia.de
    https://www.allotropia.de
    ?????????
    Registered office: Hamburg, Germany
    Registration court Hamburg, HRB 165405
    Managing director: Thorsten Behrens
    VAT-ID: DE 335606919
    ?????????




  • 3.  RE: What is the correct value of dsig:version on element

    Posted 03-05-2024 05:45
    Yes, this can be fixed in the ISO version. The ISO (JTC 1) ballot will commence in a few weeks’ time, and I can make sure that there is a comment in the ballot that specifically requests that this error be corrected in ODF 1.3. It is quite normal for comments to request changes in an ISO standard before it is approved and published. We can then recommend that OASIS publish an Erratum to ODF 1.3 to correct the error - as you say, it is purely editorial, because the normative schema is correct. There may be other comments requesting editorial corrections…

    Francis



    Sent from my iPad