RE: [election-services] question about process for v6

["David RR Webber \(XML\)" <david@drrw.info>]

Joe,

 

I'll give this a shot.

 

John basically coordinates the process as chair.  We start by collecting the "Wishes List" - then use that as a driver to facilitate changes to the schemas / specifications.  During that process the technical editors may raise questions to the team for resolution.  Then we iterate through drafts of the schemas until we're happy with them.  Next we produce the documentation updates and new release of the specification.  This then becomes the committee draft along with the schema package - and then we head into the OASIS review and approval balloting process, along with fixes and changes as people provide them either from within the team of from the public review periods.  There's a formal comment and review mechanism with outcomes and resolutions required. 

 

OASIS has its requirements on what the specifications should include, layout, format, and supporting artifacts, along with documentation in Kavi of ballots, meetings et al to support the process.  Assembling and marshalling all that is quite often a larger part of the task.

 

John will call meetings as needed to resolve issues, get consensus, brainstorm, etc, and assign tasks to willing volunteers as they step forward.

 

This is pretty "normal" for how things work in OASIS!

 

Hope that helps.

 

Thanks, DW

 

 

-------- Original Message --------
Subject: [election-services] question about process for v6
From: "Joseph Lorenzo Hall" <joehall@berkeley.edu>
Date: Thu, January 08, 2009 3:09 pm
To: "EML TC" <election-services@lists.oasis-open.org>

I was excited to see that v6 is in the infancy of thought here... and
that one goal is to facilitate used of EML in things like the VIP.

However, I have a very newbie-like question, considering I joined this
TC after v5 was developed but before it was balloted: How does an
incremental change to something like EML happen?

Does it go something like this?

1. TC decides goals for support in v6.
2. TC decides what technically it would take to make that happen.
3. TC revises goals based on difficulties anticipated from previous step.
4. TC divvies up and begins to implement changes.
5. TC converges and tests, documents, etc. the new version.
6. TC submits an initial standard for public review.
7. (Other OASIS procedures that I'm familiar with from the v5 process)

Apologies if this is documented somewhere. best, Joe

--
Joseph Lorenzo Hall
ACCURATE Postdoctoral Research Associate
UC Berkeley School of Information
Princeton Center for Information Technology Policy
http://josephhall.org/

---------------------------------------------------------------------
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