<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Brent,</div><div><br></div><div>Their data model appears to pass muster for an initial release.</div><div><br></div><div>However the naming and design rules fall short of what the governments own preferred NIEM NDR likes - and the NIEM4UML guidelines - but NIST is happily ignoring that.</div><div><br></div><div>Of course NDR alignment is a nice to have - not a required for technical operation. It would however make the XSD schema more robust, consistent and easier to develop to.<br></div><div><br></div><div>David</div><div><br></div><h3>NAMING AND DESIGN RULES (NDR) ASSESSMENT:</h3>
<ul><li style="color:red">attribute name does not match representation
term rules: 9
</li><br><font color="black"> - manufacturer - model - usage - otherUsage - disposition - otherDisposition - severity - timeStamp - type</font><br><li style="color:red">element name does not match representation
term rules: 1
</li><br><font color="black"> - Details</font><br><li style="color:red">attributes missing annotation description:
14
</li><br><font color="black"> - electionId - generatedTime - id
- manufacturer - model - usage - otherUsage - version - disposition -
otherDisposition - severity - timeStamp - type - userId</font><br><li style="color:red">attribute names not beginning with
upper case letter (A-Z): 14
</li><br><font color="black"> - electionId - generatedTime - id
- manufacturer - model - usage - otherUsage - version - disposition -
otherDisposition - severity - timeStamp - type - userId</font><br><li style="color:red">elements missing annotation description:
5
</li><br><font color="black"> - ElectionEventLog - Details - Device - ElectionEvent - Description</font><br><div><font color="red"><strong>SCORE: 7.5 out of 10.0</strong></font></div></ul><div></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: [CAVO] Fwd: [VVSG-election] Election event logging<br>
specification being finalized by the interoperability working group<br>
From: Brent Turner <<a href="mailto:turnerbrentm@gmail.com">turnerbrentm@gmail.com</a>><br>
Date: Mon, May 23, 2016 2:47 pm<br>
To: CAVO <<a href="mailto:CAVO@opensource.org">CAVO@opensource.org</a>><br>
<br>
<div dir="ltr"><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Wack, John (Fed)</b> <span dir="ltr"><<a target="_blank" href="mailto:john.wack@nist.gov">john.wack@nist.gov</a>></span><br>Date: Mon, May 23, 2016 at 11:44 AM<br>Subject: [VVSG-election] Election event logging specification being finalized by the interoperability working group<br>To: vvsg-election <<a target="_blank" href="mailto:vvsg-election@nist.gov">vvsg-election@nist.gov</a>>, vvsg-post-election <<a target="_blank" href="mailto:vvsg-post-election@nist.gov">vvsg-post-election@nist.gov</a>>, vvsg-pre-election <<a target="_blank" href="mailto:vvsg-pre-election@nist.gov">vvsg-pre-election@nist.gov</a>><br><br><br> <div link="#0563C1" vlink="#954F72" lang="EN-US"> <div> <div class="MsoNormal" style="font-size:12pt;">Hi everyone in the election, post-election, and pre-election working groups,<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">In the interoperability working group, we have decided that we are done with the election event logging common data format specification. We decided that our next step would be to send this specification to you to ensure your eyes had an opportunity to look at it, even though a good number of you are getting the interoperability working group mail posts already. Thus, I am attaching a Word and PDF version of the spec – it is quite short and, while it's not breathtaking bedtime reading, it attempts to be descriptive in a concise way and is relatively straightforward to understand.<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">A number of people have put a fair amount of time into the specification starting several years ago and more recently in the past several months. I thought we had great input and wisdom from some of the manufacturers and, as a result, we ended up with a good, simple specification.<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">If you have any questions about this specification, please respond and I'll do my best to answer them. I am sending this out on May 23 and so, in 2 weeks by June 6, if there are no showstopper issues, we can assume that we are indeed done and will move on to the next step, which is publishing it as a NIST 1500 publication.<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">If a number of you feel that it would be best to hold a telecon and for me to go over this specification and deal with any questions, I would be happy to do that.<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Cheers, John<u></u><u></u></div> </div> </div> </div><br></div> <hr>_______________________________________________<br>
CAVO mailing list<br>
<a href="mailto:CAVO@opensource.org">CAVO@opensource.org</a><br>
<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo">https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo</a><br>
</div>
</blockquote></span></body></html>