[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposed Charter for OASIS DITA Adoption TC
To OASIS Members: A draft TC charter has been submitted to establish the DITA Adoption Technical Committee. In accordance with the OASIS TC Process Policy section 2.2: (http://www.oasis-open.org/committees/process-2008-02-05.php#formation) the proposed charter is hereby submitted for comment. The comment period shall remain open until 11:45pm ET on 17 June 2008. OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: mailto:email@example.com. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail. A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar. We encourage member comment and ask that you note the name of the proposed TC (DITA-Adoption) in the subject line of your email message. Regards, Mary --------------------------------------------------- Mary P McRae Manager of TC Administration, OASIS email: firstname.lastname@example.org web: www.oasis-open.org phone: 603.232.9090 =========== PROPOSED CHARTER FOR REVIEW AND COMMENT OASIS DITA Adoption Technical Committee (1)(a) The name of the TC, such name not to have been previously used for an OASIS TC and not to include any trademarks or service marks not owned by OASIS. OASIS DITA Adoption Technical Committee (1)(b) A statement of purpose, including a definition of the problem to be solved. The OASIS DITA Adoption Technical Committee members will collaborate to provide expertise and resources to educate the marketplace on the value of the DITA OASIS standard. By raising awareness of the benefits offered by DITA, the Technical Committee increases the demand for, and availability of, DITA conforming products and services, resulting in a greater choice of tools and platforms and expanding the DITA community of users, suppliers, and consultants. Since DITA adoption is stronger in the US than in the rest of the world, especially the European Union, the Technical Committee will actively solicit participation from non-US members and help to facilitate providing information promoting DITA adoption globally. By advancing the adoption of DITA through OASIS, the Technical Committee members will: . Collaborate within the security of the OASIS open process . Maximize message credibility by working on behalf of a vendor-neutral standards consortium . Build on existing market awareness of OASIS as the source of DITA . Leverage the combined resources of all participants . Reinforce DITA as the result of an open, transparent process guided by multiple vendors, communities, and individuals . Openly share content and coordinate program execution with other entities that share a common or similar statement of purpose on a worldwide scope (1)(c) The scope of the work of the TC, which must be germane to the mission of OASIS, and which includes a definition of what is and what is not the work of the TC, and how it can be determined when the work of the TC has been completed. OASIS DITA Adoption Technical Committee activities may extend to any of the following activities: . Oversee the DITA XML.org Focus Area . Review and ensure accuracy of DITA references in commonly used resources such as Wikipedia . Host educational, vendor-neutral webinars . Organize vendor-neutral workshops and tracks at OASIS events and other conferences . Produce OASIS-branded primers, white papers, position papers, slide presentations, datasheets, and other collateral . Develop best practice guidelines . Establish liaisons with other organizations who may assist in building awareness of DITA, and promoting DITA in a variety of user communities . Assist in coordinating promotional efforts of members, leveraging activities wherever beneficial . Assist in coordinating press and analyst relations such as briefings, releases, and announcements . Encourage and coordinate volunteer efforts to translate the DITA specification and other committee documents into other languages . Interface with other TCs to define how DITA can be best integrated with other standards to address specific scenarios . Stage interoperability and/or proof-of-concept demonstrations at industry conferences . Other projects aimed at increasing adoption as identified by Committee members (1)(d) A list of deliverables, with projected completion dates. . First best practice issued within 6 months of formation. . First webinar produced jointly with the SVG Technical Committee and the DITA Translation Subcommittee and sponsored by OASIS. (1)(e) Specification of the IPR Mode under which the TC will operate. Royalty-Free on limited terms (1)(f) The anticipated audience or users of the work. Anyone involved in the implementation of the OASIS DITA standard in their own organizations, including information-development managers, content creators and distributors, consultants supporting implementations, and vendors providing tools to support content development and distribution. (1)(g) The language in which the TC shall conduct business. English (2) Non-normative information regarding the startup of the TC, which includes: (2)(a) Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations, why there is a need for another effort in this area and how this proposed TC will be different, and what level of liaison will be pursued with these other organizations. The DITA Adoption Technical Committee is closely allied with the DITA Technical Committee. The DITA TC is responsible for the development, maintenance, and enhancement of the DITA specification and the language reference. As such, the DITA TC concentrates on clearly defining and developing the technical content of the specification. It also supports the work of several subcommittees that are creating industry-specific specializations of the DITA specification. The DITA Adoption TC concentrates on the promotion of the DITA standard to the global user community, helping to encourage DITA adoption in new industries, new areas of content creation, and new organizations. To this end, the DITA Adoption TC's focus is on building public awareness of the standard, educating potential users in the standard, and ensuring that miscommunications that may exist are quickly corrected. The DITA Adoption TC intends to appoint an individual who is an active, voting member of both TCs to serve as a liaison to the DITA TC, to actively communicate the work of the Adoption TC, and to request the assistance of the DITA TC on technical issues concerning the specification. Through the liaison, the DITA Adoption TC may bring issues to the DITA TC concerning user needs in improving the specification. The DITA TC may bring issues to the DITA Adoption TC concerning the use cases or user scenarios around proposed changes and enhancements to the specification, as well as suggestions for other adoption-related work. (2)(b) The date, time, and location of the first meeting, whether it will be held in person or by telephone, and who will sponsor this first meeting. 28 July 2008 11:00 am ET The TC will use a free conference service provided by ComTech Services for its teleconferences. (2)(c) The projected on-going meeting schedule for the year following the formation of the TC, or until the projected date of the final deliverable, whichever comes first, and who will be expected to sponsor these meetings. The DITA Adoption TC plans to hold regular monthly meetings unless increased work requires more frequent meetings. Much of the Adoption TC work occurs through small working groups, such as the working group responsible for updating and monitoring the dita.xml.org website as an ongoing activity. (2)(d) The names, electronic mail addresses, and membership affiliations of at least Minimum Membership who support this proposal and are committed to the Charter and projected meeting schedule. JoAnn Hackos, Comtech Joann.email@example.com Gershon Joseph, Associate Gershon.firstname.lastname@example.org Troy Klukewich, Oracle Troy.Klukewich@oracle.com Kay Whatley, Individual email@example.com Kristen Eberlein, Individual firstname.lastname@example.org Tony Self, Associate email@example.com Bob Doyle, Associate firstname.lastname@example.org Bryan Schnabel, Individual email@example.com Michael Priestley, IBM firstname.lastname@example.org Debra Bissantz, LSI Logic email@example.com Frank Miller, Comtech Frank.firstname.lastname@example.org Julio Vasquez, SDI email@example.com Rene Gedaly, Individual firstname.lastname@example.org David J B Hollis, A&O Consultancy dhollis@AandOConsultancy.ltd.uk (2)(e) The name of the Convener who must be an Eligible Person. JoAnn Hackos Joann.email@example.com (2)(f) The name of the Member Section with which the TC intends to affiliate, if any. None (2)(g) Optionally, a list of contributions of existing technical work that the proposers anticipate will be made to this TC. None (2)(h) Optionally, a draft Frequently Asked Questions (FAQ) document regarding the planned scope of the TC, for posting on the TC's website. To be provided at a later date. (2)(i) Optionally, a proposed working title and acronym for the specification(s) to be developed by the TC. To be provided at a later date.