We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From an email:
I am trying to use the Gepsio project to parse Japanese corporate governance reports in XBRL format. But the document is failing to load. I have attached the raw files here. Would you be able to take a look and see what's going on? The files are obtained originally from here http://www2.tse.or.jp/tseHpFront/CGK020010Action.do?Show=Show After you do a search on a Japanese stock, say 4321 JP, then download the zip file. The error message is on Line 245 in XbrlSchema.cs, on the compile function call; it complains that Type XXXXXXXX is not declared.
I am trying to use the Gepsio project to parse Japanese corporate governance reports in XBRL format.
But the document is failing to load. I have attached the raw files here.
Would you be able to take a look and see what's going on? The files are obtained originally from here
http://www2.tse.or.jp/tseHpFront/CGK020010Action.do?Show=Show
After you do a search on a Japanese stock, say 4321 JP, then download the zip file.
The error message is on Line 245 in XbrlSchema.cs, on the compile function call; it complains that Type XXXXXXXX is not declared.
Attachments: XBRL.zip
The text was updated successfully, but these errors were encountered:
It seems that there's an error on taxonomy : Type informationOnRetiredPresidentsOrCEOsHoldingAdvisoryPositionsItemType used in schema http://www.xbrl.tdnet.info/jp/br/tdnet/t/cg/2007-06-30 is not defined in schema for namespace http://www.xbrl.tdnet.info/jp/br/tdnet/o/cg/cm/2007-06-30.
Sorry, something went wrong.
No branches or pull requests
From an email:
Attachments: XBRL.zip
The text was updated successfully, but these errors were encountered: