-
Notifications
You must be signed in to change notification settings - Fork 26
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
Nested Schema causing validation error #37
Comments
Thanks for the report! Can you attach the XBRL instance file as well as any schemas or linkbase documents that you have locally? I'd like to be able to reproduce and debug the issue. |
Here they are. |
Thank you! |
So the |
Form1.zip is the industry standard taxonomy and fer-20200228-121430.zip is the xbrl sample instance we are trying to validate against it. |
Understood. Thank you. And do you happen to know which version of Gepsio you're using? |
I am sorry, misread your question. Yes, they are in the same folder. |
Thank you! I'll start looking at this today. |
Yikes! Gepsio reports 1,827 validation errors on the document you provided. I'm guessing that the number will come down after the fix is applied. Thanks again for the samples. They helped me write a unit test for this issue. I'm debugging the unit test and Gepsio interactions now. |
Yep. Looks like a bug to me. Here is the schema reference chain that I see:
I'll debug Gepsio's schema loading processes now. |
As I suspected: Gepsio is not properly handling |
Thank you for your quick turnaround. The fix will be a big help.
…On Fri, Apr 3, 2020 at 6:57 AM Jeff Ferguson ***@***.***> wrote:
As I suspected: Gepsio is not properly handling <import> directives in
top-level schemas. I'll get to work on a fix.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA2G74R7CLQHCV5YMAHAOTRKXTMZANCNFSM4L2VBY6Q>
.
|
Morning Jeff,
Any luck with this?
Thanks,
Sree
…On Fri, Apr 3, 2020 at 7:57 AM Jeff Ferguson ***@***.***> wrote:
Hang on .. that might be my error, not the schema's. More in a bit.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA2G77GEFN5WCSA5FNGOUDRKX2L5ANCNFSM4L2VBY6Q>
.
|
Hi! Still working on it today. Debugging some schema namespace issues. The |
Ok thank you Jeff
…On Tue, Apr 7, 2020 at 7:48 AM Jeff Ferguson ***@***.***> wrote:
Hi! Still working on it today. Debugging some schema namespace issues. The
<import> elements have some schema namespace information that Gepsio
needs to keep track of.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA2G73ZY3RGPLPMQBHBDPTRLM4KFANCNFSM4L2VBY6Q>
.
|
Progress! It takes a lot longer to load all of those schemas, but the validation errors have gone down from 1,827 to a mere 172 after the |
It's good to see that the validation error count has gone way down, but I still need to put a little work in to find the fact. I'll keep on this one. |
Awesome, thank you so much
…On Tue, Apr 7, 2020 at 11:50 AM Jeff Ferguson ***@***.***> wrote:
It's good to see that the validation error count has gone way down, but I
still need to put a little work in to find the fact. I'll keep on this one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA2G74VCJWB3JVW66QXCIDRLNYWFANCNFSM4L2VBY6Q>
.
|
Hi Jeff, checking if you have any update on this. Thank you. |
Hi Jeff,
Getting an error when validating. It is probably not loading the nested schema files.
Fact NameOfOfficerWithCustodyOfCorporateBooks references a namespace with a URI of http://ferc.gov/form/2020-01-01/ferc, but no schema can be found for that namespace.
Schema element information is not available for this fact.
Schema it is trying to import is in the same folder as the Main schema referencing it.
The text was updated successfully, but these errors were encountered: