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

fix schemaLocation namespace issue and import schemas #2

Closed
wants to merge 3 commits into from

Conversation

jnettleton
Copy link

fix schemaLocation namespace issue
add support to import schemas

@JeffFerguson
Copy link
Owner

JeffFerguson commented Sep 13, 2017

Thank you for submitting this pull request! I appreciate your interest in improving Gepsio.

Can you tell me more about the issue here and what the modifications are trying to solve?

@jnettleton
Copy link
Author

jnettleton commented Sep 13, 2017 via email

@JeffFerguson
Copy link
Owner

Great! Justin is a good guy. I worked with him several years ago.

I'll look over the pull request and see what jogs my memory! I've done a bit of work in that area lately, so some of it may have been (partially) solved.

Thank you for trying Gepsio! Keep those suggestions coming.

@jnettleton jnettleton closed this Sep 13, 2017
@jnettleton
Copy link
Author

jnettleton commented Sep 13, 2017

The other code change had to do with schemaLocation "namespace/location pairs". Fixed the TargetNamespace when necessary. There were cases where the Targetnamespace was null and I used the value (from the pair) to update it.

mmm-20161231_cal.xml:<linkbase xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.xbrl.org/2003/linkbase" xmlns:xbrli="http://www.xbrl.org/2003/instance" xmlns:xlink="http://www.w3.org/1999/xlink" **xsi:schemaLocation="http://www.xbrl.org/2003/instance http://www.xbrl.org/2003/xbrl-instance-2003-12-31.xsd"**>

@jnettleton
Copy link
Author

closed it by accident

@jnettleton jnettleton reopened this Sep 13, 2017
@jnettleton
Copy link
Author

strange, I only tried to submit the first commit. not sure how to fix it.

@jnettleton
Copy link
Author

seems like I should create a pull request for your develop branch

@jnettleton jnettleton closed this Oct 4, 2017
@jnettleton jnettleton changed the base branch from master to develop October 4, 2017 23:34
@jnettleton
Copy link
Author

moved to your develop branch. you can decider if/when you want to check it out. worked fine for testing the dutch taxonomy.

@jnettleton jnettleton reopened this Oct 4, 2017
@JeffFerguson
Copy link
Owner

Thank you, Jerry! Yes, changes should go against the develop branch. I need to write a CONTRIBUTING.md document that describes how I would like to see branching and testing. Thank you for your contribtion! Stand by for that CONTRIBUTING.md document.

@JeffFerguson
Copy link
Owner

Hi @jnettleton ... take a look at Issue 3 at #3 ... does your pull request solve this issue? Or is it a separate issue?

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

Successfully merging this pull request may close these issues.

None yet

2 participants