-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XMLParseError after fetching categoryscheme from BIS #180
Comments
Hi @cbenz, thanks for the issue and clear summary!
Indeed, I don't find it either: not in the SDMX 2.1 standard you linked, nor in:
So this seems to not be standards-compliant SDMX-ML, idiosyncratic to this data provider. It's possible that the XML returned by this query might pass XML Schema validation (that is, the XML tag is a well-formed Some possibilities:
In any case, the design goals for Meanwhile, could you perhaps please contact the BIS via the means given on their SDMX documentation website, directing them to this issue, and ask them to please clarify what is going on? If it is case (1) above, |
Here's a reply from one Glenn Tice, via the “SDMX User Forum” (linked via the header at https://sdmx.org; unfortunately not public/requires registration):
The suggestion aligns with what I wrote earlier (“catch this exception, ignore it, and perhaps log a warning message”). I'll open a PR shortly with these changes and ask for your review. |
Running this code:
I get the following stack trace:
I understand that the following XML fragment is not supported, in particular the
class="PublicationTable"
part:This has worked until yesterday. Maybe BIS updated their SDMX API reponse content? Sadly I did not keep a copy of the working response.
Could a maintainer of this library tell me whether this is really a new SDMX feature, not implemented yet?
As of now I don't really get how to add a parser for that, but I'm going to try. (I don't find any mention of
PublicationTable
in the SDMX 2.1 information model PDF)The text was updated successfully, but these errors were encountered: