Producing documents?

[csj]

Hello, at first glance this appears to be a fully-compliant XBRL reading and validating system, which is already very impressive.

Question: Can this library be used to produce XBRL documents? It seems not (unless I simply didn't find it); do you have plans to add this?
Question 2: Are there any specifications beyond the 2.1 spec that this library conforms to? (e.g. Inline XBRL, Dimensional validation, Table linkbase spec)?

[JeffFerguson]

Thank you for the kind words! Let me try to answer your questions.

Question: Can this library be used to produce XBRL documents? It seems not (unless I simply didn't find it); do you have plans to add this?
Gepsio does not do that today. Its current focus is to read XBRL.

My original thought when thinking about what Gepsio might do is that the point of machine-readable reports is -- well -- the readable aspect. I see quite a few tools which write XBRL, but not many that read, and reading is the point of machine-readable reports. Given that, I focused on that use case first.

With that said, Gepsio already has a robust object model used to surface the parsed and validated XBRL data, so classes are in place that could be used to populate objects that are then saved into a document with something like XbrlDocument.Save(). It's not out of the realm of possibility, since the object model is already in place, but it doesn't do that today.

The idea is interesting!

Question 2: Are there any specifications beyond the 2.1 spec that this library conforms to? (e.g. Inline XBRL, Dimensional validation, Table linkbase spec)?
Not today, but I have plans for that. My vision is to build ancillary .NET assemblies, like JeffFerguson.Gepsio.Formula and JeffFerguson.Gepsio.Dimensions, which take in an XbrlDocument instance read, validated, and populated by JeffFerguson.Gepsio and add its specific specification validations on top of that raw XBRL data from the XbrlDocument instance.

Thanks for taking a look at Gepsio!