<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:495849500;
mso-list-type:hybrid;
mso-list-template-ids:-2077044100 201916417 201916419 201916421 201916417 201916419 201916421 201916417 201916419 201916421;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I’m trying to use the auto-generated XSD schema at /cgi/schema in 3.2 to assist with some integration work involving SWORD and EPrints XML packages. The schema is making it difficult to validate the XML packages we are using.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>The encoding attribute on the data element is not allowed by the schema even though it is supplied by the XML with files embedded export plugin.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>All sub-fields of a compound type are required by the schema whereas, to my knowledge, EPrints elsewhere doesn’t support this notion explicitly (except by custom validation)<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>The schema doesn’t allow Namedset fields to be blank or ‘UNSPECIFIED’ etc even though this may be a valid value depending on the workflow configuration.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve attached a patch against 3.2 that addresses these three issues. It looks like it should work in 3.3 also. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The patch for the latter two issues weakens the constraints imposed by the schema but makes the schema applicable in a greater number of what I would consider normal scenarios. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>With the patch I can validate the simple EPrints XML documents/packages we are using in our current work successfully but if I export a real eprint and validate the output there are numerous validity errors reported, which seem to relate to issues and indexcodes files. I haven’t got the time to look at these at the moment.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers<o:p></o:p></p><p class=MsoNormal>Mark<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><span style='color:#C50B45'>Mark Gregson</span></b><b> </b>| Applications and Development Team Leader<br><span style='color:gray'>Library eServices | Queensland University of Technology<br>Level 3 | R Block | Kelvin Grove Campus | GPO Box 2434 | Brisbane 4001<br>Phone: +61 7 3138 3782 | Web:</span><span style='color:#A3A3A3'> </span><u><span style='color:#0000FD'><a href="http://www.qut.edu.au/">http://eprints.qut.edu.au/</a><br></span></u><span style='color:#0080FF'>ABN: 83 791 724 622<br>CRICOS No: 00213J<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>