[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Proposal for IANA registration of Media Type for DITA ("application/dita+xml")
Whew! Thanks Robin - good preparation for the TC for followup.
/chet
On Sun, Oct 23, 2011 at 11:26 AM, Robin Cover <robin@oasis-open.org> wrote:
> DITA TC members,
>
> Following a communication from Don Day on 2011-07-29,
> I was alerted to the topic of the DITA TC's request for
> IANA registration of an "'application/dita+xml' Media Type",
> per the draft approved in June 2008 [1] and discussed
> briefly by the TC in 2010-10 [2].
>
> As a member of the OAIS TC Administration team, I am
> currently tasked with management of IANA registrations for
> ports, media/mime types, etc. So we have opened a support
> ticket to track the handling of this request from the TC,
> and I have made an initial review of the TC's 2008 draft,
> along with review of current rules and practices within
> IANA/IESG/IETF. We will plan to track the matter here:
> http://tools.oasis-open.org/issues/browse/TCADMIN-613
>
> My analysis suggests that the content of the TC proposal needs
> to be updated to match the Registration Template now being
> used the "Preliminary Community Review" phase. The required
> template [4] differs in some ways from the TC's 2008 draft [1].
>
> Similarly, information in the templated content needs update
> in several fields, including URI for the "Published
> specification:" [5], the "Person & email address to contact
> for further information:", etc.
>
> When the information required by the current template is
> updated and complete, it can be incorporated into the DITA
> specification (any draft) or published as an independent IETF
> Internet Draft. In either case, the proposal can then be
> presented to IESG for after review on the mailing list for
> review: ietf-types@iana.org [3]. Per comment in [5] below,
> I think it will be best to publish an I-D, but that
> decision will be left to the DITA TC members.
>
> I (as a Staff member of record) will assist the TC in
> communicating the proposal + amendments to IETF/IESG, which
> initially involves Preliminary Community Review, per the
> current IETF RFC governing proposals:
>
> "Preliminary Community Review
>
> Notice of a potential media type registration in the
> standards tree MUST be sent to the "ietf-types@iana.org"
> mailing list for review. This mailing list has been
> established for the purpose of reviewing proposed media
> and access types...
>
> The intent of the public posting to this list is to
> solicit comments and feedback on the choice of
> type/subtype name, the unambiguity of the references with
> respect to versions and external profiling information,
> and a review of any interoperability or security
> considerations. The submitter may submit a revised
> registration or abandon the registration completely and
> at any time."
>
> In order to move the proposal forward for the DITA TC,
> someone or some designated group of TC members will need
> to drive the effort, from a technical perspective, as the
> content of the 2008 proposal is evaluated and updated. I
> will handle the matter administratively for the TC as an
> act of registration, but technical issues -- including the
> terms of the proposal, and responses to the IESG/community
> reviewers -- will need to be resolved by the TC.
>
> It would be useful if the TC can designate one of more
> individuals to take responsibility for the proposal at
> the technical level, where authority is given to make
> decisions OR to escalate any questions to the plenary
> TC per discretion.
>
> I have appended a short list of additional resources [6]
> that may be of interest or help to those who now become
> involved in the rehistration process.
>
> - Robin
>
> Robin Cover
> OASIS, Director of Information Services
> Editor, Cover Pages and XML Daily Newslink
> Email: robin@oasis-open.org
> Staff bio: http://www.oasis-open.org/people/staff/robin-cover
> Cover Pages: http://xml.coverpages.org/
> Newsletter: http://xml.coverpages.org/newsletterArchive.html
> Tel: +1 972-296-1783
>
> ======== Resources:
>
> [1] MIME type for DITA - RFC (approved by Technical Committee)
> Tue, 10 Jun 2008 08:41:02 -0700
> http://lists.oasis-open.org/archives/dita/200806/msg00008.html
> http://lists.oasis-open.org/archives/dita/200806/bin00001.bin
> == DITAMIMETypeRFC.txt
>
>
> [2] subsequent discussion on the TC list
> http://lists.oasis-open.org/archives/dita/201010/msg00065.html
> http://lists.oasis-open.org/archives/dita/201010/msg00066.html
> http://lists.oasis-open.org/archives/dita/201010/msg00067.html
> http://lists.oasis-open.org/archives/dita/201010/msg00068.html
>
>
> [3] Official mailing list used for review of registration proposals
>
> ietf-types -- Media (MIME) type review
> Info: https://www.ietf.org/mailman/listinfo/ietf-types
> Archive: http://www.ietf.org/mail-archive/web/ietf-types/
>
>
> [4] "Media Type Specifications and Registration Procedures"
> Request for Comments: 4288
> http://tools.ietf.org/html/rfc4288
> See "Registration Template":
> http://tools.ietf.org/html/rfc4288#section-10
> See: http://tools.ietf.org/html/rfc4288#section-5.2
>
> But we need to watch this revision of RFC 4288, which includes
> a proposed slot "URI fragment/anchor identifier(s):" in
> the "Additional information:" template field
>
> Media Type Specifications and Registration Procedures
> Obsoletes: 4288 (if approved)
> September 5, 2011 (-01) or later
> http://tools.ietf.org/html/draft-freed-media-type-regs
> See "Registration Template"
> http://tools.ietf.org/html/draft-freed-media-type-regs-01#section-5.9
> - See: http://tools.ietf.org/html/draft-freed-media-type-regs-01#section-5
> - Version -01 adds "URI fragment/anchor identifier(s):"
>
>
> [5] Since DITA is now an OASIS Standard, and the (proposed)
> "DITA MIME type" is referenced in DITA Specification v1.2
> ("B.3 DITA MIME type"), I suspect (don't know) the reference
> to "Appendix B.3 DITA MIME type" would qualify as a valid
> candidate for the "Published specification:", if this is
> used in an Internet Draft designed to be approved as an
> IETF Informational RFC. In similar cases, the verbatim text
> from a published spec is (re-)used in an Internet Draft,
> or is excerpted and sent to the review mailing list. In
> the case of DITA v1.2 Appendix B.3 we don't have the
> complete/proper proposal, so I think an independent I-D
> (RFC) will be needed to support the "Preliminary Community
> Review" process.
>
> Its text:
>
> Darwin Information Typing Architecture (DITA) Version 1.2
> OASIS Standard
> 1 December 2010
>
> http://docs.oasis-open.org/dita/v1.2/os/spec/non-normative/DITA-mime-type.html
> "B.3 DITA MIME type
> (Non-normative) It is common for Web-based services to establish
> default actions for content based on the MIME type value sent in
> HTTP headers. For example, the "text/html" MIME type is what
> normally causes browsers to interpret the content of a web page
> as presentation-oriented markup, verus "text/plain" which would
> cause the markup to be displayed literally. A DITA MIME type
> enables applications to recognize content as DITA to enable
> special services such as semantically-informed search indexing
> or on-the-fly rendering in the browser.
>
> The OASIS DITA Technical Committee has requested the registration
> of "application/dita+xml" with the IANA organization as the
> formally recognized DITA MIME type. This process is in progress,
> however the details are public so that implementors can make
> early use of the proposed value.
>
> More information about the proposal is documented in this note
> of transmittal to OASIS for registration of the DITA MIME type:
>
> http://lists.oasis-open.org/archives/dita/200806/msg00008.html
> http://lists.oasis-open.org/archives/dita/200806/bin00001.bin
> == DITAMIMETypeRFC.txt
>
>
> [6] Additional resources
>
> A. Lists of Registered MIME Media Types
> - http://www.iana.org/assignments/media-types/index.html
> - http://www.iana.org/assignments/media-types/application/index.html
> - TRAC: http://trac.tools.ietf.org/group/iesg/trac/report (active?)
>
>
> B. W3C Commentary/Help (Date: 2011/06/21 13:35:30 or later)
>
> This document describes how W3C Working Groups handle
> registrations of Media Types, and it should be useful,
> by analogy.
>
> "Register an Internet Media Type for a W3C Spec"
> http://www.w3.org/2002/06/registering-mediatype
> * New Procedure: Registration template in spec, no RFC
> http://www.w3.org/2002/06/registering-mediatype#Planned
> * Old Procedure: Registration with an RFC
> http://www.w3.org/2002/06/registering-mediatype#Current
> * Status of [W3C] Internet Media type registrations
> http://www.w3.org/2002/06/registering-mediatype#RegStatus
>
>
> C. XML Media Types and Registry
> http://tools.ietf.org/html/rfc3023
>
> Registry Name: IETF XML Registry
> http://www.iana.org/assignments/xml-registry-index.html
> cites:
> http://www.iana.org/assignments/xml-registry/schema.html
> http://www.iana.org/assignments/xml-registry/publicid.html
> http://www.iana.org/assignments/xml-registry/ns.html
> http://www.iana.org/assignments/xml-registry/rdfschema.html
>
>
> D. Endeavors to improve registration processes
>
> The registration process administered by IANA through IESG
> and IETF has come under review, and several efforts are
> underway to help clarify and expedite the prosess for
> various classes of registrations. For example:
>
> 1. happiana -- IANA Registry Happiness, supporting
> discussion about streamlining and improving IETF
> (and other SDO) interfaces to IANA registration
> processes
>
> https://www.ietf.org/mailman/listinfo/happiana
> http://www.ietf.org/mail-archive/web/happiana/
>
>
> 2. Friendly Registries, as a workspace of a
> cross-IETF/W3C group whose aim is to make registries
> more usable for Web-related purposes - especially
> by non-"insiders"
>
> http://www.w3.org/wiki/FriendlyRegistries
> http://www.w3.org/wiki/FriendlyRegistryProcess
>
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-378-3472
Mobile: +1 201-341-1393
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]