Skip to content
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

Open
sreedesai opened this issue Apr 2, 2020 · 19 comments
Open

Nested Schema causing validation error #37

sreedesai opened this issue Apr 2, 2020 · 19 comments
Assignees

Comments

@sreedesai
Copy link

sreedesai commented Apr 2, 2020

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.

image

@JeffFerguson
Copy link
Owner

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.

@sreedesai
Copy link
Author

Here they are.

fer-20200228-121430.zip

Form1.zip

@JeffFerguson
Copy link
Owner

Thank you!

@JeffFerguson
Copy link
Owner

So the fer-20200228-121430 ZIP is the main XBRL instance? Do you have everything in the same folder along with the contents of the other ZIP?

@sreedesai
Copy link
Author

Form1.zip is the industry standard taxonomy and fer-20200228-121430.zip is the xbrl sample instance we are trying to validate against it.

@JeffFerguson
Copy link
Owner

Understood. Thank you. And do you happen to know which version of Gepsio you're using?

@JeffFerguson JeffFerguson self-assigned this Apr 2, 2020
@JeffFerguson JeffFerguson added the investigation needed Investigation needed. label Apr 2, 2020
@sreedesai
Copy link
Author

I am sorry, misread your question. Yes, they are in the same folder.
Library: 'Gepsio' version '2.1.0.16'

@JeffFerguson
Copy link
Owner

Thank you! I'll start looking at this today.

@JeffFerguson JeffFerguson added investigating and removed investigation needed Investigation needed. labels Apr 3, 2020
@JeffFerguson
Copy link
Owner

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.

@JeffFerguson
Copy link
Owner

Yep. Looks like a bug to me. Here is the schema reference chain that I see:

  • The schema element for fact NameOfOfficerWithCustodyOfCorporateBooks is defined in ferc-core_2020-01-01.xsd
  • fer-20200228-121430.xml is the XBRL instance document
  • fer-20200228-121430.xml has a <schemaRef> to ferc-all_2020-01-01.xsd
  • ferc-all_2020-01-01.xsd has an <import> of ferc-core_2020-01-01.xsd

I'll debug Gepsio's schema loading processes now.

@JeffFerguson
Copy link
Owner

As I suspected: Gepsio is not properly handling <import> directives in top-level schemas. I'll get to work on a fix.

@sreedesai
Copy link
Author

sreedesai commented Apr 3, 2020 via email

@sreedesai
Copy link
Author

sreedesai commented Apr 7, 2020 via email

@JeffFerguson
Copy link
Owner

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.

@sreedesai
Copy link
Author

sreedesai commented Apr 7, 2020 via email

@JeffFerguson
Copy link
Owner

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 <import> processing. Now, I need to check to make sure I can find that fact that you were hoping to find.

@JeffFerguson
Copy link
Owner

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.

@sreedesai
Copy link
Author

sreedesai commented Apr 7, 2020 via email

@sreedesai
Copy link
Author

Hi Jeff, checking if you have any update on this. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants