Next in thread →
Next in month →
RE: [dita] OASIS Call for Participation: DITA Adoption Technical Committee
Jeff and Mary, I announced at Tuesday meeting that the registration was seven days in advance. Jeff needs to send a correction to his note, which lists 14 days in advance. JoAnn JoAnn T. Hackos, PhD President Comtech Services, Inc. 710 Kipling Street, Suite 400 Denver, CO 80215 303-232-7586 joannhackos Skype www.comtech-serv.com From: Mary McRae [mailto:] On Behalf Of Mary McRae Sent: Wednesday, July 02, 2008 7:52 AM To: 'Ogden, Jeff'; Subject: RE: [dita] OASIS Call for Participation: DITA Adoption Technical Committee Thanks, Jeff, for inadvertently catching a mistake in my message ;-) Since the first meeting of the DITA Adoption TC will be a teleconference (rather than a face-to-face), you must join the TC at least *seven* days prior to the first meeting. My apologies – I’ll send a correction to the list. Regards, Mary From: Ogden, Jeff [mailto:] Sent: Wednesday, July 02, 2008 8:53 AM To: Subject: [dita] OASIS Call for Participation: DITA Adoption Technical Committee OASIS is moving forward to create the new DITA Adoption Technical Committee. Here are some dates and deadlines to note: To be able to vote at the first meeting you must notify the TC of your intent to participate at least 15 days prior to the first meeting (no later than July 12th) by using the "Join this TC" button on the TC's public page at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita-adoption ; and The first meeting/conference call will be held Monday, 28 July 2008 at 11:00 am ET. One can of course join the new TC after these dates. -Jeff > -----Original Message----- > From: Mary McRae [mailto:] On Behalf Of Mary McRae > Sent: Thursday, June 26, 2008 10:05 AM > To: ; > Cc: > Subject: [members] OASIS Call for Participation: DITA Adoption Technical Committee > > To: OASIS members & interested parties > > A new OASIS technical committee is being formed. The OASIS DITA Adoption > Technical Committee has been proposed by the members of OASIS listed below. > > The proposal, below, meets the requirements of the OASIS TC Process [a]. The > TC name, statement of purpose, scope, list of deliverables, audience, and > language specified in the proposal will constitute the TC's official charter. > Submissions of technology for consideration by the TC, and the beginning of technical > discussions, may occur no sooner than the TC's first meeting. > > This TC will operate under our IPR Policy [b]. The eligibility requirements > for becoming a participant in the TC at the first meeting (see details below) > are that: > > (a) you must be an employee of an OASIS member organization or an individual > member of OASIS; > (b) the OASIS member must sign the OASIS membership agreement [c]; > (c) you must notify the TC chair of your intent to participate at least 15 > days prior to the first meeting, which members may do by using the > "Join this TC" button on the TC's public page at [d]; and > (d) you must attend the first meeting of the TC, at the time and date fixed below. > > Of course, participants also may join the TC at a later time. OASIS and > the TC welcomes all interested parties. > > Non-OASIS members who wish to participate may contact us about joining OASIS [c]. > In addition, the public may access the information resources > maintained for each TC: a mail list archive, document repository and public comments > facility, which will be linked from the TC's public home page at [d]. > > Please feel free to forward this announcement to any other appropriate lists. > OASIS is an open standards organization; we encourage your feedback. > > Regards, > > Mary > > --------------------------------------------------- > Mary P McRae > Manager of TC Administration, OASIS > email: > web: www.oasis-open.org > > [a] http://www.oasis-open.org/committees/process.php > [b] http://www.oasis-open.org/who/intellectualproperty.php > [c] See http://www.oasis-open.org/join/ > [d] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita-adoption] > > CALL FOR PARTICIPATION > OASIS DITA Adoption TC > > Name: > > OASIS DITA Adoption Technical Committee > > Statement of Purpose: > > 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 DITA > Adoption Technical Committee expects the demand for, and availability of, DITA > conforming products and services to increase, resulting in a greater choice of > tools and platforms and an expanded 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. > > 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 is encouraged to bring issues to the DITA TC concerning user needs > in improving the specification. The DITA TC is encouraged to 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. > > By advancing the adoption of DITA through OASIS, the Technical Committee 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 > . Actively solicit participation from members outside North America > and help to facilitate the provision of information promoting DITA > adoption globally > > Scope of Work: > > 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 > . Other activities that are considered appropriate to forwarding the > goals of the Technical Committee. > > The OASIS DITA Adoption Technical Committee will refer suggestions and > requests for changes to and clarification of the DITA Specification to the existing > DITA Technical Committee. > > List of Deliverables: > . 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. > . Ongoing maintenance of the DITA.xml.org Focus Area > . Additional materials supportive of the above scope. > > The OASIS DITA Adoption Technical Committee is an on-going activity with > no specific end date for its activities established in advance. > > IPR Mode: > > Royalty-Free on limited terms > > Anticipated Audience/Users: > > 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. > > Language in which the TC will 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. 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 > specifications for 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 will be > encouraged to 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 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 is expected > to occur through small working groups, such as a 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 > Gershon Joseph, Associate > Troy Klukewich, Oracle > Kay Whatley, Individual > Kristen Eberlein, Individual > Tony Self, Associate > Bob Doyle, Associate > Bryan Schnabel, Individual > Michael Priestley, IBM > Debra Bissantz, LSI Logic > Frank Miller, Comtech > Rene Gedaly, Individual > Chona Shumate, Individual > > (2)(e) The name of the Convener who must be an Eligible Person. > > JoAnn Hackos > > (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. > > None. > > --------------------------------------------------------------------- > > This email list is used solely by OASIS for official consortium communications. > > Opt-out requests may be sent to , however, > all members are strongly encouraged to maintain a subscription to this list.
Next in thread →
Next in month →