XULE

Per XBRL US, the creator of XULE; XULE is described as, "an expression syntax that allows the querying of XBRL reports and taxonomies using a XULE processor". Again, per XBRL US, "XULE is syntax independent and will operate on XBRL reports published in JSON, iXBRL, CSV and XML formats.

XULE is free to download on GitHub.

XULE has a rules editor that works with Microsoft Visual Studio which can be downloaded here.

But XULE is really a family of things all of which run on Arelle, an open source XBRL processor, XBRL Dimensions processor, and XBRL Formula processor that is free to download and use:

  • XLUE - formula expressions; technical syntax to query and process XBRL taxonomies and instance documents.
  • XENDR - rendering of Inline XBRL instance documents; uses XULE syntax within an HTML template to define and create inline XBRL instance documents.
  • XINCE - XBRL instance creation; Uses XULE syntax to create instance documents.
  • XODEL - XBRL taxonomy creation; uses XULE syntax to create taxonomies.
XBRL US has a presentation on the XULE Family, a copy of which I have put here.  This graphic is from that presentation:
The XULE family above is a command line or programmer's tool.  Why? Well, because XULE works at the XBRL technical syntax level of objects.  This is part of another graphic from the above mentioned presentation.

But WHAT IF another layer was added to XULE?  WHAT IF a Standard Business Report Model (SBRM) layer was built into XULE.  WHAT IF the XBRL technically oriented objects completely abstracted away using the higher level logical conceptualization of SBRM for business reports.  WHAT IF XULE, or something like XULE, could work with the XBRL technical syntax, RDF+OWL+SHACL technical syntax, ISO global standard GQL, and maybe even the PROLOG technical syntax.

WHAT IF business report logical patterns was the fundamental grounding and not some individual technical syntax.  What if you could simply convert, bi directionally, between common technical syntaxes? WHAT IF SBRM's logical conceptualization was the center of the universe?

WHAT IF XULE, or something like XULE would implement this by directional transformation between technical syntax alternatives?

Additional Information:

Comments

Post a Comment

Popular posts from this blog

Relational Knowledge Graph System (RKGS)

Image
Relational Knowledge Graph System (RKGS) is an interesting idea that combines the relational paradigm and the knowledge graph paradigm.  This documentation, Why RKGS , explains the idea. This gets even more interesting with the notion of "relational AI".  RelationalAI is described as follows by the company of the same name, Relational.ai : “RelationalAI is a cloud-based relational knowledge graph management system, with state of the art probabilistic processing and declarative reasoning at scale to make developing Data Applications a superpower for your business.” This notion of knowledge graphs represented in relational databases fits into my belief that knowledge graphs have two aspects: the expression SYNTAX and the logic of what is expressed or SEMANTICS. While the LOGIC of a knowledge graph is always the same regardless of technical syntax used to express that logic; there are many, many different technical syntaxes that can be used to represent a knowledge graph. There
Read more

Graph Hairball

Image
Knowledge graph system logic, the "things" and "relations between things" that  graph theory calls "vertices" (a.k.a. nodes, points, entities, things) and "edges" (a.k.a.  links, lines, relations, associations), looks like a big graph hairball as some people call it an example of which you can see here: Why?  This common view of a graph is because there has to be some "general view" of the information provided by the graph.  This is just like a general view of the information within a relational database is a table ; a set of ROWS and COLUMNS for exactly one table at a time. So what is interesting is that with a graph database the default view is everything in the graph of knowledge.  Whereas the default view of everything in a relational database is one table at a time. Further, it does not really matter whether the information that populates your knowledge graph comes from, say, CSV files, Excel, JSON, XBRL, RDF, PROLOG or whateve
Read more

PLATINUM Business Use Cases, Test Cases, Conformance Suite

Image
A brick wall is made of exactly two things: bricks, mortar. But a brick wall created by a master craftsman, or mason, and a brick wall created by a “weekend warrior” with no knowledge of masonry will be very different. Master craftsmen are created and that process takes time and effort. This blog post is a first prototype that brings several things together into one useful resource for business professionals.  It pulls together the human readable information of the Showcase of Reports   and the machine readable information of the Conformance Suite of XBRL-based Financial Reports Prepared using the Seattle Method .  Then, I want to incorporate the information found in these PLATINUM XBRL-based Financial Report Examples . The three resources can be useful and used independently; but they are even more useful when used together.  Business professionals really could not care a less about the technical details of getting some result that they want.  But technical professionals need to under
Read more