Election Markup Language 3.0

Part 1 version: Id: structures.xsd,v 1.2 2004/01/15 11:34:25 ht Exp
Part 2 version: Id: datatypes.xsd,v 1.3 2004/01/23 18:11:13 ht Exp

The schema corresponding to this document is normative,
with respect to the syntactic constraints it expresses in the
XML Schema language.  The documentation (within <documentation> elements)
below, is not normative, but rather highlights important aspects of
the W3C Recommendation of which this is a part

The simpleType element and all of its members are defined
   towards the end of this schema document

simple type for the value of the 'namespace' attr of
'any' and 'anyAttribute'

Value is
           ##any      - - any non-conflicting WFXML/attribute at all
           ##other    - - any non-conflicting WFXML/attribute from
                           namespace other than targetNS
           ##local    - - any unqualified non-conflicting WFXML/attribute
           one or     - - any non-conflicting WFXML/attribute from
           more URI        the listed namespaces
           references
           (space separated)
 ##targetNamespace or ##local may appear in the above list, to
     refer to the targetNamespace of the enclosing
     schema or an absent targetNamespace respectively

notations for use within XML Schema schemas

First the built-in primitive datatypes.  These definitions are for
information only, the real built-in definitions are magic.

For each built-in datatype in this schema (both primitive and
derived) can be uniquely addressed via a URI constructed
as follows:
  1) the base URI is the URI of the XML Schema namespace
  2) the fragment identifier is the name of the datatype
For example, to address the int datatype, the URI is:
  http://www.w3.org/2001/XMLSchema#int
Additionally, each facet definition element can be uniquely
addressed via a URI constructed as follows:
  1) the base URI is the URI of the XML Schema namespace
  2) the fragment identifier is the name of the facet
For example, to address the maxInclusive facet, the URI is:
  http://www.w3.org/2001/XMLSchema#maxInclusive
Additionally, each facet usage in a built-in datatype definition
can be uniquely addressed via a URI constructed as follows:
  1) the base URI is the URI of the XML Schema namespace
  2) the fragment identifier is the name of the datatype, followed
     by a period (".") followed by the name of the facet
For example, to address the usage of the maxInclusive facet in
the definition of int, the URI is:
  http://www.w3.org/2001/XMLSchema#int.maxInclusive

Now the derived primitive types

			Changes from version 0.3 to 1.0 (2002-10-10):
				None
			Changes from version 0.2 to 0.3 (2002-10-08):
				ElectionEventName changed to Event
				xsd:any made optional
				ConfirmationReference made optional
				Messages made optional
			Changes from version 0.1 to 0.2 (11/7/2002):
				ElectionEventName added

			Changes from version 0.8 to 1.0 (2002-10-10):
				Proxy and PostalProxy removed from enumerations for VotingChannelType
				New element ProxyAgrees added to Proxy
				Messages element made optional in IncomingGenericCommunicationsStructure and OutgoingGenericCommunicationsStructure
			Changes from version 0.7 to 0.8 (2002-10-07):
				More detail added to Affiliation
				Multiple Id elements added to Proposer to allow, for example, electoral roll numbers to be added
				New Candidate element and CandidateStructure type replace CandidateName
				New Agent element and AgentStructure type added
				EventStart and EventEnd removed
				New DateType simple type is a union of xsd:date and xsd:dateTime
				New Gender element
				New Logo element
				Candidate Id attribute made optional as it is not known at the time of nomination
				LocationName replaced by PollingPlace. This allows multiple levels.
				Message now has an optional Type attribute
				ElectionEventName replaced by Event with an EventName and EventQualifier
				Added ProxyStructure
				In VoterInformationStructure, Military replaced by more general Qualification
				Optional TransactionId added to EML element so it is available to every message
				Message element has an optional xml:lang element. This has been removed from other places that added it (ElectionStatement, Profile)
			Changes from version 0.6 to 0.7:
				AuditInformationStructure changed to allow logging of more device types
				AuditInformation element deleted as use will be by derivation from the data type
				ProcessingUnitStructure added for inclusion in the audit information
			Changes from version 0.5 to 0.6:
				ReportingUnitNameStructure and ReportingUnitName added
			Changes from version 0.4 to 0.5:
				ScrutinyRequirementStructure and ScrutinyRequirement added
				VTokenQualified and VTokenQualifiedStructure added
				VTokenQualified added as an alternative to VToken in VoterIdentificationStructure
				AuditInformationStructure now has the audit information included
				Proxy added to OutgoingGenericCommunicationStructure and IncomingGenericCommunicationStructure
				TransactionId removed from OutgoingGenericCommunicationStructure and IncomingGenericCommunicationStructure
				Proxy and PostalProxy added to enumerations for VotingChannelType

