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

FI-SBR output does not match input #61

Closed
dgm9704 opened this issue Sep 25, 2018 · 1 comment
Closed

FI-SBR output does not match input #61

dgm9704 opened this issue Sep 25, 2018 · 1 comment
Assignees
Labels

Comments

@dgm9704
Copy link
Owner

dgm9704 commented Sep 25, 2018

Some problem with matching namespaces/prefixes
input:
<xbrli:context id="Context_Instant_IntangibleRights"> <xbrli:entity> <xbrli:identifier scheme="http://www.xbrl.fi">1234567-1</xbrli:identifier> <xbrli:segment> <xbrldi:explicitMember dimension="fi-sbr-dim-D033:IntangibleAssetsBreakdownDimension">fi-sbr-dim-D033:IntangibleRights</xbrldi:explicitMember> </xbrli:segment> </xbrli:entity> <xbrli:period> <xbrli:instant>2013-12-31</xbrli:instant> </xbrli:period> </xbrli:context>
output:
<xbrli:context id="Context_Instant_IntangibleRights"> <xbrli:entity> <xbrli:identifier scheme="http://www.xbrl.fi">1234567-1</xbrli:identifier> <xbrli:segment> <xbrldi:explicitMember xmlns:q1="http://www.xbrl.fi/sbr/dimensions/D033/01-01-2013" dimension="q1:IntangibleAssetsBreakdownDimension">q1:IntangibleRights</xbrldi:explicitMember> </xbrli:segment> </xbrli:entity> <xbrli:period> <xbrli:instant>2013-12-31</xbrli:instant> </xbrli:period> </xbrli:context>

@dgm9704 dgm9704 added the bug label Sep 25, 2018
@dgm9704 dgm9704 self-assigned this Sep 25, 2018
@dgm9704 dgm9704 removed their assignment May 13, 2019
@dgm9704 dgm9704 self-assigned this Apr 5, 2020
@dgm9704
Copy link
Owner Author

dgm9704 commented Apr 5, 2020

Having looked at this again, I find that this is a non-issue at the moment. The example files available do not match the current specifications and were poorly constructed anyway. This issue is closed, if any further issues come to light with current and correct instances a new issue should be opened.

@dgm9704 dgm9704 closed this as completed Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant