-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
The taxonomy with namespace http://fasb.org/us-gaap/2020-01-31 could not be found #28
Comments
I got the same error for the instance: Error Message
|
Any idea on how to solve this issue in a general way? The problem is that the |
To deal with this issue I created a function that maps common namespaces (such as the dei or us-gaap taxonomy) to the corresponding namespace. However this apparently does not work in your case. I will check why it's not working and implement a fix. I don't really know how to solve this in a general way. The taxonomy schema file can be stored on any server on the internet. So it is impossible to locate the taxonomy schema if you only have the namespace. For all popular taxonomies the solution with a mapping from namespace to schema url is probably the only solution 🤔. |
Seems to work now with both submissions you provided. The issue was that these submission do not even mention the us-gaap and dei taxonomies in their extension taxonomy. Due to the fact that both the us-gaap and the dei taxonomy are standard taxonomies we can easily parse and load these taxonomies even after the extension taxonomy was already parsed. I will create a new minor version of the package that contains this change. |
Awesome work! Thank you very much. I really appreciate the effort 👍 |
Bug description
Steps to reproduce the behavior
Error Trace
The text was updated successfully, but these errors were encountered: