OASIS Darwin Information Typing Architecture (DITA) TC

Dawn, Frank, Gershon, and Nancy: What do you think of this? Do you want to meet and talk this over, or do we want to get feedback from the TC on tomorrow's call? Basically, I did the following: Added a Scope of Work section Moved some content from Statement of Purpose into Scope of Work Changed places where we previously referred to the DITA standard to DITA standards (keeping the door open for LwDITA) Chet, do you think the Scope of Work is sufficiently broad that it won't prevent us from doing something without changing the charter? As mich work as this has been, I don't think we want to revisit the charter frequently. TC Name: Darwin Information Typing Architecture (DITA) Technical Committee (TC) Statement of Purpose: DITA is an XML-based standard for modular and extensible topic-based information. It enables content creators to separate content into semantically rich, reusable components that reflect the core purpose of the content they contain. DITA provides a model for defining and processing new components as specializations of ones, thus enabling interoperability of DITA-based content. Scope of work The scope of the DITA encompasses the following: Defining and maintaining DITA standards Promoting the use of DITA standards The DITA TC does not produce reference implementations or rate compliance of DITA products. Deliverables: The DITA TC produces the following deliverables and more: DITA specifications and associated grammar files Committee notes that contain non-normative content (tutorials, best practices, migration information, etc.) Webinar and conference presentations In addition, the DITA TC sponsors several Open OASIS GitHub repositories through which non-OASIS members can participate in DITA-related work. Audience: The following are the primary audiences for the work of the DITA TC: Developers of DITA-supporting applications Content engineers and XML specialists Information architects and information developers IPR Mode: RF on Limited Terms Mode of the OASIS IPR Policy Language: English -- 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)

I think it is fine, but I really felt we needed the word existing where I’ve noted.   I’m off on vacation until the 25 th , so won’t be around to discuss with the TC, but I’m sure you don’t need me for those discussions.   Dawn   From: Kristen James Eberlein <kris@eberleinconsulting.com> Date: Monday, October 11, 2021 at 11:56 AM To: Dawn Stevens <dawn.stevens@Comtech-serv.com>, Wegmann, Frank <Frank.Wegmann@softwareag.com>, Nancy Harrison <nharrison@infobridge-solutions.com>, Gershon Joseph <gerjosep@cisco.com> Cc: DITA TC <dita@lists.oasis-open.org> Subject: Updates to strawman charter, after feedback from Chet Ensign Dawn, Frank, Gershon, and Nancy: What do you think of this? Do you want to meet and talk this over, or do we want to get feedback from the TC on tomorrow's call? Basically, I did the following: Added a "Scope of Work" section Moved some content from "Statement of Purpose" into "Scope of Work" Changed places where we previously referred to the DITA standard to "DITA standards" (keeping the door open for LwDITA) Chet, do you think the "Scope of Work" is sufficiently broad that it won't prevent us from doing something without changing the charter? As mich work as this has been, I don't think we want to revisit the charter frequently. TC Name: Darwin Information Typing Architecture (DITA) Technical Committee (TC) Statement of Purpose: DITA is an XML-based standard for modular and extensible topic-based information. It enables content creators to separate content into semantically rich, reusable components that reflect the core purpose of the content they contain. DITA provides a model for defining and processing new components as specializations of existing ones, thus enabling interoperability of DITA-based content. Scope of work The scope of the DITA encompasses the following: Defining and maintaining DITA standards Promoting the use of DITA standards The DITA TC does not produce reference implementations or rate compliance of DITA products. Deliverables: The DITA TC produces the following deliverables and more:     DITA specifications and associated grammar files     Committee notes that contain non-normative content (tutorials, best practices, migration information, etc.)     Webinar and conference presentations In addition, the DITA TC sponsors several Open OASIS GitHub repositories through which non-OASIS members can participate in DITA-related work. Audience: The following are the primary audiences for the work of the DITA TC:     Developers of DITA-supporting applications     Content engineers and XML specialists     Information architects and information developers IPR Mode: RF on Limited Terms Mode of the OASIS IPR Policy Language: English -- 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)

