Re-send: Internationalization od OptionsList proposal

[David Mas <david.mas@scytl.com>]

Apparently the list does not allow emails with attached files, so I'll 
resubmit the text of my last message plus a diff file showing the 
discussed part.

It is a diff between emlcore-v5.0.xsd (as in version 
EML-v5-0-schemas-070522) and our changes on the same file.
This is the diff text:

START
74d73
<     <xs:element name="ReferendumOption" type="ReferendumOptionStructure"/>
644,649c643
<     <xs:complexType name="ReferendumOptionStructure">
<         <xs:sequence>
<             <xs:element ref="ReferendumOptionIdentifier" />
<             <xs:element name="Messages" type="MessagesStructure"/>
<         </xs:sequence>
<     </xs:complexType>
---
 >
659c653
<                         <xs:element ref="ReferendumOption" 
minOccurs="0" maxOccurs="unbounded"/>
---
 >                         <xs:element ref="ReferendumOptionIdentifier" 
maxOccurs="unbounded"/>
END

And here is the mentioned message, just in case it was filtered due to 
the attachments:

Hello,

   In our effort to internationalize the referendum questions options, 
we have thought about some changes to the XSD that would help to better 
support it. The changes would affect the 6xx messages, and the only type 
affected is Proposal. We propose to change the Proposal/Options element, 
so that it is composed of ReferendumOption rather than 
ReferendumOptionIdentifier. ReferendumOption would be of type 
ReferendumOptionStructure and it is composed by a 
ReferendumOptionIdentifier and a Messages, as shown in the attached 
picture (OptionsListInternationalized.jpg). The current version (draft 
of 22nd of May) is also attached for reference (OptionsListCurrent.jpg).

   Another element that we found hard to internationalize is the Area: 
its definition is as follows:
   <xs:complexType name="AreaStructure">
       <xs:annotation>
           <xs:documentation>The geographical area (and its type, such 
as County) covered by a contest</xs:documentation>
       </xs:annotation>
       <xs:simpleContent>
           <xs:extension base="xs:token">
               <xs:attribute name="Type" type="xs:token" use="optional"/>
               <xs:attributeGroup ref="DisplayIdOpt"/>
           </xs:extension>
       </xs:simpleContent>
   </xs:complexType>

   so, supporting multiple languages is not allowed. If the extended 
type were Messages instead of xs:token then any number of languages 
would be automatically supported.

   What do you think about these suggestions?

Thank you,

-- 
David Mas Santaló, Software Engineer

e-mail: david.mas@scytl.com
phone:  +34 934 230 324
fax:    +34 933 251 028

Scytl Secure Electronic Voting
C. Tuset 20 1-7
08006 Barcelona, Spain
http://www.scytl.com 


NOTICE: The information in this e-mail and in any of its attachments is
confidential and intended solely for the attention and use of the named
addressee(s). If you are not the intended recipient, any disclosure,
copying, distribution or retaining of this message or any part of it,
without the prior written consent of Scytl Secure Electronic Voting SA,
is prohibited and may be unlawful. If you have received this in error,
please contact the sender and delete the material from any computer.