<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div><a href="http://docs.oasis-open.org/election/eml/v5.0/os/EML-Process-Data-Requirements-v5.0.pdf">http://docs.oasis-open.org/election/eml/v5.0/os/EML-Process-Data-Requirements-v5.0.pdf</a> </div>
<div> </div>
<div>FYI - Section 3 - overview of election process.</div>
<div> </div>
<div>This is good conceptual view of all the moving parts. Where it gets weird of course is aligning this with the 5,000 ways elections are done here in the USA.</div>
<div> </div>
<div>It's not hard - but people love to make it so - as the IEEE is doing with their 1622 initiative that has sadly taken a swerve off into a bad place WRT to XML they are generating from models.</div>
<div> </div>
<div>Aside: I know - I've told them that is a really bad idea - I've told them not even the OMG is doing it that way - but what do I know - I'm not a UML modeler, right!? They shot the messenger.</div>
<div> </div>
<div>Then I see a couple of online hackathons that are completely reinventing both OASIS EML and Google VIP all over again - and ignoring existing standards work.</div>
<div> </div>
<div>Ho hum. But we digress.</div>
<div> </div>
<div>Back to the task in hand - I'm seeing the OASIS work forms a solid foundation for defining a working process for California - informed by actual public standards, that have actually been used successfully in elections in EU, Asia and USA.</div>
<div> </div>
<div>David</div></span></body></html>