This schema references external schemas where the references might be changed for national use. The intention is that these schemas are used internationally.

			Changes from version 0.4 to 1.0 (2002-10-08):
				CastVote now an extension of the CastVoteStructure defined in 440
				Added ProposedRejection to CastVote
			Changes from version 0.3 to 0.4 (2002-10-08):
				Optional xsd:any added
			Changes from version 0.2 to 0.3 (2002-07-11):
				AuditInformation added

			Changes from version 0.4 to 1.0:
				Made a data type for extension in 460
			Changes from version 0.3 to 0.4:
				ElectionEventName changed to Event
				Value leg of selection made optional and this area of Option simplified
				ID attribute of Option removed
				Option made optional to allow for abstentions
				Optional BallotReference added (used in 460 for electronically counted paper votes)
				xsd:any made optional
			Changes from version 0.2 to 0.3:
				Addition of Reporting Unit
				Update to AuditInformation

			Changes from version 0.2 to 1.0 (2002-10-10):
				Optional Proxy element added
			Changes from version 0.1 to 0.2 (2002-10-07):
				xsd:any made optional

			Changes to version 1.0 (2002-10-29):
				xsd:any child of Contest made optional
			Changes from version 0.3 to 1.0 (2002-10-10):
				None
			Changes from version 0.2 to 0.3 (25/9/2002):
				CandidateName changed to Candidate
				Candidate now a child of Contest
				Multiple contests allowed
				Optional xsd:any added to CandidateList and Contest elements
			Changes from version 0.1 to 0.2 (11/7/2002):
				ElectionName added

			Changes from version 0.4 to 1.0 (2002-10-10):
				None
			Changes from version 0.3 to 0.4 (2002-10-08):
				ElectionEventName replaced by Event
			Changes from version 0.2 to 0.3 (2002-11-07):
				Multiple elections per message allowed
				AuditInformation added
			Changes from version 0.1 to 0.2:
				Addition of Reporting Units to the count

			Changes from version 0.4 to 1.0 (2002-10-10):
				None
			Changes from version 0.3 to 0.4 (2002-09-20 to meet needs of UK local elections):
				ElectionEventName replaced by new Event element
				PollingPlace added
				New element Blocked with a Reasion attribute to mark if voter has postal vote, already voted by another method etc
				Qualifier added to allow partial lists (e.g. of those with postal votes)
				optional xsd:any added

			Changes from version 0.5 to 1.0 (2002-10-10):
				None
			Changes from version 0.4 to 0.5 (2002-10-02):
				VoterRegistrationStructure made a global type for use elsewhere
				VoterInformation made optional
				element Proxy added
				element CheckBox added
				xsd:any added to Voter
			Changes from version 0.3 to 0.4:
				VoterIdentification altered to use the new definition of VoterIdentificationStructure in emlcore v0.5

			Changes from version 0.3 to 1.0 (2002-10-10):
				None
			Changes from version 0.2 to 0.3 (19/9/2002):
				The Status attribute of VToken and VTokenQualified changed to mandatory and made an xsd:string
				ElectionEventName changed to Event
			Changes from version 0.1 to 0.2 (11/7/2002):
				AuditInformation added

			Changes from version 0.2 to 1.0 (2002-10-10):
				None
			Changes from version 0.1 to 0.2:
				CandidateName and CandidateContact replaced by Candidate
				Only one xsd:any allowed at end

			Changes from version 0.4 to 1.0 (2002-10-10):
				None
			Changes from version 0.3 to 0.4 (2002-10-07):
				ElectionEventName changed to Event
				Options is a choice between Candidate and Option This allows more variation between elections and referenda.
				New element "Qualified" with a "Reason" attribute
				VoterContact renamed Contact
				Proxy added
			Changes from version 0.2 to 0.3:
				Addition of Reporting Unit
			Changes from version 0.1 to 0.2:
				VoterIdentification altered to use the new definition of VoterIdentificationStructure in emlcore v0.5

			Changes from version 0.2 to 1.0 (2002-10-10):
				None
			Changes from version 0.1 to 0.2 (2002-10-07):
				xsd:any made optional

			Changes from version 0.4 to 1.0 (2002-10-10):
				Optional Proxy element added
			Changes from version 0.3 to 0.4 (2002-10-07):
				xsd:any made optional

			Changes from version 0.3 to 1.0 (2002-10-10):
				None
			Changes from version 0.2 to 0.3 (2002-09-20)
				TransactionId removed (now in emlcore)
			Changes from version 0.1 to 0.2:
				AuditInformation removed

			Changes from version 0.3 to 1.0 (2002-10-10):
				None
			Changes from version 0.2 to 0.3:
				Candidate now uses the expanded version from EML core
				Choice added between nomination and candidate action. Candidate action can be to consent or withdraw.
				Only one xsd:any allowed at end
			Changes from version 0.1 to 0.2:
				ScrutinyRequirements added

			Changes from version 0.3 to 1.0 (2002-10-10):
				None
			Changes from version 0.2 to 0.3 (26/9/2002):
				Optional Event added
			Changes from version 0.1 to 0.2 (11/7/2002):
				AuditInformation added

			Changes from version 0.5 to 1.0 (2002-10-10):
				None
			Changes from version 0.4 to 0.5 (2002-09-20):
				ElectionEventName replaced by Event
				LocationName relaced by PollingPlace
				VotingPeriod allowed per channel and has DisplayOrder added. Unbounded to allow poll opening and closing times. Removed from previous location.
			Changes from version 0.3 to 0.4:
				VoterIdentification altered to use the new definition of VoterIdentificationStructure in emlcore v0.5
				VotingInformation changed to allow a VTokenQualified as an alternative to a VToken

			Changes from version 0.3 to 1.0 (2002-10-10):
				None
			Changes from version 0.2 to 0.3 (2002-09-24)
				TransactionId removed (now in emlcore)
				ElectionEventName changed to Event
				Ballots restriction has been re-applied. This brings in the current version of Ballots from 410
				Under Ballot, the choice between ElectionRuleId and Voter has a maxOccurs of 0
			Changes from version 0.1 to 0.2:
				VoterIdentification altered to use the new definition of VoterIdentificationStructure in emlcore v0.5

			Changes from version 0.2 to 1.0 (2002-10-10):
				None
			Changes from version 0.1 to 0.2 (2002-10-01):
				ElectionEventName changed to new Event element
				DefaultLanguage added
				An additional Date element has been added for general use for other relevant dates
				ResponsibleOfficer added with contact details
				Each channel can now have start and end dates and times. Multiple entries are allowed to show open and close of channel over multiple days
				EventDate element replaces EventStart and EventEnd
				Repeateable generic Contact element added
				PollingPlace added to Contest
				Messages element added at Election Event, Election and Contest levels
				MinVotes made optional
				xsd:any added

			Changes from version 0.2 to 1.0 (2002-10-10):
				None
			Changes from version 0.1 to 0.2 (2002-10-07):
				xsd:any made optional

			Changes from version 0.4 to 1.0 (2002-10-10):
				None
			Changes from version 0.3 to 0.4 (2002-09-20)
				TransactionId removed (now in emlcore)
			Changes from version 0.2 to 0.3:
				Data type (xsd:string) added to Action
			Changes from version 0.1 to 0.2:
				Source and Destination elements changed from xsd:string to a union of xsd:string and xsd:anyURI