Error retrieving taxonomy file that does appear to exist #93
-
I am encountering the following error when trying to parse an iXBRL file saved locally. With other files, the parser is able to download all the relevant taxonomies, but this file (and many others like it) are failing when trying to retrieve certain taxonomies. The error appears to indicate that such a taxonomy does not exist, but following the link indicates that there is something present. My knowledge of XBRL is limited and I am not sure what is causing this error. My code block is as follows: `logging.basicConfig(level=logging.INFO) cache: HttpCache = HttpCache('./cache') schema_url = "./07804038_aa_2021-08-27.xhtml" The taxonomy is linked at this address which does appear to exist. Yet I get the following error. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
The error code 404 implies that the file could not be found on the server. However, I was also able to retrieve the file using the url you provided. Have you tried setting the HTTP header? https://py-xbrl.readthedocs.io/en/latest/usage.html#online If you want you can send me the xbrl file via email and i will try to parse it myself. |
Beta Was this translation helpful? Give feedback.
-
@ahoward-cf Unfortunately the parser is still not able to parse the instance document you provided. This is not only invalid XBRL but also invalid with regards to the XML Specification, as each prefix must have a namespace. |
Beta Was this translation helpful? Give feedback.
@ahoward-cf Unfortunately the parser is still not able to parse the instance document you provided.
The issue is that the filer uses the prefix 'dpl-frs' but does not specify a namespace for it. (the
xmlns:dpl-frs="..."
is missing).This is not only invalid XBRL but also invalid with regards to the XML Specification, as each prefix must have a namespace.
So unfortunately there is no way to parse this particular filing. Filings from bigger companies and/or from trustworthy sources (as EDGAR or UK Company House) should not be syntactically incorrect.