Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Committee Draft
    • Fix Version/s: Working Draft
    • Component/s: ODF11-InteropProfile
    • Labels:
      None
    • Proposal:
      Hide

      a) adding the word 'accumulated' would clarify the intention

      b) and it indeed makes sense that a Producer only uses days, hours, minutes and seconds because months and years is ambiguous
      (we can safely ignore leap seconds and assume a day is always 86400 seconds, and I don't think someone is actually interested in seconds)

      c0) Producer SHALL only use days, hours, minutes and seconds

      c1) Consumers SHALL be able to parse P0Y0M... (Y = 0, M = 0 is a bit useless, but valid, and an implementation has to be able to parse this notation anyway if it also supports meta:user-defined with a duration...)

      c2) Consumers MAY treat Y = 365 and M = 30 days

      Show
      a) adding the word 'accumulated' would clarify the intention b) and it indeed makes sense that a Producer only uses days, hours, minutes and seconds because months and years is ambiguous (we can safely ignore leap seconds and assume a day is always 86400 seconds, and I don't think someone is actually interested in seconds) c0) Producer SHALL only use days, hours, minutes and seconds c1) Consumers SHALL be able to parse P0Y0M... (Y = 0, M = 0 is a bit useless, but valid, and an implementation has to be able to parse this notation anyway if it also supports meta:user-defined with a duration...) c2) Consumers MAY treat Y = 365 and M = 30 days

      Description

      Section 3.3.2.17 of http://www.oasis-open.org/committees/download.php/33633/OpenDocument-v1.2-part1-cd03.odt

      defines <meta:editing-duration> Metadata as an element with a value that conforms to section 3.2.6 of the xmlschema-2 Spezifikation.

      http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#duration

      I interpret the meaning of that value as the total accumulated time during which the document was being edited. Since there can be any
      number of gaps since the document was created where the document was not edited and which would thus not contribute to this total editing time a
      value here that would contain subelements specified as number of years or months does IMHO not make sense although it would be allowed by
      xmlschema-2 section 3.2.6. Number of years and months subelements in such a value being present would only make sense if we would have a
      value for some kind of elapsed time without non counted gaps in between which is not the case here.

        Attachments

          Activity

            People

            • Assignee:
              bart.hanssens Bart Hanssens (Inactive)
              Reporter:
              bernd.eilers Bernd Eilers (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: