This document includes release notes for the VIP Spec for versions 6.0 and later.
- Issue #412 - Support geospatial data for modeling electoral district boundaries
- Issue #364 - Add LeaderPersonIds to Party
- Issue #297 - Links to projects implementing this specification
- Issue #279 - Improve comments in python YAML code
- Issue #400 - Add
IsMailOnly
to Locality object- PR #403
- Issue #401 - Add
ElectionNotice
to ElectionAdministration object- PR #406
- Issue #367 - Add ballot tracking URLs to ElectionAdministration object
- PR #389
- Issue #162 - restore
HouseNumberSuffix
andHouseNumberPrefix
to StreetSegment- PR #388
- Issue #351 - Add
StructuredAddress
to PollingLocation object- PR #387
- Issue #324 - YAML files become one true source for XML and CSV documentation
- PR #376
- Issue #366 - Improve Best Practice documentation
- PR #393
- Add a
Name
element to the PollingLocation object- PR #317
- Make
LocalityType
optional- Issue #337
- Several optional extensions to NIST objects
- Added a backwards-compatible
AnnotatedURI
type to allow publishers to specify metadata about aContactInformation.Uri
- Issue #317
- Created a release branch as a stable tag for the current release.
- Convergence with the released version of the NIST election
results reporting spec.
- Issue #298
- Use
xs:IDREFS
instead ofxs:IDREF maxOccurs="unbounded"
- This was also causing some issues with Java code generation
- Move Move
SequenceOrder
fromCandidate
toBallotSelectionBase
- Update
CandidateContest
to support multiplePrimaryPartyIds
- Add
Gender
toPerson
- Make
TermType
inTerm
optional - Add "borough" to
DistrictType
- Support for city-level wildcarding
- Issue #289
- Clarify documentation surrounding element use
- Issue #291
- Updated sample feed
- Convergence with the NIST election results reporting spec.
- Issue #42
- Objects and enumerations also used in the NIST ERR spec include:
CandidatePreElectionStatus
andCandidatePostElectionStatus
DistrictType
IdentifierType
BallotSelectionBase
,BallotMeasureSelection
, andCandidateSelection
BallotStyle
Candidate
ContactInformation
ContestBase
,BallotMeasureContest
,CandidateContest
,PartyContest
, andRetentionContest
HoursOpen
(known in NIST ERR asSchedule
)Office
OrderedContest
Party
Person
- Object identifiers use the
xs:ID
andxs:IDREF
types instead ofxs:string
orxs:integer
. Thexs:ID
type has certain restrictions and requirements beyond normal strings or integers.- Issue #45
- Add support for internationalization (i.e. multiple languages) via the
InternationalizedText
type. - Per-
Precinct
links toBallotStyle
elements.- Issue #94
- Per-
PollingLocation
lat/lng support.- Issue #165
- Structured hours for open and close times.
- Issue #21
StreetSegment
objects can useIncludesAllAddresses
instead of magic values forStartHouseNumber
andEndHouseNumber
.- Issue #235
- Support for various voter services being handled by different departments or
people.
- Issue #63
- Better handling of apartments/multi-home lots.
- Issue #22
- Removed
NonHouseAddress
since it was only used in one element now.- Issue #258
- All elements which specify web links are now of type
xs:anyURI
(instead ofxs:string
) and end inUri
instead ofUrl
.- Issue #87
- Structured handling of types for
ElectoralDistrict
andLocality
, replacing the free-form string with an enumeration. - The odd/even/both type (
OebType
) is now lower-case only.- Issue #46
- The
yesNoEnum
has been replaced byxs:boolean
, meaning those field can only take the valuestrue
orfalse
(case-sensitive).- Issue #66
- The spec and all content in this repository is available under a Creative
Commons Attribution 4.0 International license.
- Issue #269
- The spec generally uses a Venetian
Blind design philosophy.
- Issue #113
- Created a spec style guide.
- Created a
CONTRIBUTING
guide.
- Issue #93
- Documentation is now stored in YAML files, which are then used to generate the
RST and HTML documentation
- Issue #255
- Created an approval process for pull requests.
- Issue #117
- The sample feed now uses UTF-8.
- Issue #81