Thanks for catching that! I obviously copied and pasted from the original version with the missing word. Have a super vacation. Kris Sent from my iPad On Oct 11, 2021, at 7:29 PM, Dawn Stevens <dawn.stevens@comtech-serv.com> wrote: ï I think it is fine, but I really felt we needed the word existing where I ve noted.   I m off on vacation until the 25 th , so won t be around to discuss with the TC, but I m sure you don t need me for those discussions.   Dawn   From: Kristen James Eberlein <kris@eberleinconsulting.com> Date: Monday, October 11, 2021 at 11:56 AM To: Dawn Stevens <dawn.stevens@Comtech-serv.com>, Wegmann, Frank <Frank.Wegmann@softwareag.com>, Nancy Harrison <nharrison@infobridge-solutions.com>, Gershon Joseph <gerjosep@cisco.com> Cc: DITA TC <dita@lists.oasis-open.org> Subject: Updates to strawman charter, after feedback from Chet Ensign Dawn, Frank, Gershon, and Nancy: What do you think of this? Do you want to meet and talk this over, or do we want to get feedback from the TC on tomorrow's call? Basically, I did the following: Added a Scope of Work section Moved some content from Statement of Purpose into Scope of Work Changed places where we previously referred to the DITA standard to DITA standards (keeping the door open for LwDITA) Chet, do you think the Scope of Work is sufficiently broad that it won't prevent us from doing something without changing the charter? As mich work as this has been, I don't think we want to revisit the charter frequently. TC Name: Darwin Information Typing Architecture (DITA) Technical Committee (TC) Statement of Purpose: DITA is an XML-based standard for modular and extensible topic-based information. It enables content creators to separate content into semantically rich, reusable components that reflect the core purpose of the content they contain. DITA provides a model for defining and processing new components as specializations of existing ones, thus enabling interoperability of DITA-based content. Scope of work The scope of the DITA encompasses the following: Defining and maintaining DITA standards Promoting the use of DITA standards The DITA TC does not produce reference implementations or rate compliance of DITA products. Deliverables: The DITA TC produces the following deliverables and more:     DITA specifications and associated grammar files     Committee notes that contain non-normative content (tutorials, best practices, migration information, etc.)     Webinar and conference presentations In addition, the DITA TC sponsors several Open OASIS GitHub repositories through which non-OASIS members can participate in DITA-related work. Audience: The following are the primary audiences for the work of the DITA TC:     Developers of DITA-supporting applications     Content engineers and XML specialists     Information architects and information developers IPR Mode: RF on Limited Terms Mode of the OASIS IPR Policy Language: English -- 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)

Looks fine to me. I don't see anything here that looks like it could be limiting. Seems sufficiently broad to keep the TC busy for some time to come. /chet On Mon, Oct 11, 2021 at 1:56 PM Kristen James Eberlein < kris@eberleinconsulting.com > wrote: Dawn, Frank, Gershon, and Nancy: What do you think of this? Do you want to meet and talk this over, or do we want to get feedback from the TC on tomorrow's call? Basically, I did the following: Added a "Scope of Work" section Moved some content from "Statement of Purpose" into "Scope of Work" Changed places where we previously referred to the DITA standard to "DITA standards" (keeping the door open for LwDITA) Chet, do you think the "Scope of Work" is sufficiently broad that it won't prevent us from doing something without changing the charter? As mich work as this has been, I don't think we want to revisit the charter frequently. TC Name: Darwin Information Typing Architecture (DITA) Technical Committee (TC) Statement of Purpose: DITA is an XML-based standard for modular and extensible topic-based information. It enables content creators to separate content into semantically rich, reusable components that reflect the core purpose of the content they contain. DITA provides a model for defining and processing new components as specializations of ones, thus enabling interoperability of DITA-based content. Scope of work The scope of the DITA encompasses the following: Defining and maintaining DITA standards Promoting the use of DITA standards The DITA TC does not produce reference implementations or rate compliance of DITA products. Deliverables: The DITA TC produces the following deliverables and more: DITA specifications and associated grammar files Committee notes that contain non-normative content (tutorials, best practices, migration information, etc.) Webinar and conference presentations In addition, the DITA TC sponsors several Open OASIS GitHub repositories through which non-OASIS members can participate in DITA-related work. Audience: The following are the primary audiences for the work of the DITA TC: Developers of DITA-supporting applications Content engineers and XML specialists Information architects and information developers IPR Mode: RF on Limited Terms Mode of the OASIS IPR Policy Language: English -- 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) --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- Chet Ensign Chief Technical Community Steward OASIS Open +1 201-341-1393 chet.ensign@oasis-open.org www.oasis-open.org