Details

    • Proposal:
      Hide

      Proposed text: The manifest:media-type attribute specifies the MIME media type of a file or directory. See [RFC6838].

      Show
      Proposed text: The manifest:media-type attribute specifies the MIME media type of a file or directory. See [RFC6838] .
    • Resolution:
      Hide

      We agree to this PAS comment.
      We plan to adapt ODF as suggested in its next version.

      Show
      We agree to this PAS comment. We plan to adapt ODF as suggested in its next version.

      Description

      Comment logged by national body during the ODF 1.2 PAS process, to be address at Ballot Resolution Meeting.

      Nature of defect :Technical

      Original text of NB comment: The latest RFC for ""Media Type Specifications and Registration Procedures"" is RFC6838. Should see RFC6838.

        Attachments

          Activity

          Hide
          patrick Patrick Durusau added a comment -

          ODF 1.2 cites RFC4288 on MIME types.

          The comment suggests updating to cite RFC6838.

          The one change that looks problematic about updating (to me) is:

          *****
          The ABNF for media type names has been further restricted to require that names begin with an alphanumeric character.
          *****

          Making naming more restrictive than in RFC4288 looks like it would block updating to RFC6838.

          You may find other problems in Appendix B of RFC4288 which specifies the following differences from RFC4288:

          *****
          Suffixes to indicate the use of a particular structured syntax are now fully specified and a suffix registration process has been defined.

          Registration of widely deployed unregistered unfaceted type names in the vendor or personal trees is now allowed, subject to approval by the media types reviewer and the IESG.

          The standards-tree registration process has been revised to include Expert Review and generalized to address cases like media types in non-IETF stream documents.

          A field for fragment identifiers has been added to the registration template and brief directions for specifying fragment identifiers have been added.

          The specification requirements for personal-tree registrations have been changed to be the same as those for the vendor tree. The text has been changed to encourage (but not require) specification availability.

          The process for defining additional trees has been clarified to state that an IETF Standards Action is required.

          Widely deployed types with "x-" names can now be registered as an exception in the vendor tree.

          The requirements on changes to registrations have been loosened so minor changes are easier to make.

          The registration process has been completely restructured so that with the exception of IETF-generated types in the standards tree, all requests are processed by IANA and not the IESG.

          A provisional registration process has been added for early assignment of types in the standards tree.

          Many editorial changes have been made throughout the document to make the requirements and processes it describes clearer and easier to follow.

          The ability to specify a list of deprecated aliases for a media type has been added.

          Types with names beginning with "x-" are no longer considered to be members of the unregistered "x." tree. As with any unfaceted type, special procedures have been added to allow registration of such types in an appropriate tree.

          Changes to a type registered by a third party may now be made by the designated change controller even if that isn't the vendor or organization that created the type. However, the vendor or organization may elect to assert ownership and change controller over the type at any time.

          Limited-use media types are now asked to note whether or not the supplied list of applications employing the media type is exhaustive.

          The ABNF for media type names has been further restricted to require that names begin with an alphanumeric character.

          Mailing list review is no longer required prior to registration of media types. Additionally, the address associated with the media type review mailing list has been changed to media-types@iana.org.

          The rules for text/* media types have been updated to reflect the changes specified in [RFC6657].
          *****

          Show
          patrick Patrick Durusau added a comment - ODF 1.2 cites RFC4288 on MIME types. The comment suggests updating to cite RFC6838. The one change that looks problematic about updating (to me) is: ***** The ABNF for media type names has been further restricted to require that names begin with an alphanumeric character. ***** Making naming more restrictive than in RFC4288 looks like it would block updating to RFC6838. You may find other problems in Appendix B of RFC4288 which specifies the following differences from RFC4288: ***** Suffixes to indicate the use of a particular structured syntax are now fully specified and a suffix registration process has been defined. Registration of widely deployed unregistered unfaceted type names in the vendor or personal trees is now allowed, subject to approval by the media types reviewer and the IESG. The standards-tree registration process has been revised to include Expert Review and generalized to address cases like media types in non-IETF stream documents. A field for fragment identifiers has been added to the registration template and brief directions for specifying fragment identifiers have been added. The specification requirements for personal-tree registrations have been changed to be the same as those for the vendor tree. The text has been changed to encourage (but not require) specification availability. The process for defining additional trees has been clarified to state that an IETF Standards Action is required. Widely deployed types with "x-" names can now be registered as an exception in the vendor tree. The requirements on changes to registrations have been loosened so minor changes are easier to make. The registration process has been completely restructured so that with the exception of IETF-generated types in the standards tree, all requests are processed by IANA and not the IESG. A provisional registration process has been added for early assignment of types in the standards tree. Many editorial changes have been made throughout the document to make the requirements and processes it describes clearer and easier to follow. The ability to specify a list of deprecated aliases for a media type has been added. Types with names beginning with "x-" are no longer considered to be members of the unregistered "x." tree. As with any unfaceted type, special procedures have been added to allow registration of such types in an appropriate tree. Changes to a type registered by a third party may now be made by the designated change controller even if that isn't the vendor or organization that created the type. However, the vendor or organization may elect to assert ownership and change controller over the type at any time. Limited-use media types are now asked to note whether or not the supplied list of applications employing the media type is exhaustive. The ABNF for media type names has been further restricted to require that names begin with an alphanumeric character. Mailing list review is no longer required prior to registration of media types. Additionally, the address associated with the media type review mailing list has been changed to media-types@iana.org. The rules for text/* media types have been updated to reflect the changes specified in [RFC6657] . *****
          Hide
          owittmann Oliver-Rainer Wittmann (Inactive) added a comment -

          discussion from TC call, 2014-09-29:

          • expert needed to compare the versions in order to decide, if an update is possible and makes sense [in the meanwhile Patrick already had a closer look - see previous comment]
          Show
          owittmann Oliver-Rainer Wittmann (Inactive) added a comment - discussion from TC call, 2014-09-29: expert needed to compare the versions in order to decide, if an update is possible and makes sense [in the meanwhile Patrick already had a closer look - see previous comment]
          Hide
          patrick Patrick Durusau added a comment -

          Raised at meeting 10-27-2014 - Pending - Patrick, investigate the impact of the new ABNF naming

          Show
          patrick Patrick Durusau added a comment - Raised at meeting 10-27-2014 - Pending - Patrick, investigate the impact of the new ABNF naming
          Hide
          owittmann Oliver-Rainer Wittmann (Inactive) added a comment -

          on TC call 2014-11-10 we agreed on the given resolution as our disposition to the received PAS comment; Patrick is taking over

          Show
          owittmann Oliver-Rainer Wittmann (Inactive) added a comment - on TC call 2014-11-10 we agreed on the given resolution as our disposition to the received PAS comment; Patrick is taking over
          Hide
          patrick Patrick Durusau added a comment -

          Applied in OpenDocument-v1.3-wd05-part3-documents.odt

          Show
          patrick Patrick Durusau added a comment - Applied in OpenDocument-v1.3-wd05-part3-documents.odt
          Hide
          patrick Patrick Durusau added a comment -

          Corrected in part 3, but, also needs correction in present part 2 (packages)

          Show
          patrick Patrick Durusau added a comment - Corrected in part 3, but, also needs correction in present part 2 (packages)
          Hide
          regina.henschel Regina Henschel added a comment -

          I see the new reference [RFC6838] in "1.3 Normative References" in OpenDocument-v1.3-wd06-part2-packages. Should not the references in the text be changed? I find the old value [RFC4288] in
          3.3 MIME Media Type
          4.8.10 manifest:media-type
          6.7 pkg:mimeType

          Show
          regina.henschel Regina Henschel added a comment - I see the new reference [RFC6838] in "1.3 Normative References" in OpenDocument-v1.3-wd06-part2-packages. Should not the references in the text be changed? I find the old value [RFC4288] in 3.3 MIME Media Type 4.8.10 manifest:media-type 6.7 pkg:mimeType
          Hide
          patrick Patrick Durusau added a comment -

          Applied OpenDocument-v1.3-wd09-part2-packages.odt

          Show
          patrick Patrick Durusau added a comment - Applied OpenDocument-v1.3-wd09-part2-packages.odt

            People

            • Assignee:
              patrick Patrick Durusau
              Reporter:
              chris.rae Chris Rae (Inactive)
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: