Who are the organizations and people who currently participate?
Who should participate?
Roles of individuals
- Consultants
- Information architects
- Managers
- Content engineers
- Information developers
Types of organization
- Companies that produce XML and CCMS products
- Universities
- Software companies, hardware companies, medical devices and
information
- Any organization that creates a significant amount of
content
- Corporations
- Governments
- Non-profit organizations
Questions:
Should this be the audience for output of the TC? People who
participate? How does this relate to scope?
Deliverables
What work does the TC produce? This can be specifications,
committee notes, schemas, models, glossaries, requirements
documents, according to the OASIS template.
- Specification
- Committee notes (best practices, migration information,
specification previews, white papers)
- Webinars and conference presentations
- Migration information
- Best practices
- White papers
- Tutorial
- Reference content (examples of how to do stuff)
- GitHub repositories (style sheets, RNG to DTD converter,
specializations that have been removed from the spec)
- Specializations
Questions:
- Should this list be exhaustive or more general? Answer:
Brainstorm list should be exhaustive; what goes into the
charter should be general.)
- Who is the audience for the document? Answer: People looking
for information about the DITA TC.
- How do we deal with the overlap with the Adoption TC? Is the
Adoption TC needed? Is this the time to have one not two TC?
Scope
What is in (and out) of scope? OASIS reminds us to focus on the
"what" not the "how".
Out-of-scope
- Documents that rate DITA compliance
- DITA-OT
- Learning materials? How-to materials?
- Implementation materials
In-scope
--
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)