FW: [dita] Protocol for specialization working groups

["Mary McRae" <mary.mcrae@oasis-open.org>]

Hi everyone,

  Great topic - and I'm glad to see there's so much interest! 

  There's a couple of alternatives within the OASIS structure that the TC might wish to consider.

  The first - and simplest - is the creation of subcommittees. To be a member of a subcommittee you must be a member of the TC (not
necessary to be a voting member). A subcommittee can't make formal decisions; they would do all the work, and then submit to the
full TC for any necessary votes. The nice part of this is the built-in coordination aspect.

  The second option would be to create separate TCs. They would each have their own charter, voting membership, etc. 

  A third option is a combination of the two - basically creating something akin to a "member section" which has a steering
committee. Each of the separate TCs would then unify under this umbrella. TCs could have unique membership, but activities would be
coordinated.

  I'll be happy to provide more details or any other info.

  And since I'm here, congratulations to everyone who participated in the development of DITA v1.0!

Regards,

Mary  


 

> -----Original Message-----
> From: Don Day [mailto:dond@us.ibm.com]
> Sent: Tuesday, May 10, 2005 10:48 AM
> To: DITA TC list
> Subject: [dita] Protocol for specialization working groups
> 
> Indi Liepa asked me, What is the protocol for starting a DITA 
> telecommunications specialization working group.  Meanwhile, Seraphim 
> has a similar question for a semiconductor industry specialization 
> that has several interested parties already lined up.
> 
> The Charter for the DITA TC describes the community-building role for 
> promotion of DITA as a Standard:
> 
>    To encourage cooperation within and between the various topical 
> domains
>    of potential DITA users
> 
> 
>    It is anticipated that, in addition to the common information 
> elements
>    provided in the base specification, specific communities of users 
> may
>    develop additional, specialized type hierarchies of particular 
> relevance
>    to their use cases. The TC may choose to recognize new information 
> types
>    or domain specializations where a new specialization provides a 
> standard
>    solution for a well-established need, has broad support, does not
>    conflict with existing types, and serves as a useful base for 
> additional
>    specialization. For example, the concept, task, and reference
>    information types do so for the user assistance community. The TC
>    anticipates maintaining a set of core information types of general
>    utility, implemented in schema languages (such as DTD or XML 
> Schema)
>    selected by the TC. Recognized types may also be maintained by 
> other
>    groups (including other OASIS TCs).
> 
> We need to start thinking about how to nurture and host these 
> specialization activities that are starting to spring forth.
> We need to provide these teams with ideas about how to conduct a 
> specialization process. We must plan how we will use OASIS facilities 
> (if feasible) for a DITA Specialization Registry or other way to host 
> specializations as spinoffs of the DITA core activity. How should such 
> activities be governed?
> Should they report to the TC?  How can we help other such activities 
> get started?
> 
> Whew--the list could go on.  What are your thoughts about how the TC 
> should help instigate/guide/mentor these activities?
> 
> Regards,
> --
> Don Day <dond@us.ibm.com>
> Chair, OASIS DITA Technical Committee
> IBM Lead DITA Architect
> 11501 Burnet Rd., MS 9037D018, Austin TX 78758
> Ph. 512-838-8550   (T/L 678-8550)
> 
> "Where is the wisdom we have lost in knowledge?
> Where is the knowledge we have lost in information?"
>         --T.S. Eliot
> 
>