You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR: 'The prefix "xsi" for attribute "xsi:schemaLocation" associated with an element type "crossref" is not bound.'
From what I could deduce from reading the source code and debugging, each metadata node is parsed individually by the XOAI library. And, in that context, the xsi prefix is indeed not bound, as it is only defined in parent node OAI-PMH.
There should be a way to configure the XML reader to ignore namespace errors.
The text was updated successfully, but these errors were encountered:
The xml serialiser we use (lxml) won't repeat namespaces, so the oai_dc element does not define the xsi namespace, since it is already represented at the top of the OAI-PMH document. While this is technically not spec compliant, it is valid XML, and it would be helpful if the XOAI library could cope with that.
See the referenced bug report for details DOAJ/doaj#2186
Giving the following response XML from an OAI repository:
We get an error if we try to parse it using XOAI.
ERROR: 'The prefix "xsi" for attribute "xsi:schemaLocation" associated with an element type "crossref" is not bound.'
From what I could deduce from reading the source code and debugging, each metadata node is parsed individually by the XOAI library. And, in that context, the xsi prefix is indeed not bound, as it is only defined in parent node OAI-PMH.
There should be a way to configure the XML reader to ignore namespace errors.
The text was updated successfully, but these errors were encountered: