Comments (7)
I’ll take a look at this and get back to you!
from xoxo.
Hi!
Bad news I'm afraid.
The way the library is built, means that handling additional attributes
in the same way as the normal ones is not supported.
The main reason is (there are others also):
Any facts with the same metric, context, value, unit and decimals
are considered "identical" as per the taxonomy (and DPM)
Additional attributes would/could create facts that are duplicate
in that way, but different in a way that would require them both to be
represented in a file.
This would be true eg. for facts that are modeled in more than table
in a given entrypoint (module).
That report file could then violate the taxonomy, Filing Rules,
or some other validation.
There is a possible work-around however:
That is to create your report normally, but instead of writing it to file,
you would call Instance.ToXmlDocument(), manipulate the returned XmlDocument
by adding any necessary attributes, and finally writing that XmlDocument
to file.
Having said all this, I confess I am very curious:
I handle lots of XBRL files coming and going in my day job, also those
that are based on the EBA DPM, and I haven't seen any need for additional
attributes for facts in succesful reporting.
EBA releases different test and reference instances for each DPM/taxonomy version.
I vaguely remember that they did put out some files that still had some of their
internal modeling data still "attached" by mistake.
(And afterwards released the corrected files without this extra info)
Now, please don't take offense, but could it be that you might be working
with those incorrect test files, and trying to reproduce them?
If that is the case then simply downloading the newest test files
would perhaps help you or clarify the issue?
If not, then I will gladly try to figure a way around this problem.
from xoxo.
Hi,
Despite my 10 years in banking industry I'm totally new to XBRL.
You are totally right. I started experimenting with XBRL for EBA reports and took the XBRL samples some 3 months ago. Following your suggestion, I just downloaded them again and it now contains a readme file with errata containing the text "Originally provided instance files mistakenly contained model:table, model:x, model:y, model:z etc attributes on fact values.". The new samples do not contain these attributes anymore.
Glad that this can be categorized as a non-issue. Thanks a lot for pointing me in the right direction!
Kind regards,
Bart.
from xoxo.
I'm glad I could help, I know first hand that there is a somewhat steep learning curve to XBRL. Please feel free to ask if there are any other problems, either with the library, or even XBRL reporting in general.
from xoxo.
from xoxo.
Hello.
Could you provide the actual error message if there is one? You can leave out any information that is private of course.
What you could try is to serialize the same Instance that gives the error with .ToFile and see what that produces. If that works as it should then the problem would be in the ToXmlDocument or related code.
from xoxo.
from xoxo.
Related Issues (20)
- Allow string formatting of reported differences for data points etc.
- Fails to parse ExplicitMember with whitespace in value HOT 8
- Unit.Measure should be XmlQualifiedName instead of string HOT 1
- No support for Inline XBRL HOT 1
- No way to validate inline xbrl HOT 1
- Drop support for .NET Framework 4.5.2 HOT 1
- [Question] how to add an explicit member with namespace specified HOT 5
- Support for XBRL-CSV HOT 4
- Unused namespace 'xbrldi' for instance with no explicit or typed members
- ScenarioComparisonMessage has extra set of parentheses HOT 1
- Bug with namespaces used in the value field of a segment explicit member HOT 3
- Use System.Text.Json instead of string handling
- xBRL-JSON support HOT 1
- Missing conversion from xBRL-JSON to xBRL-XML
- No API documentation
- ESEF validations don't belong in the library
- Xml/Fact Equals does not consider contextRef HOT 3
- Xml/Report FromXml does not provide an overload for additional parameters. HOT 4
- Context comparison throws in certain cases when one Scenario is null
- Option to disable 'instance-generator' declaration HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from xoxo.