Profile cover photo
Profile photo
Gepsio
11 followers -
XBRL Document Object Model for .NET
XBRL Document Object Model for .NET

11 followers
About
Gepsio's posts

Post has attachment
Public
Microsoft recently announced.NET Core 2.0 Preview 1 and, in keeping with the Gepsio development roadmap for 2017, work began to see how the Gepsio code base would survive the move from the .NET Framework to .NET Core. Good news and bad news came out of…

Post has attachment
Public
Microsoft has announced that the Codeplex site will be retired this year. This news does not affect Gepsio in any way. As noted in the original roadmap plan for Gepsio, as well as the March 2017 update to that plan, Gepsio will be moving from Codeplex to…

Post has attachment
Public
Microsoft has released Visual Studio 2017, which is the development environment used for Gepsio development. Gepsio’s development roadmap for 2017, published in December 2016 and outlined here, noted that Gepsio would be moving to .NET Standard 2.0 once…

Public
Working on Gepsio's support for decimal inference as documented in section 4.6.6 of the XBRL spec. This work will allow conformance test 322-01-bindcalculationdefaultdecimals-instance.xbrl to pass. One of the three facts in the tests lacks both a "decimals" attribute and a "precision" attribute and is being referenced in a calculation arc.

This statement in the spec was an interesting read:

"the inferred decimals is given by the following expression: precision - int(floor(log10(abs(number(item))))) - 1, where precision is the value of the @precision attribute, int( ) a function returning an integer of its argument, floor( ) a function returning the largest integer less than or equal to its argument, log10( ) a function returning the logarithm base 10 of its argument, abs( ) a function returning the absolute value of its argument, number( ) a function providing a numeric conversion if its argument is not internally numeric (as may be needed for the math computations), and item is the item's value (PSVI typed numeric node value if available, or otherwise inner text of numeric item node)."

Fortunately, that equation won't be tough to implement ... but it needs to put in the right place in the code! Now, where might that be .... ?

Post has attachment
Public
Gepsio Development Roadmap for 2017 #xbrl

Visual Studio 2017 and .NET Standard promise to bring exciting changes to .NET-based development efforts, and Gepsio will be taking full advantage of these changes. Gepsio’s cross-platform vision, as outlined here, is to make use of .NET Standard to bring…

Post has attachment
Public
Moving Gepsio Platform Support Forward with .NET Standard #xbrl

Gepsio currently supports several different versions of the .NET Framework, but it has long been a goal to support the code on a variety of platforms, including the Universal Windows Platform (UWP) and Xamarin. Microsoft is making strides in the…

Post has attachment
The last post discussed a future design whereby Gepsio would ship as two assemblies and that, as a result of this work, would no longer be able to support .NET 3.5. Never mind. MissingManifestResourceException Thrown In UWP Calls To PCL Resources Some…

Post has attachment
Gepsio‘s support for the Windows 10 Universal Windows Platform (UWP) will bring two changes to Gepsio that will be new to the platform: Gepsio will ship as two assemblies, rather than a single assembly. Gepsio will no longer be able to support .NET 3.5…

Post has attachment
Gepsio‘s support for the Windows 10 Universal Windows Platform (UWP) will bring two changes to Gepsio that will be new to the platform: Gepsio will ship as two assemblies, rather than a single assembly. Gepsio will no longer be able to support .NET 3.5…

Post has attachment
This email came into the Gepsio inbox recently: I’ve been playing around with the library. My first exercise for myself is trying to reconstruct the financial statements. I thought I’d group Facts by time periods. The ContextRefNames were not what I…
Wait while more posts are being loaded