Gepsio Released

A NuGet package for Gepsio is now available here. Release notes for this version are available here. This release includes support for reference linkbases and automatic support for several new industry standard taxonomies, including schemas from IFRS and US-GAAP.

The last three releases have been published on a monthly basis. Version was released at the beginning of June, version was released at the beginning of July, and this new version at the beginning of August. This cadence brings smaller changes with each release but puts changes in the hands of users more frequently.



Adding Local Search Support For Schemas With Invalid URLs

The discussion threads on a previous post, as well as the discussion attached to a GitHub issue, speak to the fact that Gepsio cannot find facts for XBRL instances that use the Dutch taxonomy. There are a couple of issues here, so this post will discuss the issue as well as an idea that will allow Gepsio to mitigate one of the issues.

A Gepsio user recently wrote to the project and said that they were in possession of an XBRL instance that was successfully parsed by Gepsio but was devoid of facts. The XBRL instance started out as follows:

<?xml version="1.0" encoding="UTF-8"?>
<xbrli:xbrl xmlns:xbrli="" xmlns="" xmlns:dst="" xmlns:cmn="" xmlns:sob="" xmlns:link="" xmlns:iso4217="" xmlns:xsi="" xmlns:ref="" xmlns:xh11d="" xmlns:arr="" xmlns:ixt="" xmlns:lnk="" xmlns:xbrldt="" xmlns:basis="" xmlns:ifrs="" xmlns:ix="" xmlns:xhtml="" xmlns:mrv="" xmlns:xl="" xmlns:fsa="" xmlns:xbrldi="" xmlns:gsd="" xmlns:xs="" xmlns:xlink="">
   <lnk:schemaRef xlink:href="" xlink:type="simple"/>

There is an issue right away, because that schema reference specifies an invalid URL. There is no document, XML schema or otherwise, at the address of What happens here is that Gepsio loads the document, finds the schema reference, and attempts to load the schema. Since the schema load fails, it logs a validation error and continues on as best it can. Since no schemas are loaded, no element definitions are loaded, and Gepsio can find no facts.

The first question is, “Why does this document reference a taxonomy with an invalid URL?” The answer that came back was this:

But the issue is that there will never be a hosted taxonomy in denmark, since they have chosen to not take the responsibility thereof.

OK, then. Apparently, the URLs for Dutch taxonomies are placeholders, and they are meant to be available locally, in the same location as the XBRL instance.

Gepsio is being modified to assist with this issue. If Gepsio attempts to resolve a schema reference, and gets the equivalent of an HTTP 404 back from the request to retrieve the schema, then Gepsio will look for the schema in the same folder as the XBRL instance which contains the schema reference.

Next Release to Support Automatic Loading of Industry Standard Schemas

Currently, Gepsio parses an XBRL instance and automatically loads any schemas referenced by a <schemaRef> element. The facts in the XBRL instance are then automatically validated against the loaded schemas. However, Gepsio does not automatically load any industry-standard schemas not explicitly referenced by the <schemaRef> element. Since XBRL instances do not typically make an explicit reference to industry-standard schemas (nor should they), facts that reference those schemas cannot be validated.

Consider, for example, the XBRL instance at It contains one <schemaRef> element so that a linkbase can be loaded. However, the facts in this instance reference namespaces such as and Since there is no schema reference for those namespaces, the facts that use those namespaces fail validation. The trick, though, is that those namespaces reference well-known industry standard namespaces that identify well-known schemas with schema source at well-known locations across the Internet.

The next version of Gepsio will add support for these well-known namespaces and will automatically load schemas referenced by the XBRL instance’s <xbrl xmlns:...> syntax even though the schema locations for the schemas are not explicitly referenced by a <schemaRef> element in the instance. Doing this will allow the facts in the instance using those namespaces to validate with full schema fidelity.

As of this writing, Gepsio supports the following industry-standard schemas:

  • Document Information and Entity Information 2009
  • US-GAAP 2009

Support for many other industry-standard schemas will be added as testing continues. The important note is that the code now has the infrastructure in place to support this notion, and support for other industry-standard schemas can be added relatively easily, and in one place, now that the infrastructure is available.

This change is in the develop branch in GitHub. The changes are available in this commit and will be available in the next update to Gepsio’s NuGet package.

Gepsio Repository Now Available on GitHub

The Gepsio code base has a new home on GitHub! The latest code base, built for .NET Standard 2.0, is available at Feel free to clone it and take a look!

Please keep in mind that the Gepsio Git repo is in preview. The solution in the repo is based on .NET Standard 2.0 and requires Visual Studio 2017 Preview 15.3.0 Preview 3.0 or higher, as well as .NET Core 2.0 Preview 2 or higher, to build. If you need code compatible with the current shipping production releases of Visual Studio 2017 and the full .NET Framework, please see Gepsio’s legacy Codeplex repository.

Gepsio and .NET Core 2.0 Preview 2

Microsoft recently announced .NET Core 2.0 Preview 2 and, in keeping with the Gepsio development roadmap for 2017, work continued to see how the Gepsio code base would survive the move from the .NET Framework to .NET Core. A previous blog post discussed this same work with .NET Core 2.0 Preview 1.

Spoiler alert.

The unit tests in the .NET Standard-based Gepsio solution have been updated to use the latest available version of the XBRL Conformance Suite (XBRL-CONF-2014-12-10). The solution builds a .NET Standard 2.0 build of Gepsio and a .NET Core 2.0 build of the unit tests, and the tests run to the same point at which the older .NET Framework build of Gepsio runs. The tests seem to run a bit more slowly than they do in the .NET Framework, but, since .NET Standard 2.0 is in preview mode, it can be assumed that some performance tuning has yet to be done.

This is fantastic news! Gepsio is on its way to being able to provide services to a variety of Windows and non-Windows platforms, extending its reach beyond .NET to a variety of operating systems and device platforms.

Next Steps

After doing some final cleanup, the .NET Standard-base Gepsio solution will be moved up to GitHub. A separate blog post will be created when the new repo is ready. The older .NET Framework-based Gepsio solution will remain on Codeplex.

It is important to note that the solution that will be posted to GitHub is based on .NET Standard 2.0 and requires Visual Studio 2017 Preview 15.3.0 Preview 3.0 or higher, as well as .NET Core 2.0 Preview 2 or higher, to build. If you need code compatible with the current shipping production releases of Visual Studio and the .NET Framework, continue to reference Gepsio’s existing Codeplex repository.