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-3342

ODF 1.2 Part 1 "IRI" abuse

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ODF 1.2 CD 05
    • Fix Version/s: ODF 1.2 CD 06
    • Component/s: Public Review
    • Labels:
      None
    • Proposal:
      Hide

      Replace all occurrences of "URL" and "URI" with "IRI", except where "url" or "uri" appears as attribute value or as part of an attribute or element name.

      Support the use of IRI reference (the proper term in almost every usage in ODF) by a normative reference to [RFC3987] and introduce an anyIRI datatype to be perfectly clear how IRIs are to be allowed in the anyURI datatype.

      Limit considerations of iRI mappling to URLs for purpose of resolution to the special case in section 3 involving "Usage of IRIs in Packages." This is the only place where actual mapping to single-byte encodings matter.

      Show
      Replace all occurrences of "URL" and "URI" with "IRI", except where "url" or "uri" appears as attribute value or as part of an attribute or element name. Support the use of IRI reference (the proper term in almost every usage in ODF) by a normative reference to [RFC3987] and introduce an anyIRI datatype to be perfectly clear how IRIs are to be allowed in the anyURI datatype. Limit considerations of iRI mappling to URLs for purpose of resolution to the special case in section 3 involving "Usage of IRIs in Packages." This is the only place where actual mapping to single-byte encodings matter.

      Description

      There are over 20 places in ODF 1.2 CD05 Part 1 where the term "IRI" is used without reference or explanation. These are often in the same statement where URI/URL are used and it is not clear whether these are being assumed to be interchangeable or different.

      These mentions of IRI are too casual. We should perhaps establish that we assume all provisions for URI references in Part 1 are subject to IRI encoding and choose to use IRI consistently. We might need to be careful that we don't overstep existing provision on URIs used as part of attributes defined by other specifications, such as xhtml:href and xlink:href, however. We may also need to say more about URI references when they use XML Schema Datatype anyURI.

      Whatever we do, it is a defect to continue to use IRI casually and with neither definition nor reference to an authoritative source.

      This is related to the similar situation in ODF 1.2 CD05 Part 3, addressed by issue OFFICE-2685 and any resolution in part 1 should be consistent.

      There may also be need for IRI clarification, and clarification around the permissable use of relative URIs in OpenFormula when an OpenFormula expression employs a URI in one of its forms for a reference.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: