Difference between revisions of "Quality Analysis in Ballot"
Jump to navigation
Jump to search
WoodyBeeler (talk | contribs) (Created page with 'Since January 2010 WGM, V3 Publishing has extended Quality Analysis and Reporting as follows: *Created domain-specific reports in order that each Faciulitator can focus on her/hi…') |
WoodyBeeler (talk | contribs) |
||
| Line 4: | Line 4: | ||
*In ballot QA Report, flagged the "fatal errors" that cause validation errors vis-a-vis the "soft" errors (such as an undefined concept domain) that can be corrected by subsequent additions to the vocabulary content. | *In ballot QA Report, flagged the "fatal errors" that cause validation errors vis-a-vis the "soft" errors (such as an undefined concept domain) that can be corrected by subsequent additions to the vocabulary content. | ||
*Updated the transforms used to go from static model designs (in either "Visio xml" or "RoseTree hmd" formats) in order to eliminate those errors that can be detected during conversion '''and can be corrected algorithmically with no "decisions"'''. (This reduced validation errors by 90%, when applied to the content of Ballot2010May.) | *Updated the transforms used to go from static model designs (in either "Visio xml" or "RoseTree hmd" formats) in order to eliminate those errors that can be detected during conversion '''and can be corrected algorithmically with no "decisions"'''. (This reduced validation errors by 90%, when applied to the content of Ballot2010May.) | ||
| + | *In both Ballot2010May and NormativeEdition2010 (now assembled for electronic review) the domain-specific Quality Analysis Report was automatically added to the published domain, and integrated into the table-of-contents for that domain. Further, a "Note to Balloters" was added to Ballot2010May to call attention to these reports and to suggest that these might be used to support Negative votes. | ||
Revision as of 12:34, 15 May 2010
Since January 2010 WGM, V3 Publishing has extended Quality Analysis and Reporting as follows:
- Created domain-specific reports in order that each Faciulitator can focus on her/his area of responsibility
- Extended the metrics analyzed to include errors that lead to validation failures of the generated schemas or of the generated MIF files
- In ballot QA Report, flagged the "fatal errors" that cause validation errors vis-a-vis the "soft" errors (such as an undefined concept domain) that can be corrected by subsequent additions to the vocabulary content.
- Updated the transforms used to go from static model designs (in either "Visio xml" or "RoseTree hmd" formats) in order to eliminate those errors that can be detected during conversion and can be corrected algorithmically with no "decisions". (This reduced validation errors by 90%, when applied to the content of Ballot2010May.)
- In both Ballot2010May and NormativeEdition2010 (now assembled for electronic review) the domain-specific Quality Analysis Report was automatically added to the published domain, and integrated into the table-of-contents for that domain. Further, a "Note to Balloters" was added to Ballot2010May to call attention to these reports and to suggest that these might be used to support Negative votes.
