OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-adoption message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita-adoption] Review of the current DITA Adoption TC charter


Thanks, Chris
Let's take this up at Mondays meeting.
JoAnn

Sent from my iPad
JoAnn Hackos
Comtech Services Inc


On Jul 25, 2012, at 12:14 PM, "Goolsby, Chris" <cgoolsby@ptc.com> wrote:

Hi all.

 

I took an action item in the last meeting to review the TC charter and post my comments to the list. Here’s the charter with my comments interspersed:

 

Name:

 

OASIS DITA Adoption Technical Committee

 

[Comments] – This is obviously fine

 

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.

 

[Comments] – This seems fine.

 

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.

 

[Comments] – Why is the EU particularly called out? Seems like this should either be made more generic by removing the EU or expanded to include the Asia subcommittee.

 

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.

 

[Comments] – This seems fine. Should we call out the liaison to the DITA TC somewhere in the Adoption TC web pages, perhaps where the chairs are listed?

 

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

 

[Comments] – This seems ok, though the last bullet just repeats what was said in the second paragraph above. One or the other could be removed. I also wonder why the first three bullet points seem to focus more on OASIS than DITA adoption. Perhaps those points could be combined into fewer bullets?

 

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.

 

[Comments] – This is a really big scope. It seems like this could be reduced to focus on the areas that we really think we can accomplish. For example, do the two bullets on “Assist in coordinating….” really need to be there?

 

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.

 

[Comments] – This seems fine, but why not make it a bullet point and add to the list above?

 

List of Deliverables:

 

•First best practice issued within 6 months of formation.

•First webinar produced jointly with the XLIFF 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.

 

[Comments] – It seems like this list needs to be revised. The first two bullets could go, since they refer to old deliverables. Perhaps we should make this a more generic list with typical TC deliverables?

 

The OASIS DITA Adoption Technical Committee is an on-going activity with no specific end date for its activities established in advance.

 

[Comments] – This statement seems out of place in the deliverables section. It’s not a deliverable. Maybe move this to the purpose or scope section?

 

IPR Mode:

 

Royalty-Free on limited terms.

 

[Comments] – I assume this is fine, but I’m not that familiar with the IPR distinctions. According to OASIS, we’d have to close and submit a new charter to change this anyway.

 

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.

 

[Comments] – This seems fine.

 

Language in which the TC will conduct business:

 

English

 

[Comments] – This seems fine.

 

 

 

<image001.png>


Chris Goolsby
Principal Technical Writer

T 734.352.2841
E cgoolsby@ptc.com

PTC.com

 

 

PNG image



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]