Uploaded image for project: 'OASIS Open Document Format for Office Applications (OpenDocument) TC'
  1. OASIS Open Document Format for Office Applications (OpenDocument) TC
  2. OFFICE-2079

Section 18.51 db:enable-sql92-check and others

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Applied
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ODF 1.2
    • Fix Version/s: ODF 1.2
    • Component/s: Database, Table
    • Labels:
      None
    • Environment:

      This bug applies to ODF 1.2 Part 1 cd03 and changes under discussion

    • Proposal:
      Hide

      Replace:

      false: names of tables, views, columns and queries may contain characters defined by the [SQL] feature F392.
      true: names of tables, views, columns and queries should not contain characters defined by the [SQL] feature F392.

      with:

      false: editing applications should permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries.
      true: editing applications should not permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries.

      Show
      Replace: false: names of tables, views, columns and queries may contain characters defined by the [SQL] feature F392. true: names of tables, views, columns and queries should not contain characters defined by the [SQL] feature F392. with: false: editing applications should permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries. true: editing applications should not permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries.
    • Resolution:
      Hide

      Replaced:

      false: names of tables, views, columns and queries may contain characters defined by the [SQL] feature F392.
      true: names of tables, views, columns and queries should not contain characters defined by the [SQL] feature F392.

      with:

      false: editing applications should permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries.
      true: editing applications should not permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries.

      Show
      Replaced: false: names of tables, views, columns and queries may contain characters defined by the [SQL] feature F392. true: names of tables, views, columns and queries should not contain characters defined by the [SQL] feature F392. with: false: editing applications should permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries. true: editing applications should not permit characters defined by the [SQL] feature F392 for new or changed names of tables, views, columns, and queries.

      Description

      In Section 18.51 on db:enable-sql2-check and other sections that deal with conditions/constraints on communication with a database service, there is use of normative language such as shall, shall not, may, need not, etc.

      It is not clear what the targets of these normative conditions are. What and who does the normative language apply to?

      There has been some back-and-forth on this matter on the office-comment list with regard to the correct normative references and how those references are being profiled with statements such as that above. See the threads around
      <http://lists.oasis-open.org/archives/office-comment/200909/msg00013.html>.

        Attachments

          Activity

            People

            • Assignee:
              patrick Patrick Durusau
              Reporter:
              orcmid Dennis Hamilton (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: