Category Archives: Uncategorized


I’m trying to animate the iQ logo:


I’ve got this part down:



IR Basics

I’m relating what I learn here, to what I am applying to iQ. Here I’m reiterating some key terms; follows by a definition, an IR Book example, and an iQ example.

Python Docstrings 101

Good code is self-documenting code.

That’s why I’m getting into the habit of using Python Docstrings.

Here is a summary:

  • Where
    • First statement in module, function, class, or method (the “thing”) definition
  • Why
    • Becomes the __doc__ special attribute of the “thing” it’s documenting
  • What
    • Don’t document the “thing’s” name or “signature”; you can get that with introspection.
    • Do document the return value; you can’t get that with introspection.
  • How
    • Triple double quotes (can be r (raw) or u (unicode))
    • Prescription > description. Method’s effect, not only its result.
  • More


I’m working on a web app for craft breweries. The app will help them file information about their production to the US TTB (Alcohol and Tobacco Tax and Trade Bureau) Midway through I realized it’s a perfect opportunity for iXBRL. Continue reading

Don’t Be So Negative: XBRL Values (1/3)

Paul Warren recently revisited the popular discussion of negative values in XBRL . Many experts consider negative values the biggest quality/comparability issue in XBRL. If it’s that important, I want to chime in! This post is hopefully the first of a few on the subject. This post will focus on my experience in creating XBRL and the rationale I apply to the problem of “negative values”. Continue reading

Tagged , , , , , , , , , , , , , , ,

Postgres Queries: Learning More

The most sophisticated query I have used these major features:

    • To combine fields from separate tables, as if they’re in one table
  • ON
    • The property or attribute that is the hinge for a JOIN
    • The conditions that must be met for the new one table
    • To select only a subset of results

I’m checking a query discussed in an XBRL US Webinar, it includes other functions. Let’s learn more about these… : Continue reading

Conflict Minerals, Part II: Missing Data

Note: This article has been published at Hitachi Data Interactive, a fantastic review of current topics in XBRL. Check it out, here:

I recently posted about the new Form SD, where I asked a few questions about the structure of the XBRL taxonomy.

Since posting, I analyzed the instance document more closely. I also had a lively chat with the XBRL-Public Discussion group. The conversation was originally about tuples. The “Lines” of data reported (as seen in the picture below), had clear patterns; They need a Payment amount, a Project, a Country, etc. Some members, including myself, thought this was “tuple”-like.

Michelle from the Bank of Italy enlightened me as to why tuple structure is generally avoided in XBRL; the nesting of data allows taxonomy authors to create new meaning, or create the same meaning in a different way, (or hide meaning!); this wouldn’t be standard, so it wouldn’t be  understood, and that’s bad.

But the tuple discussion was a tangent; I focused the second part of the conversation on missing data.  Continue reading

Conflict Minerals in the Congo!

Note: This article has been referenced at Hitachi Data Interactive, a fantastic review of current topics in XBRL. Check it out, here:

As Phil MennonaCharlie HoffmanCompliance Week, and the SEC themselves noted; the SEC has come out with a new  (XBRL) Taxonomy. The Taxonomy is for Form SD. This Form is a disclosure of certain Blood Diamond Conflict Mineral* information… and I have a few brief observations. Continue reading

JQuery: Do Something!

I’m dabbling in jQuery for a simple interface: “Pick a company.” My latest app interface does exactly that; the user can pick from a list of publicly filed companies. Eventually we’ll get to the XBRL!

To pick a company… Continue reading

Part Three: The Results

In part one, I framed the business question. In part two, I described the query. A query on its own may not make sense, so in a later post I’ll be sure to discuss the “Tables”, (it might be called “Schema”?) That is, the way XBRL US Arranges their data.**

For now I’ll discuss the results, because this is really the answer to Phil’s original question; find those filers who report a “backwards calculation.” Here are the result of the query; these filers report calculationArc from us-gaap_ProfitLoss to us-gaap_NetIncomeLoss… Continue reading