XBRLWiki - User contributions [en]

Licencia revocada

2025-02-25T16:15:17Z

Ihr:

= SI SU LICENCIA YA NO ES VÁLIDA, DEBE DE SOLICITAR UNA NUEVA LICENCIA =

- Si la licencia la ha obtenido a través de un tercero, (Regulador, Superintendencia y organismo similar) solicite de nuevo la licencia por el método indicado por ese organismo.

- Si lo que desea es solicitar una licencia para el diligenciamiento de informes a la Superintendencia de Sociedades, debe descargar la herramienta de licenciamiento de Superintendencia de Sociedades de Colombia en el siguiente link:

https://www.supersociedades.gov.co/documents/80312/333846/Licenciador-SDS-PRD.zip

- Si lo que desea es solicitar una licencia para el reporte de información a la Superintendencia de Servicios Públicos, puede consultar en la siguiente dirección como descargar el software y solicitar la licencia:

https://sui.superservicios.gov.co/Normas-de-Informacion-Financiera-y-Lenguaje-de-Informacion-XBRL?tab=manuales-nif-xbrl

- Si la licencia la obtuvo directamente a través de Reporting Estándar, por favor, envíenos un correo a soporte at reportingstandard.com

= Navegación =
[[Main Page]]

Licencia revocada

2025-02-24T13:09:46Z

Ihr:

= Causa del error =

Este mensaje indica que tu licencia ha sido desactivada en nuestros sistemas.

= Solución del problema =

- Si tu licencia ha sido obtenida a través de un tercero (una Superintendencia, otro Regulador o un organismo similar) pruebe a volver a solicitar la licencia usando el mecanismo indicado por el tercero. Durante los periodos en los que los que se renuevan los contratos de licencias también cambian las listas de supervisados a los que se conceden las licencias, por ello nosotros desactivamos las licencias que no están en el nuevo listado o que han sido obtenidas antes del nuevo periodo de renovación.

- Si tu licencia ha sido obtenida directamente a Reporting Estándar S.L. envíanos un email a info en reportingstandard.com para que lo revisemos.

= Navegación =
[[Main Page]]

Licencia revocada

2025-02-24T13:04:14Z

Ihr:

Este mensaje indica que tu licencia ha sido desactivada en nuestros sistemas.

- Si tu licencia ha sido obtenida a través de un tercero (una Superintendencia, otro Regulador o un organismo similar) pruebe a volver a solicitar la licencia usando el mecanismo indicado por el tercero. Durante los periodos en los que los que se renuevan los contratos de licencias también cambian las listas de supervisados a los que se conceden las licencias, por ello nosotros desactivamos las licencias que no están en el nuevo listado o que han sido obtenidas antes del nuevo periodo de renovación.

- Si tu licencia ha sido obtenida directamente a Reporting Estándar S.L. envíanos un email a info en reportingstandard.com para que lo revisemos.

Licencia revocada

2025-02-24T13:01:44Z

Ihr: Created page with "Este mensaje indica que tu licencia ha sido desactivada. - Si tu licencia ha sido obtenida a través de un tercero (una Superintendencia, otro Regulador o un organismo similar) pruebe a volver a solicitar la licencia usando el mecanismo indicado por el tercero. - Si tu licencia ha sido obtenida directamente a Reporting Estándar S.L. envíanos un email a info en reportingstandard.com para que lo revisemos."

Este mensaje indica que tu licencia ha sido desactivada.

- Si tu licencia ha sido obtenida a través de un tercero (una Superintendencia, otro Regulador o un organismo similar) pruebe a volver a solicitar la licencia usando el mecanismo indicado por el tercero.

- Si tu licencia ha sido obtenida directamente a Reporting Estándar S.L. envíanos un email a info en reportingstandard.com para que lo revisemos.

XBRL Template File

2018-10-27T11:03:40Z

Ihr:

==Description==

The XBRL Template file is an XML file that defines events in order to let drivers to capture data that will be used for the generation of a new XBRL report.

The namespace definition of elements in the XBRL Template file is '''<nowiki>http://www.reportingstandard.com/map/3</nowiki>'''

The official location for the schema that corresponds to the indicated namespace is '''<nowiki>http://www.reportingstandard.com/schemas/mapper/mapper-2011.xsd</nowiki>'''

==Sample file==

<source lang="xml">
<?xml version="1.0" encoding="UTF-8"?>

<xbrlMap
xmlns="http://www.reportingstandard.com/map/3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.reportingstandard.com/map/1 http://www.reportingstandard.com/schemas/mapper/mapper-2011.xsd"
xmlns:xbrli="http://www.xbrl.org/2003/instance"
xmlns:xbrldi="http://xbrl.org/2006/xbrldi">


<datasources>
<source id="source0" class="com.ihr.xbrl.mapper.source.StaticSource"/>
</datasources>


<instance>

<dts>
<file>taxonomy.xsd</file>
</dts>

<contexts>
<scheme>http://www.xbrl.org/companyName</scheme>
<company>The Sample Company Name</company>


<context id="ctx0i">
<entity>
<xbrli:identifier scheme="_">_</xbrli:identifier>
</entity>
<period>
<instant>eoy-P1Y</instant>
</period>
</xbrli:context>


<context id="ctx0d">
<entity>
<xbrli:identifier scheme="_">_</xbrli:identifier>
</entity>
<period>
<startDate>boy-P1Y</startDate>
<endDate>eoy-P1Y</endDate>
</period>
</context>
</contexts>


<units>
<xbrli:unit id="EUR">
<xbrli:measure xmlns:iso4217="http://www.xbrl.org/2003/iso4217">iso4217:EUR</xbrli:measure>
</xbrli:unit>
</units>


<facts xmlns:tx="http://taxonomy.com/example">

<item sourceRef="source0" contextRef="ctx0i" mapIdentifier="identifier0" concept="tx:A" unitRef="EUR"/>
<item sourceRef="source0" contextRef="ctx0d" mapIdentifier="identifier1" concept="tx:B" multi="Single" unitRef="EUR"/>

<tuple concept="tx:U">
<item sourceRef="source0" contextRef="ctx0d" mapIdentifier="identifier2" concept="tx:C" multi="1"/>
<item sourceRef="source0" contextRef="ctx0d" mapIdentifier="identifier3" concept="tx:D" multi="Single"/>
<item sourceRef="source0" contextRef="ctx0d" mapIdentifier="identifier4" concept="tx:E" multi="All" unitRef="EUR"/>
</tuple>
</facts>
</instance>
</xbrlMap>

</source>

==Elements==

The root element is '''xbrlMap'''

The content of the xbrlMap element is divided in two sections.

* Definition of data sources
* Event definitions and associated metadata

Both sections are required in a mapping file and that must occurs only once

===Definition of data sources===

Data sources are defined using '''source''' elements as children of the '''datasources''' element.

The '''source''' element is an empty element that has three attributes:
* Required ''id'' attribute. Used by '''item''' and '''tuple''' events (see next section Definition of Events) in order to identify the data source they are linked with.
* Required ''class'' attribute. Used to indicate the driver class. The driver class must be instantiated at runtime (in a dll or in the classpath) and must implement the interface defined in [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/mapper/source/XBRLDataSource.html the XBRLDataSource interface].
* Optional ''config'' attribute. Used to point to a file with configuration information for the driver indicated in the ''class'' attribute. The content may be a URI relative to the URI of the XBRL Template File and it is resolved using ''xml:base'' if it is indicated in the '''source''' element or any of it ancestors.

A sample datasources section where two data sources are defined. One is a web form, the other is a connection to a database that requires a configuration file called SQLMapperDriverConfig.xml and is located in the same folder as the XBRL Template file:
<source lang="xml">
<datasources>
<source id="form" class="com.ihr.xbrl.mapper.source.WebFormDataSource"/>
<source id="sql" class="com.ihr.xbrl.mapper.source.SQLDataSource" config="SQLMapperDriverConfig.xml"/>
</datasources>
</source>

===Definition of events===

The '''xbrlMap''' root element must have an '''instance''' element that in turn contains four sub-sections:
* The definition of the instance DTS
* The definition of the contexts templates
* The definition of the units
* The definition of the facts (Here is where the real events are defined. The previous three sections are just meta-data in order to facilitate the definition of the events)

====The instance DTS====

The instance DTS defines the schemas and linkbases that will be included in the new XBRL report in '''link:schemaRef''' and '''link:linkbaseRef''' elements. In the template file it is not required distinguishing between linkbase files and schema files. Both will be documented as simple files. The API will detect the file type and will include the required elements in the final XBRL report automatically.

The first child of the instance element must be a '''dts''' element that, in turn, contains an unlimited number of '''file''' elements each one of them indicating a relative or absolute file that will be included in the instance document during instance document generation phase. It is strongly recommended using official absolute file names of taxonomy or linkbase files in order to produce XBRL reports than can be opened everywhere. If you believe this is against performance, you may know that mapping external files on the Internet to local files is supported by almost all serious XBRL software vendors. Reporting Standard S.L. has implemented this feature using the [[XBRL Catalog]] and providing user friendly tools in order to help maintaining the local taxonomy catalog.

This is a sample '''dts''' section definition for the IFRS taxonomy:
<source lang="xml">
<dts>
<file>http://xbrl.iasb.org/taxonomy/2009-04-01/ifrs/ias_1_2009-04-01/cal_ias_1_2009-04-01_role-210000.xml</file>
<file>http://xbrl.iasb.org/taxonomy/2009-04-01/ifrs/label/lab_ifrs-en_2009-04-01.xml</file>
<file>http://xbrl.iasb.org/taxonomy/2009-04-01/ifrs/ias_1_2009-04-01/pre_ias_1_2009-04-01_role-210000.xml</file>
<file>http://xbrl.iasb.org/taxonomy/2009-04-01/ifrs/ias_1_2009-04-01/def_ias_1_2009-04-01_role-210000.xml</file>
</dts>
</source>
Note that this example is not including the IFRS taxonomy schema. This is not an error. The required schema will be added automatically by the tool in order to produce a valid XBRL report during the document creation phase.

====Contexts templates====

The '''contexts''' (in plural) element is a container for context templates. Context templates looks like xbrl contexts but most of the elements are in the namespace defined in the mapper schema rather than the XBRL namespace.

The content of some parts of the context container can be parameterized in order make them dynamic. The dynamic content will be calculated at the time the report is generated. The calculated value will be used in the resulting document in the part that corresponds according to the template.

Context templates may have dimensions in the segment and scenario containers.

This is a very simple example of contexts inside the template file:
<source lang="xml">
<contexts>
<scheme>http://www.xbrl.org/companyName</scheme>
<company>The Sample Company Name</company>


<context id="ctx0i">
<entity>
<xbrli:identifier scheme="_">_</xbrli:identifier>
</entity>
<period>
<instant>eoy-P1Y</instant>
</period>
</xbrli:context>


<context id="ctx0d">
<entity>
<xbrli:identifier scheme="_">_</xbrli:identifier>
</entity>
<period>
<startDate>boy-P1Y</startDate>
<endDate>eoy-P1Y</endDate>
</period>
</context>
</contexts>
</source>

The first two elements of the contexts element are '''scheme''' and '''company'''. The value of those elements is any string value for company and a valid URI value for the scheme element. The values indicated here will be used in order to substitute the content of the XBRL identifiers in the real contexts. When the value of the scheme attribute in the identifier elements is an underscore character '''"_"''', the mapper processor will substitute the underscore character by the value indicated in the scheme element. When the processor find an underscore character are the value of the identifier element, it will be substituted by the value of the company element.

The dates on '''instant''', '''startDate''' and '''endDate''' elements in the context can also be parameterized. The valid values are:
* a date; in this case it is not parameterized, it is just a fixed date, or
* the token "boy" (Beginning Of the Year) optionally followed by a + or - sign and the declaration of a period using XML Schema notation. "boy" will be dynamically substituted by the date of the beginning of the current year, or
* the token "eoy" (End Of the Year) optionally followed by a + or - sign and the declaration of a period using XML Schema notation. "eoy" will be dynamically substituted by the last date of the current year, or
* the token "now" that indicates current date.

Each context here must have a context id that will be referenced from '''item''' elements declaring item generation events.

====Units====

The next part of the instance template document after the contexts element is the '''units''' (in plural) element. This element wraps all units used by item data events.

The content of the units elements are xbrl units as they appear in XBRL reports.

This is an example of a units element with content:
<source lang="xml">
<units>
<xbrli:unit id="Euros">
<xbrli:measure xmlns:iso4217="http://www.xbrl.org/2003/iso4217">iso4217:EUR</xbrli:measure>
</xbrli:unit>
</units>
</source>

Units must have an id that will be referenced from item data events.

====Events====

Linking all together; the most important part of the instance template document are the events. Events are defined in order to obtain data from drivers and according to the [[Mapper to driver data exchange dialog|mapper to driver data exchange dialog]]. The '''facts''' element wraps the content of all events defined in an XBRL Template File.

The following piece of XML code is the declaration of an event in order to obtain data for an item fact. All required information for the event definition is stored in attributes. Part of the information is required and other parts are optional.
<source lang="xml">
<item sourceRef="source0" contextRef="ctx0i" mapIdentifier="identifier0" concept="tx:A" unitRef="Euros"/>
</source>

The attributes defined in a fact item data capturing event are:
* required ''sourceRef'', this attribute content must match with the id of the '''source''' to be informed about the event.
* required ''contextRef'', this attribute content must match with the id of one of the contexts defined in the '''contexts''' section.
* required ''mapIdentifier'', this attribute holds the event name and will be used by drivers. See the [[Mapper to driver data exchange dialog|mapper to driver data exchange dialog]] wiki page for more information.
* required ''concept'', this attribute hold the concept QName this item refers to. The concept must be defined in a taxonomy schema that is part of the DTS declared in the DTS section.
* optional ''unitRef'', this attribute content must match with the id of one of the units defined in the '''units''' section. The attribute is optional because non numeric concepts does not require units. If the used does not add this optional attribute in a numeric fact then the driver would be responsible of adding a unit. If the driver does not add a unit then the produced instance document may not be valid
* optional ''multi'', this attribute defines the behavior of the engine generating the report when the driver returns more than one value for this event and the element is inside a tuple. Possible values are "All", "Single", "Prev" or an integer. See the [[Mapper to driver data exchange dialog|mapper to driver data exchange dialog]] wiki page for more information.

The following piece of XML code is the declaration of a sample event in order to obtain data for a tuple fact.
<source lang="xml">
<tuple concept="tx:T">
... here goes the tuple specific events; they are other item events or tuple events. Events can be nested in order to represent tuple structures in the instance document ...
</tuple>
</source>

The declaration of events in order to populate content for tuples contains the following attributes:
* required ''concept'', this attribute holds the concept QName this tuple refers to. The concept must be defined in a taxonomy schema that is part of the DTS declared in the DTS section.
* optional ''mapIdentifier'', this attribute holds the event name and will be used by drivers. Due to the reason that tuple content are items or other tuples, the mapIdentifier here is optional. If there is no mapIdentifier attribute declared none of the drivers will be informed about the event for generating a tuple, one instantiation of the tuple will be created automatically in order to populate the tuple content.
* optional ''multi'', this attribute defines the behavior of the engine generating the report when there is a nested tuple inside a parent tuple and there are more than one fact tuples to be created in the report. See the [[Mapper to driver data exchange dialog|mapper to driver data exchange dialog]] wiki page for more information.
* optional ''sourceRef'', if the attribute exist its content must match with the id of the '''source''' to be informed about the event. If the attribute exists, the driver will be responsible of calculating the number of fact tuples that the final instance document will contain. See the [[Mapper to driver data exchange dialog|mapper to driver data exchange dialog]] wiki page for more information.

An event is declared and named using the ''mapIdentifier'' attribute in either a '''tuple''' or an '''item''' element. The content of that attribute is a string that identifies the event name. Other GUI tools and drivers will use the content of the mapIdentifier attribute in order to match it with the function that obtains values from the data source.

Sample content of a facts element:
<source lang="xml">
<facts xmlns:tx="http://taxonomy.com/example">


<item sourceRef="source0" contextRef="ctx0i" mapIdentifier="identifier0" concept="tx:A" unitRef="Euros"/>


<tuple concept="tx:T">
<tuple concept="tx:T">
<item sourceRef="source0" contextRef="ctx0i" mapIdentifier="identifier1" concept="tx:B" multi="Single" unitRef="Euros"/>
<item sourceRef="source0" contextRef="ctx0dim" mapIdentifier="identifier3" concept="tx:C" multi="2" unitRef="Euros"/>
</tuple>
<item sourceRef="source0" contextRef="ctx0i" mapIdentifier="identifier1" concept="tx:B" multi="All" unitRef="Euros"/>
</tuple>


<tuple concept="tx:U">
<item sourceRef="source0" contextRef="ctx0i" mapIdentifier="identifier2" concept="tx:B" multi="1" unitRef="Euros"/>
</tuple>


<item sourceRef="source0" contextRef="ctx0dim" mapIdentifier="identifier3" concept="tx:C" unitRef="Euros"/>
</facts>
</source>
==Navigation==
[[Main Page]] | [[XBRLmapper]]

Software requirements

2018-10-09T09:09:12Z

Ihr:

Reporting Standard S.L. software requirements for desktop installation are as follows:

Make sure your computer meet the [http://www.reportingstandard.com/wiki/index.php/Hardware_requirements minimum hardware requirements] too

WARNING: Java 9, Java 10 or Java 11 are not supported Java versions as they are not backwards compatible with Java 8.

==Version 3.1.0 ==
This version is under development now
* Our XBRL API at the bottom of all tools supports Java from version 1.7 at this time (May 2017) we announce we plan to update to Java 1.8 in our core API due to external dependencies of new features that are only implemented in Java 1.8 so it is recommended for all our clients to migrate to Java 1.8

==Version 3.0.6 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010, 2013 or 2016 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.8 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.5 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.7 or 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.4 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 or 1.7 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.3 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 or 1.7 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.1 and up to version 2.8.2 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-us/download/details.aspx?id=44074 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.7.4 and up to version 2.7.7 ==

* Operating system can be Windows (XP SP3, Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 or 2010 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-US/download/details.aspx?id=42513 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.7.3==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 or 2010 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-US/download/details.aspx?id=42513 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.6.12==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 (only if you want to install the Excel Add In for Mapper and the Excel Formulas)
* Office 2007 Interop Assemblies. Can be downloaded from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513 Microsoft Downloads Web Site]. This is required only for the Excel Add In.
* .NET framework 3.5 only on windows platform and when the Excel Add In is installed.

==Version 2.6.11==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 (only if you want to install the Excel Add In for Mapper and the Excel Formulas)
* Office 2007 Interop Assemblies. Can be downloaded from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513 Microsoft Downloads Web Site]. This is required only for the Excel Add In.
* .NET framework 3.5 only on windows platform and when the Excel Add In is installed.

==Navigate==
[[Main Page]]

File:Esta licencia no funcionara en este computador renovar.jpg

2018-04-06T21:54:04Z

Ihr:

Esta licencia no funcionará en este computador

2018-04-06T21:51:45Z

Ihr: /* Solución del problema */

= Causa del error =

Se está intentando usar un archivo de licencia en un computador distinto al computador desde el que se solicitó la licencia

= Solución del problema =

Vuelva a solicitar la licencia desde el computador donde va a hacer la instalación del software

Puede usar el botón de Renovar Licencia aquí:

[[File:Esta licencia no funcionara en este computador renovar.jpg]]

= Navegación =
[[Main Page]]

File:Esta licencia no funcionará en este computador renovar.jpg

2018-04-06T20:58:23Z

Ihr: Ihr uploaded File:Esta licencia no funcionará en este computador renovar.jpg

Mensaje de error cuando la licencia no corresponde con el computador

File:XBRLizerIFRSInstance.png

2017-12-13T09:57:06Z

Ihr: Ihr uploaded File:XBRLizerIFRSInstance.png

File:OpenDataForMapping.png

2017-12-13T09:55:53Z

Ihr: Ihr uploaded File:OpenDataForMapping.png

File:OpenIFRS2009SampleInstance.png

2017-12-13T09:54:46Z

Ihr: Ihr uploaded File:OpenIFRS2009SampleInstance.png

Relational database data source driver

2017-09-20T16:50:38Z

Ihr:

==Description==

The Relational Database Source Driver is a configurable generic driver to obtain data from relational databases (tables) and create XBRL reports inside the automatization framework provided by the XBRL Mapper engine designed by Reporting Standard.

==Editors==

There are currently no specific editors designed for the Relational Database Source Driver configuration files. They are XML files than can be created using standard XML editors.

==Configuration file==

The configuration file is provided during the driver declaration inside the instance document template file. See [[XBRL Template File#Definition_of_data_sources]] for more information. The driver class is '''com.ihr.xbrl.mapper.source.SQLDataSource'''

Sample SQL Driver data source declaration:

<source lang="xml">
<datasources>
<source
id="source0"
class="com.ihr.xbrl.mapper.source.SQLDataSource"
config="SQL-driver-config.xml"/>
</datasources>
</source>

The configuration file must be valid according to the XML Schema that has the following namespace <nowiki>http://www.reportingstandard.com/source/driver/SQLDriver-2009</nowiki> and that is published in the following official location <nowiki>http://www.reportingstandard.com/schemas/source/XBRLDataSourceSQL-2009.xsd</nowiki>

Sample configuration file:
<source lang="xml">

<XBRLDataSourceSQL xmlns="http://www.reportingstandard.com/source/driver/SQLDriver-2009" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.reportingstandard.com/source/driver/SQLDriver-2009 http://www.reportingstandard.com/schemas/source/XBRLDataSourceSQL-2009.xsd">
<connection id="con0">
<url>jdbc:mysql://localhost:3306/testdb</url>
<user>root</user>
<password>xbrl</password>
</connection>
<data connRef="con0">
<precision>INF</precision>
<table>GovernmentGrantsDisclosuresMasterTuple</table>
<field identifier="ifrs-gp_GovernmentGrantsDisclosures" name="GovernmentGrantsDisclosures" />
<field identifier="ifrs-gp_DetailOfGovernmentGrants" name="DetailOfGovernmentGrants" />
<field identifier="ifrs-gp_AmountOfGovernmentGrantsNettedAgainstReportedExpenses" name="AmountOfGovernmentGrantsNettedAgainstReportedExpenses" />
<where>fiscalCode = '12345'</where>
</data>
<data connRef="con0">
<decimals>0</decimals>
<table>GovernmentGrantsDisclosuresDetailsTuple</table>
<field identifier="ifrs-gp_DescriptionOfGovernmentGrant" name="DescriptionOfGovernmentGrant"/>
<field identifier="ifrs-gp_AmountOfGovernmentGrantRecognised" name="AmountOfGovernmentGrantRecognised"/>
<field identifier="ifrs-gp_ExplanationOfUnfulfilledConditionsAndOtherContingenciesAttachingToGovernmentAssistance" name="ExplanationOfUnfulfilledConditions"/>
<where>fiscalCode = '12345'</where>
</data>
<data connRef="con0">
<decimals>INF</decimals>
<table>GovernmentGrantsDisclosuresAmounts</table>
<field identifier="GovermentGrantTuple" name="rut"/>
<where>fiscalCode = '12345'</where>
</data>
<data connRef="con0">
<decimals>INF</decimals>
<table>GeneralData</table>
<statement>
select
row_id as id,
companyname,
substring(companyid from 1 to length(companyid)-2) as compid,
from GeneralData
where row_id = ${MY_ROW_ID}
</statement>
<field identifier="regulator-gp_CompanyName" name="companyname"/>
<field identifier="regulator-fiscalCode" name="compid"/>
</data>
</XBRLDataSourceSQL>
</source>

Each '''data''' element above defines a select statement to the database in order to retrieve information that may be relevant to create an XBRL report. Each '''data''' element has a '''connRef''' attribute that identify the database connection parameters.

The content of a '''data''' element is first either a '''decimals''' or a '''precision''' element that will be relevant for all numeric fields obtained by this select statement.

The next element is a '''table''' element that contains the SQL table o view name used to build the select statement.

After the '''table''' element there may be a '''statement''' element (this is optional) if present, the content of the statement element will replace the select statement that the driver creates for you automatically using the table name and selected fields.

Following the '''statement''' element there is a sequence of one or unlimited number of '''field''' elements. A field element maps a table field with a generation identifier name. The field name is indicated in the '''name''' attribute and the event generation identifier name is indicated in the '''identifier''' attribute.

Other optional attributes on the '''field''' element are:
* The '''count''' attribute. This attribute, if present, contains a select statement in order to allow the driver detect how many times there is data available for the field when creating facts in the instance document.
* The '''keys''' attribute. This attribute, if present, contains a sequence of keys that will be used to obtain the values for the elements returned in the '''count''' attribute. The existence of the '''keys''' attribute requires a '''keyRef''' attribute on a '''data''' element that will be executed for each key returned in the '''keys''' attribute.

Optionally, there may exist one '''where''' element that contains the text of a where clause that will be added to the end of the select statement.

=== Parameters ===
From the API, it is possible to send parameters to the SQL statements using a Properties object as a parameter to the map method. The following code adds a parameter that is later replaced in the SQL statements:

<source lang="java">
// uConfig is the URI of the configuration file
MapEngine me = new MapEngine(uConfig);

Properties props = new Properties();
props.setProperty("SELECTED_RECORD", idSelectedRecord);
Object parameters[] = { props };

// Generamos el informe XBRL
XBRLInstance instance = me.map(parameters);
</source>

The text '''${SELECTED_RECORD}''' will be replaced by the value of the '''idSelectedRecord''' variable.

<source lang="xml">
<data connRef="con0">
<decimals>INF</decimals>
<table>GovernmentGrantsDisclosuresAmounts</table>
<field identifier="GovermentGrantTuple" name="rut"/>
<where>fiscalCode = ${SELECTED_RECORD}</where>
</data>
</source>

===When the statement is executed===

In the [[Mapper to driver data exchange dialog]], during the 2<sup>nd</sup> question, the mapper asks the driver about how may fact items for a specific mapping event are in the data source (using the identifier as the key). At this time, if the query has not been executed before, it is executed now (and the result is cached during the live of the execution of the XBRL report).

==Navigation==
[[Main Page]] | [[XBRLmapper]]

Hardware requirements

2017-05-18T08:38:57Z

Ihr:

Reporting Standard S.L. software requirements for desktop installation are as follows:

==Version 3.1.0 ==
This version is under development

* We plan to remove the support of windows 32 bits from this version onwards

==Version 3.0.6 x64 (64 bits version) ==

* Minimum 8 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 3.0.6 x86 (32 bits version) ==
* Minimum 4 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.8.5 x64 (64 bits version) ==

* Minimum 8 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.8.5 x86 (32 bits version) ==
* Minimum 4 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.8.4 x64 (64 bits version) ==

* Minimum 8 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.8.4 x86 (32 bits version) ==
* Minimum 4 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.8.3 x64 (64 bits version) ==

* Minimum 8 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.8.3 x86 (32 bits version) ==
* Minimum 4 Gb of RAM.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.8.1 and up to Version 2.8.2 ==

* Minimum 3 Gb of RAM. We recommend 4 Gb of RAM on 32 bit operating systems and 8Gb on 64 bit operating systems.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.7.4 and up to Version 2.7.7 ==

* Minimum 2 Gb of RAM. We recommend 4 Gb of RAM on 32 bit operating systems and 8Gb on 64 bit operating systems.
* CPU 1.6 GHz Dual Core (minimum). The maximum CPU speed, the better performance you get.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.7.3==

* Minimum 2 Gb of RAM. We recommend 4 Gb of RAM on 32 bit operating systems and 8Gb on 64 bit operating systems.
* CPU 1.6 GHz Dual Core.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1080 or greater.
* 1 Gb of Hard Drive space

==Version 2.6.12==

* Minimum 2 Gb of RAM. We recommend 4 Gb of RAM.
* CPU 1.6 GHz Dual Core recommended.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1200 or greater.
* 1 Gb of Hard Drive space

==Version 2.6.11==

* Minimum 1 Gb of RAM. We recommend 4 Gb of RAM.
* CPU 1.6 GHz Dual Core recommended.
* Monitor 1024 x 768 minimum resolution. We recommend a resolution of 1600x1200 or greater.
* 200 Mb of Hard Drive space

==Navigate==
[[Main Page]]

Software requirements

2017-05-18T08:34:51Z

Ihr:

Reporting Standard S.L. software requirements for desktop installation are as follows:

Make sure your computer meet the [http://www.reportingstandard.com/wiki/index.php/Hardware_requirements minimum hardware requirements] too

==Version 3.1.0 ==
This version is under development now
* Our XBRL API at the bottom of all tools supports Java from version 1.7 at this time (May 2017) we announce we plan to update to Java 1.8 in our core API due to external dependencies of new features that are only implemented in Java 1.8 so it is recommended for all our clients to migrate to Java 1.8

==Version 3.0.6 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010, 2013 or 2016 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.8 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.5 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.7 or 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.4 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 or 1.7 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.3 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 or 1.7 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.1 and up to version 2.8.2 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-us/download/details.aspx?id=44074 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.7.4 and up to version 2.7.7 ==

* Operating system can be Windows (XP SP3, Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 or 2010 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-US/download/details.aspx?id=42513 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.7.3==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 or 2010 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-US/download/details.aspx?id=42513 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.6.12==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 (only if you want to install the Excel Add In for Mapper and the Excel Formulas)
* Office 2007 Interop Assemblies. Can be downloaded from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513 Microsoft Downloads Web Site]. This is required only for the Excel Add In.
* .NET framework 3.5 only on windows platform and when the Excel Add In is installed.

==Version 2.6.11==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 (only if you want to install the Excel Add In for Mapper and the Excel Formulas)
* Office 2007 Interop Assemblies. Can be downloaded from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513 Microsoft Downloads Web Site]. This is required only for the Excel Add In.
* .NET framework 3.5 only on windows platform and when the Excel Add In is installed.

==Navigate==
[[Main Page]]

Software requirements

2017-05-18T08:30:39Z

Ihr:

Reporting Standard S.L. software requirements for desktop installation are as follows:

Make sure your computer meet the [http://www.reportingstandard.com/wiki/index.php/Hardware_requirements minimum hardware requirements] too

==Version 3.0.6 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010, 2013 or 2016 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.8 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.5 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.7 or 1.8 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.4 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 or 1.7 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.3 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 or 1.7 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [https://www.microsoft.com/en-us/download/details.aspx?id=48217 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.8.1 and up to version 2.8.2 ==

* Operating system can be Windows (Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits, Windows 8 or 8.1 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007, 2010 or 2013 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-us/download/details.aspx?id=44074 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.7.4 and up to version 2.7.7 ==

* Operating system can be Windows (XP SP3, Windows Server 2003 SP2, Windows Server 2008 SP2, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 or 2010 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-US/download/details.aspx?id=42513 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.7.3==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 or 2010 (only if you want to install the Excel Add In for Mapper and the Excel Formulas). This works only under windows.
* .NET framework 4.0 Client Profile only on windows platform and when the Excel Add Ins are installed. From [http://www.microsoft.com/download/en/details.aspx?id=24872 Microsoft Web Site].
* VSTO 4.0 Runtime. (Microsoft Visual Studio 2010 Tools for Office Runtime) This is for Office 2007 and 2010. Can be downloaded from [http://www.microsoft.com/en-US/download/details.aspx?id=42513 Microsoft Web Site]. This is required for all Excel Add ins including Taxonomy Editor and XBRL Mapper. This works under windows platforms only and MUST be installed after .NET framework 4.0 Client profile is installed.

==Version 2.6.12==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 (only if you want to install the Excel Add In for Mapper and the Excel Formulas)
* Office 2007 Interop Assemblies. Can be downloaded from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513 Microsoft Downloads Web Site]. This is required only for the Excel Add In.
* .NET framework 3.5 only on windows platform and when the Excel Add In is installed.

==Version 2.6.11==

* Operating system can be Windows (XP SP3, Vista or Windows 7, 32 or 64 bits) or Unix (any kind of Linux, MacOSX etc).
* Java 1.6 installed. It is '''not''' required that the Java virtual machine be the one from SUN (Oracle)
* Office 2007 (only if you want to install the Excel Add In for Mapper and the Excel Formulas)
* Office 2007 Interop Assemblies. Can be downloaded from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513 Microsoft Downloads Web Site]. This is required only for the Excel Add In.
* .NET framework 3.5 only on windows platform and when the Excel Add In is installed.

==Navigate==
[[Main Page]]

Main Page

2016-10-13T09:06:50Z

Ihr:

===Reporting Standadrd XBRL WIKI.===

This WIKI web site is organized in the following sections:

* Reporting Standard S.L. - Product specific discussions, including new feature requests
** Products WITH user interface
*** [[XBRLview]]
*** [[XBRLvalid]]
*** [[XBRLizer]]
*** [[XBRLmapper]]
*** [[Taxonomy Builder]]
*** [[TeamTax]]
** Components without user interface
*** [[XBRL API related discussions]]
*** [[XBRL Database]]
*** [[XBRL Validation Service]]
*** [[XBRL Storage Service]]
*** [[XhBtRmL]]
*** [[XBRLmapper as a service]]
** Other products and components
*** [[Excel XBRL functions library]]

=== Requirements ===

* Requirements
** [[Software requirements]]
** [[Hardware requirements]]

=== Installation ===
* Installation
** [[Installation on Windows]]
** [[Installation on UNIX (Linux, Solaris, AIX, Mac OS X)]]

=== Configuration ===
* [[Taxonomy Catalogs Overview]]
** [[Reporting Standard Taxonomy Catalog]]
** [[XBRL International Taxonomy Packages]]
** [[Oasis Taxonomy Catalogs]]
** [[Custom Taxonomy Catalogs such as Reporting Standard XBRL Database]]

==== Other optional installation steps ====

* [[Installing the XBRL Database]]

=== Useful links and frequently asked questions (FAQ) ===

# [[Where is the license file stored and how can I backup it?]]
# [[The XBRL Taxonomy Catalog]]
# [[java.security.SignatureException: invalid encoding for signature]]
# [[java.security.SignatureException: invalid encoding for signature (Español)]]
# [[This license will not work on this computer]]
# [[Esta licencia no funcionará en este computador]]
# [[Adding taxonomies to the ZIP Catalog]]
# [[Walkthrough downloading Reporting Standard XBRL tools set]]
# [[Walkthrough requesting evaluation license]]
# [[Walkthrough load and store XBRL taxonomies]]
# [[Detailed explanation about Excel mapping process from XBRLizer]]
# [http://www.supersociedades.gov.co/servicios/software-para-el-diligenciamiento/Paginas/NIIF-Videos-de-CapacitaciOn.aspx Vídeos respecto a la instalación y funcionamiento de las herramientas de licenciamiento XBRL para la Superintendencia de Sociedades de Colombia]

=== Other unrelated ===
* XBRL Specifications and related discussions
** [[XBRL 2.1]]
*** [[Comments about the Call for review the proposed edit recommendation made on 2011/05/27]]
** [[XDT 1.0 Dimensions Specification]]
** [[XQuery Formula Specification (Minimun XML based and more XQuery based)]]

Main Page

2016-09-18T23:09:36Z

Ihr: Reverted edits by MediaWiki default (talk) to last revision by Ihr

===Reporting Standadrd XBRL WIKI.===

This WIKI web site is organized in the following sections:

* XBRL Specifications and related discussions
** [[XBRL 2.1]]
*** [[Comments about the Call for review the proposed edit recommendation made on 2011/05/27]]
** [[XDT 1.0 Dimensions Specification]]
** [[XQuery Formula Specification (Minimun XML based and more XQuery based)]]

* Reporting Standard S.L. - Product specific discussions, including new feature requests
** Products WITH user interface
*** [[XBRLview]]
*** [[XBRLvalid]]
*** [[XBRLizer]]
*** [[XBRLmapper]]
*** [[Taxonomy Builder]]
*** [[TeamTax]]
** Components without user interface
*** [[XBRL API related discussions]]
*** [[XBRL Database]]
*** [[XBRL Validation Service]]
*** [[XBRL Storage Service]]
*** [[XhBtRmL]]
*** [[XBRLmapper as a service]]
** Other products and components
*** [[Excel XBRL functions library]]

=== Requirements ===

* Requirements
** [[Software requirements]]
** [[Hardware requirements]]

=== Installation ===
* Installation
** [[Installation on Windows]]
** [[Installation on UNIX (Linux, Solaris, AIX, Mac OS X)]]

=== Configuration ===
* [[Taxonomy Catalogs Overview]]
** [[Reporting Standard Taxonomy Catalog]]
** [[XBRL International Taxonomy Packages]]
** [[Oasis Taxonomy Catalogs]]
** [[Custom Taxonomy Catalogs such as Reporting Standard XBRL Database]]

==== Other optional installation steps ====

* [[Installing the XBRL Database]]

=== Useful links and frequently asked questions (FAQ) ===

# [[Where is the license file stored and how can I backup it?]]
# [[The XBRL Taxonomy Catalog]]
# [[java.security.SignatureException: invalid encoding for signature]]
# [[java.security.SignatureException: invalid encoding for signature (Español)]]
# [[This license will not work on this computer]]
# [[Esta licencia no funcionará en este computador]]
# [[Adding taxonomies to the ZIP Catalog]]
# [[Walkthrough downloading Reporting Standard XBRL tools set]]
# [[Walkthrough requesting evaluation license]]
# [[Walkthrough load and store XBRL taxonomies]]
# [[Detailed explanation about Excel mapping process from XBRLizer]]
# [http://www.supersociedades.gov.co/servicios/software-para-el-diligenciamiento/Paginas/NIIF-Videos-de-CapacitaciOn.aspx Vídeos respecto a la instalación y funcionamiento de las herramientas de licenciamiento XBRL para la Superintendencia de Sociedades de Colombia]

XBRLProcessorFactoryBase

2016-08-12T09:50:44Z

Ihr: Created page with '== The XBRLProcessorFactoryBase abstract class wiki page== This abstract class provides a minimum implementation of the XBRLPlugInProcessor interface and let the extending c…'

== The XBRLProcessorFactoryBase abstract class wiki page==

This abstract class provides a minimum implementation of the [[XBRLPlugInProcessor]] interface and let the extending class to provide code for the following 3 methods.
* public XBRLPlugInProcessor create()
* public String getProcessorDescription()
* public String getProcessorName()

===The create() method===

Shall create a new instance of the validation class this class is the factory for. The base class contains a protected field with the DTSContainer instance

===The getProcessorDescription() method===

Shall return the processor description string. Normally this method just calls a static method in the validation class that also returns the processor description

===The getProcessorName() method===

Shall return the processor name that is a unique name used to distinguish every processor than can be referenced in the [http://reportingstandard.com/apidoc/com/ihr/xbrl/om/DTSContainer.html#PROCESSORS_SEQUENCE PROCESSORS_SEQUENCE] property

Download the [http://www.reportingstandard.com/samples.jar samples and demo] file and review its source code available inside for examples

==Navigation==
[[XBRL API related discussions]]

XBRLProcessorFactory

2016-08-12T09:39:08Z

Ihr: Created page with '== The XBRLProcessorFactory interface wiki page== This interface describes the methods that are required in order for a DTSContainer to create a new instance of a specific […'

== The XBRLProcessorFactory interface wiki page==

This interface describes the methods that are required in order for a [[DTSContainer]] to create a new instance of a specific [[XBRLPlugInProcessor]] class.

Visit the [http://reportingstandard.com/apidoc/com/ihr/xbrl/om/XBRLProcessorFactory.html XBRLProcessorFactory API page] for technical details

All existing validation engines contains a factory class implementing this interface. The implementation of the interface requires the class to add code to obtain information about the validation add-in such as processor name and processor description and if the processor is hidden to the user interface or will be visible for configuration.

There is an abstract class [http://reportingstandard.com/apidoc/com/ihr/xbrl/om/XBRLProcessorFactoryBase.html XBRLProcessorFactoryBase] that provides minimum implementation of the interface and requires extending classes to implement the method:
* public XBRLPlugInProcessor create()
* public String getProcessorDescription()
* public String getProcessorName()

Download the [http://www.reportingstandard.com/samples.jar samples and demo] file and review its source code available inside for examples

==Navigation==
[[XBRL API related discussions]]

XBRLPlugInProcessor

2016-08-12T09:27:57Z

Ihr:

== The XBRLPlugInProcessor interface wiki page==

This interface describes the methods that are available in a validation engine.

Visit the [http://reportingstandard.com/apidoc/com/ihr/xbrl/om/XBRLPlugInProcessor.html XBRLPlugInProcessor API page] for technical details

All existing validation engines implements this interface. The implementation of the interface requires the class to add code to the validate() and validate(XBRLDocument document) method. That code must return an instance of a new XBRLValidationReport containing the details of the validation process including new inconsistencies and errors detected.

There is a super interface of this interface called [http://reportingstandard.com/apidoc/com/ihr/xbrl/om/XBRLCompilableProcessor.html XBRLCompilableProcessor] that adds up two methods to the XBRLPlugInProcessor. They are used when the validator requires to pre-process resources in XBRL linkbases in order to create internal structures that will be used during the validation phase. This is the case of the Formula Processor, Table processor and other that perform static validation of resources in the taxonomy and pre-compile XPath expressions to perform accelerated validation.

==Navigation==
[[XBRL API related discussions]]

The basis of all validation engines

2016-08-12T09:27:03Z

Ihr:

==The basis of Reporting Standard S.L. validation engines==

===What's a validation engine===

A validation engine is a java class that implements the [[XBRLPlugInProcessor]] interface and performs validation of an XBRL report or XBRL Taxonomy by executing code and utilizing the XBRL object model from the RS API. All existing processors already works the same way. All them implements the [[XBRLPlugInProcessor]] interface and executes code looking for error conditions as indicated in the XBRL Specifications.

Validation engines are created by the API when they are needed during the validation process. The validation process is driven internally by the [[DTSContainer]] class.

In order for the [[DTSContainer]] class to create a validator instance, validation factories must be registered.

===What's a validation engine factory===

A validation engine factory is a java class implementing the [[XBRLProcessorFactory]] interface (or extending the [[XBRLProcessorFactoryBase]] abstract class) that is able to create an instance of the a validation engine when it is needed to validate a specific DTSContainer instance.

During the API initialization phase, all factories of validation engines are "discovered" in the java classpath using this technique:

# The entire classpath (all jars in the classpath) are examined looking for a directory called RSXBRLMANIFEST and a file in that directory called xbrlprocessors.properties.
# When a file with that information is found, a property with name processor-factories is obtained.
# That property value must be a comma separated list of class names implementing the [[XBRLProcessorFactory]] interface.
# An instance of the factory class is created with no arguments constructor and the method getProcessorName() is called over the new factory instance.
# Then, the factory class is registered inside the static part of the DTSContainer and the new processor name is available to be used in the validation chain.

===What's the validation chain===

A validation chain is the content of the [http://reportingstandard.com/apidoc/com/ihr/xbrl/om/DTSContainer.html#PROCESSORS_SEQUENCE PROCESSORS_SEQUENCE] property that is passed in to the creation of the [[DTSContainer]]

This property can be used to manipulate the chain of processors that will handle XBRL Validation.

In order to use custom processors during XBRL Validation phase they must satisfy the following requirements:

# a processor factory must be registered with a unique name
# the processor name must be added to the PROCESSORS_SEQUENCE property
# during a call to the validate() method, the processor can creare new errors and inconsistencies and add them to the validation report

==Navigation==
[[XBRL API related discussions]]

XBRLPlugInProcessor

2016-08-12T09:22:45Z

Ihr: Created page with '== The XBRLPlugInProcessor interface wiki page== This interface describes the methods that are available in a validation engine. Visit the [http://reportingstandard.com/apidoc/…'

The basis of all validation engines

2016-08-12T09:12:03Z

Ihr: Created page with '==The basis of Reporting Standard S.L. validation engines== ===What's a validation engine=== A validation engine is a java class that implements the XBRLPlugInProcessor int…'

XBRL API related discussions

2016-08-12T08:32:55Z

Ihr: /* Objects overview */

==XBRL 2.1 Reporting Standard API==

===Product page===

[[http://www.reportingstandard.com/XBRL_API.xhtml XBRL API product page]]

===Descripcion===

The XBRL API is an object model created on top of the XBRL Specification. The XBRL API has been designed to facilitate the development of user friendly applications or applications that works with XBRL information without having to worry about the complexities of the XBRL syntax and related specifications like XML Schema, XLINK, XPointer etc. Using the XBRL API the user interact with the content of a DTS (XBRL Reports and related metadata in taxonomies and linkbases) using just objects and methods defined in the objects.

Current version of the XBRL API is 2.6.7 and there is ongoing work on version 2.6.8. Changes in the API occurs from time to time in order to add new functionality or reimplement things in order to accelerate execution. The public part of the API is stable and has not suffered any changes in the last year or so.

All Tools from Reporting Standard have been build using Reporting Standard XBRL API.

The API provides access to several components from other libraries like XML Schema aware XPath processing from Saxonica XML processor (License included in Reporting Standard license) or Storage capabilities in relational databases.

===Quick start guide===

This section is a walkthrough describing the required steps in order to start using Reporting Standard XBRL API in your own code. The section is divided in two sub sections; one for Java and another one for .NET development environments

====Java====

The Java version requires Java 1.6 installed and 4Gb of RAM are recommended 2Gb of RAM minimun. A single CPU processor of 1.4 Ghz is minimun but, in order to be able to handle large taxonomies a dual CPU at GHz or more is recommended.

# Download the latest version of Reporting Standard tools from the [http://www.reportingstandard.com/downloads.xhtml downloads page]
# Install the tools on your computer
# Install the license files in the lib folder as indicated in the documentation
# Create a new Java project and add the following jar libraries to it:
## The XBRL API in the '''xbrljlib-2.0.jar''' file
## The dependencies are: '''jdom.jar''', '''commons-logging-1.0.4.jar''', '''log4j-1.2.11.jar''', '''saxon9ee.jar''', '''saxon9-jdom.jar''' and '''resolver.jar'''
## Reporting Standard license file ('''XBRLlicense.lic''') MUST be available in the classpath of the JVM
# Take a look at the section describing the environment variables in order to understand how they can be configured in your organization
# Start coding

====.NET====

# Download the latest version of Reporting Standard tools from the [http://www.reportingstandard.com/downloads.xhtml downloads page]
# Install the tools on your computer
# Install the license files in the lib folder as indicated in the documentation
# Download the .NET version of the libraries (ask support at reportingstandard dot com for the download URL)
# Read the section about the environment variables and set them according to your settings. Note there is no Classpath in .NET so the XBRLLIBRARYPATH environment variable is of high importance in .NET environments.
# Create a new project in, for example, Visual Basic .NET
# add references to the following DLL files: '''xbrljlib-2.0.dll''', '''IKVM.OpenJDK.Core.dll''', '''IKVM.OpenJDK.Util.dll''', '''IKVM.OpenJDK.XML.API.dll''', '''IKVM.OpenJDK.XML:Parse.dll''', '''IKVM.AWT.WinForms.dll''' and '''IKVM.Runtime.dll'''
# Please note, other DLLs may be required depending on the application you are using. All of them are in the same directory.
# Start coding

===Architecture===

The API is organized in logical layers. The lowest layer is considered the syntactical layer of the XML files that are the source of the information. One intermediate layer is the object model that represents the DTS content after resolving relationship prohibitions. A higher layer on top of the previous layer is the output of the XBRL validation rules that operated with the input of the previous later. Each one of the layers are able to detect XBRL errors or errors related to the specific layer, for example, the XML parser will detect and raise errors found on the syntax of the XML files. The XML Schema validation layer will raise XML Schema errors and so on. Information can flow between the layers, for example when you load a DTS from files, the information flows from bottom to top, but when you create an XBRL report programatically and later you call de <tt>save</tt> method, the information flows from top bottom layers.

===Environment Variables and Java Variables ===

Reporting Standard XBRL API can be configured using environment variables and Java Variables in order to set the location of common components such as the license file and taxonomy catalog files. The following environment variables and java variables are recognized by the XBRL API:

* '''XBRLCATALOGPATH''' This environment variable points to a ; separated list of directories where files with the name '''XBRLCatalog.xml''' exist. Those files must be according to the OASIS XML Catalog syntax convention. For this reason, it is recommended (but not required) that they reference the Catalog.xsd schema. The variable has effect in Windows and Unix, Java and .NET environments. The Windows installer already sets the environment variable and the right value pointing to the directory where the installer has installed the Taxonomy Catalog.

* '''XBRLRSHOME''' This environment variable points to a directory that will be used as the home directory where Reporting Standard applications store user properties that are used to share information across multiple applications (like the information to connect to the XBRL Repository). The Windows installer does not set this environment variable and the API defaults to the user's home directory. The value is used in Windows and Unix, Java and .NET environments.

* '''xbrl.rs.home''' If this java system property exist, it shall point to a directory that will be used instead of the '''XBRLRSHOME''' enviroment variable.

* '''XBRLLIBRARYPATH''' This environment variable points to the directory where Reporting Standard libraries are installed on the system.

Note: the next directory after the directory pointed to by this variables must have a fixed name '''ReportingStandardXBRLTools'''.

There is more information about how the API obtains the path for a user file on the [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/util/RSStaticAndUser.html RSStaticAndUser java class documentation]

===Objects overview===

The starting point for almost anything you want to do with Reporting Standard API requires the creation of a DTSContainer object. See the [[http://www.reportingstandard.com/apidoc/com/ihr/xbrl/om/DTSContainer.html DTSContainer javadoc page]] this object will be used for loading a DTS or for creating a new DTS from scratch, performing XBRL validation, etc.

* [[DTSContainer]] wiki page

XBRL Document related objects

* [[XBRLTaxonomy]] wiki page

* [[XBRLLinkbase]] wiki page

* [[XBRLInstance]] wiki page

Simple API Services

* XBRL 2.1 validation [[XBRLCoreProcessor]]

* XBRL Dimensions processor [[XDTProcessor]]

* XBRL Formulas processor [[XBRLFormulaProcessor]]

* XBRL UTR (Universal Type Registry) processor [[XBRLUTR]]

* XBRL Edgar (US SEC Validator) [[EDGAR Validator]]

* Traversing networks of relationships [[DTSExplorer]]

* Exploring the content of XBRL reports [[InstanceExplorer]]

* Getting concept labels [[LabelsProvider]]

* Getting available languages [[LangsProvider]]

Extending the validation engine

* [[The basis of all validation engines]]

* [[XBRLPlugInProcessor]] wiki page

* [[XBRLProcessorFactory]] interface wiki page

* [[XBRLProcessorFactoryBase]] abstract class that implements the [[XBRLProcessorFactory]] interface

=== Related documentation===

[[http://www.xbrl.org/Specification/Infoset/PWD-2009-02-04/infoset-PWD-2009-02-04.html The XBRL Infoset Specification document]] Created by Reporting Standard S.L.

==Navigation==
[[Main Page]]

File:Esta licencia no funcionará en este computador renovar.jpg

2016-08-11T09:07:43Z

Ihr: uploaded a new version of "File:Esta licencia no funcionará en este computador renovar.jpg"

Mensaje de error cuando la licencia no corresponde con el computador

File:Esta licencia no funcionará en este computador renovar.jpg

2016-08-11T09:04:08Z

Ihr: uploaded a new version of "File:Esta licencia no funcionará en este computador renovar.jpg"

Mensaje de error cuando la licencia no corresponde con el computador

Esta licencia no funcionará en este computador

2016-08-11T09:02:42Z

Ihr: /* Solución del problema */

= Causa del error =

Se está intentando usar un archivo de licencia en un computador distinto al computador desde el que se solicitó la licencia

= Solución del problema =

Vuelva a solicitar la licencia desde el computador donde va a hacer la instalación del software

Puede usar el botón de Renovar Licencia aquí:

[[File:Esta licencia no funcionará en este computador renovar.jpg]]

= Navegación =
[[Main Page]]

File:Esta licencia no funcionará en este computador renovar.jpg

2016-08-11T08:57:37Z

Ihr: Mensaje de error cuando la licencia no corresponde con el computador

Mensaje de error cuando la licencia no corresponde con el computador

XBRL 2.1

2016-06-08T12:13:06Z

Ihr: /* Horrible mistakes */

==XBRL 2.1==

This wiki page is for notes about the use of the XBRL 2.1 specification. We will document here things like best practices, ideas hints in order to properly use XBRL 2.1

The HTML version of the XBRL 2.1 specification is here http://www.xbrl.org/Specification/XBRL-RECOMMENDATION-2003-12-31+Corrected-Errata-2008-07-02.htm

==Marvellous things about XBRL 2.1==

This section describes functionality that is included in the XBRL 2.1 specification and really facilitates the modelling of business concepts into XBRL 2.1 concepts

===Tuples===

Tuples groups things together. This is the main purpose of a tuple in the XBRL 2.1 specification and also in the XML Schema specification from the W3C. A Tuple represent the construction of a concept that requires other concepts in order to make it meaningful.

The tipical example of a tuple is a '''person'''. In our example, a person is composed by a '''name''' and a '''surname'''. So it is very clear and simple to understand that a '''person''' can be defined as a group of a '''name''' and a '''surname'''.

===Dimensions===

Dimensions was created by Ignacio Hernández-Ros (founder of Reporting Standard S.L.) in order to fill a gaap in the deifinition of concept properties and validation rules of concept properties.

A concept property is, for example, the type of a telephone number (fax, voice, ...). Properties can be defined using special XBRL Concept definitions called '''dimensions''' and possible dimension values can also be defined using XBRL and XML syntactical artifacts like hypercubes, members etc.

A property adds two things to a concept definition:
* The existence of the property for that concept
* A property value for a fact item of that concept in a report

===Common errors about tuples and dimensions===

Some taxonomies worldwide (and regulators) are trying to force the use of just one of the technologies (dimensions) against the other (tuples). In our experience this is just because of the personality of the decision makers and the lack of technical knowledge (of the decision makers) in order to make proper decisions. The decisions has come into a very complex modelling scenario in which companies has to create dimensions and taxonomy extensions for things that naturally are beter modelled using a tuple.

In our experience, a taxonomy can use both, Tuples and Dimensions together, in order to achieve the better quality in modelling techniques around XBRL. Some taxonomies like Australia SBR are already following this modelling technique and more will follow in the future.

All Reporting Standard XBRL products are open to use ALL possibilities that exist in the XBRL 2.1 specifications. Tuples and Dimensions because we believe the current situation in the USA (only dimensions) is not a sustainable model for the future as the rest of the world is not following them and the XBRL specifications are more open in their functionality.

==Horrible mistakes==

In this section we will document real bad practices that, unfortunatelly, are also real practices.

===Replacing officially published taxonomy files===

This is, for sure, one of the most horrible things an XBRL user can ever imagine. A regulator is changing the validation rules whenever he likes, without any notice, any information, any documentation and any possibility for the users to catch-up the changes. But it is true in the case of some regulators this is how they work... They update their taxonomy files without telling anything to anybody, without changing the official namespaces and without changing the official document locations... Reporting Standard is not going to tell you who is doing this we are going to limit ourselves to document the implications of this decisions:

* '''No validation is possible anylonger'''. An instance document that WAS valid against a previous version of the taxonomy MAY NOT be valid against a new version of the taxonomy.
* '''Taxonomy validation rules lose trustability'''. An instance document that WAS invalid against a previous version of the taxonomy MAY be valid against a new version of the taxonomy.
* '''The regulator cannot demonstrate it is performing well'''. Because a document that cannot be validated at any moment in time does not guarantee it was valid at the submission time by the regulated entity either.
* '''Unauditability of the changes'''. Because the regulator insist on not changing the official taxonomy URLs and the namespaces used in the taxonomies, the changes in the taxonomies are not auditable and not trackable by computers or humans. The process is completely out of control.
* '''The worst thing a regulator can do today is become less transparent'''. In fact, this is adding stoppers to the process building the history of the reporting suply chain and it is suspicious that some regulators are doing this things these days. (Not transparent regulators)

===Role URIs with spaces===

Some software vendors (at this time Fujitsu is one of them) allows to create role URIs with spaces. They are not legal in the raw XML data type and causes problems in any other processor different from Fujitsu processor. Please VALIDATE your taxonomies with more than one taxonomy validation engine and DO NOT JUST TRUST ONE and never trust a validation engine that is not properly performing XML Schema validation.

==Navigate==
[[Main Page]]

Main Page

2016-06-07T19:06:44Z

Ihr: /* Useful links and frequently asked questions (FAQ) */

Custom Taxonomy Catalogs such as Reporting Standard XBRL Database

2016-02-22T14:32:53Z

Ihr: Created page with '== Custom Taxonomy Catalogs such as Reporting Standard XBRL Database == On top of all taxonomy Catalogs and catalog formats, Reporting Standard maintains a global database with …'

== Custom Taxonomy Catalogs such as Reporting Standard XBRL Database ==

On top of all taxonomy Catalogs and catalog formats, Reporting Standard maintains a global database with copies to commonly used taxonomy packages. The database is available over the Internet and Reporting Standard XBRL Tools connects regularly to update the list of taxonomies.

You can access the list of taxonomies available from the GUI and you can install and uninstall taxonomies from the global database. If you have subscribed to a taxonomy packages and we update the taxonomy in the global repository, your copy will be updated automatically next time the tools are started with Internet connection available.

Note: the update is only available if your license is covered by the maintenance period, you can extend the maintenance period updating your license file and purchasing a maintenance period extension.

= References =
[[XBRL Catalog]]<br/>
[[Adding taxonomies to the ZIP Catlog]]<br/>
[[Select Taxonomy From Catalog]]<br/>

= Feedback =
Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]

=Navigate=
[[Main Page]]

XBRL International Taxonomy Packages

2016-02-22T13:15:22Z

Ihr: Created page with '== XBRL International Taxonomy Packages == This taxonomy catalog is under development by XBRL International. Reporting Standard has already implemented the candidate recommendat…'

== XBRL International Taxonomy Packages ==

This taxonomy catalog is under development by XBRL International. Reporting Standard has already implemented the candidate recommendations and proposed recommendation but the final recommendation is still work in progress.

The XBRL International taxonomy catalog is more or less similar to Reporting Standard ZIP catalog. The main important contribution of this new format is the capability to document DTS entry points in a human readable form and multi language.

= References =
[[XBRL Catalog]]<br/>
[[Adding taxonomies to the ZIP Catlog]]<br/>
[[Select Taxonomy From Catalog]]<br/>

= Feedback =
Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]

=Navigate=
[[Main Page]]

Oasis Taxonomy Catalogs

2016-02-22T13:11:44Z

Ihr:

== Oasis Taxonomy Catalog ==

This taxonomy catalog is based on Oasis XML Catalogs. The configuration of a taxonomy catalog based on Oasis catalogs is materialized in a file with the fixed name "XBRLCatalog.xml"

For more information visit the [[The XBRL Taxonomy Catalog]] page and follow links to the Oasis catalogs.

Reporting Standard XBRL Tools contains a GUI to edit the Oasis taxonomy catalog.

= References =
[[XBRL Catalog]]<br/>
[[Adding taxonomies to the ZIP Catlog]]<br/>
[[Select Taxonomy From Catalog]]<br/>

= Feedback =
Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]

=Navigate=
[[Main Page]]

Oasis Taxonomy Catalogs

2016-02-22T13:10:27Z

Ihr: Created page with '== Oasis Taxonomy Catalog == This taxonomy catalog is based on Oasis XML Catalogs. The configuration of a taxonomy catalog based on Oasis catalogs is materialized in a file with…'

== Oasis Taxonomy Catalog ==

This taxonomy catalog is based on Oasis XML Catalogs. The configuration of a taxonomy catalog based on Oasis catalogs is materialized in a file with the fixed name "XBRLCatalog.xml"

For more information visit the [[XBRL Catalog]] page and follow links to the Oasis catalogs.

Reporting Standard XBRL Tools contains a GUI to edit the Oasis taxonomy catalog.

= References =
[[XBRL Catalog]]<br/>
[[Adding taxonomies to the ZIP Catlog]]<br/>
[[Select Taxonomy From Catalog]]<br/>

= Feedback =
Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]

=Navigate=
[[Main Page]]

Reporting Standard Taxonomy Catalog

2016-02-22T13:06:37Z

Ihr:

== Reporting Standard Taxonomy Catalog ==

This taxonomy catalog is based on ZIP files. It was first created back in year 2009.

For more information use the links in the References section

= References =
[[XBRL Catalog]]<br/>
[[Adding taxonomies to the ZIP Catlog]]<br/>
[[Select Taxonomy From Catalog]]<br/>

= Feedback =
Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]

=Navigate=
[[Main Page]]

Reporting Standard Taxonomy Catalog

2016-02-22T13:05:37Z

Ihr: Created page with '== Reporting Standard Taxonomy Catalog == This taxonomy catalog is based on ZIP files. It was first created back in year 2009. For more information use the links in the Referen…'

Taxonomy Catalogs Overview

2016-02-22T13:03:35Z

Ihr:

== Taxonomy Catalogs Overview ==

As the name suggest, a taxonomy catalog is a local repository of taxonomy files that the processor can consume as if they were coming from the Internet.

For example:

An XBRL Report contains a schemaRef pointing to an external URL where a taxonomy shall be located.

In normal circumstances, the target URL is available and reading the Taxonomy is required to perform XBRL validation. Reading files from the Internet is also a slow process.

The solution is to install a kind of "proxy" that serves the files as if they were read from the official location but the file is on the hard drive.

The first idea about implementing taxonomy catalogs comes from OASIS [https://www.oasis-open.org/committees/entity/spec-2001-08-06.html https://www.oasis-open.org/committees/entity/spec-2001-08-06.html]

At this time, we have implemented several taxonomy catalogs so if one file is served by a taxonomy catalog the processor never goes to the Internet. On the tools that contains a user interface, at the very bottom of the taxonomy catalogs there is one that asks the user to provide a file from a directory. This makes a point about how deep we use the idea of taxonomy catalogs.

This wiki contains information about the 3 most commonly used:

The [[Oasis Taxonomy Catalogs]] was the first one implemented on the RS API. This one is good to map local files extracted in a directory that exactly matches the structure of the files on an official web site.

The [[Reporting Standard Taxonomy Catalog]] was defined back in year 2010. It is still in use and a good mechanism to distribute taxonomy packages. It is based on a ZIP file with an additional file with metadata that describes the ZIP content, the official URL start string and the mapping between the ZIP content (directories inside the ZIP) and the official locations. The API reads a file where are ZIP files that belongs to the catalog are explored.

The [[XBRL International Taxonomy Packages]] is similar to the previous one and it will be released as XBRL Specification during year 2016. The differences against the Reporting Standard Taxonomy Catalog are that the XBRL Int version supports the declaration of taxonomy entry points in the metadata and the ZIP file does not need to be "registered" in a separate file. The ZIP file can just be drop to a folder and it becomes available to be used.

There are calls to the DTSContainer in order to set the taxonomy catalogs available and to register additional taxonomy catalogs during the API startup. The API contains more taxonomy catalogs defined but they are considered "advanced use" and might not be documented here. If you need further information or assistant drop us an email.

= References =
[[XBRL Catalog]]<br/>
[[Adding taxonomies to the ZIP Catlog]]<br/>
[[Select Taxonomy From Catalog]]<br/>

=Navigation=
[[Main Page]]

Main Page

2016-02-03T15:31:33Z

Ihr: /* Reporting Standadrd XBRL WIKI. */

===Reporting Standadrd XBRL WIKI.===

This WIKI web site is organized in the following sections:

* XBRL Specifications and related discussions
** [[XBRL 2.1]]
*** [[Comments about the Call for review the proposed edit recommendation made on 2011/05/27]]
** [[XDT 1.0 Dimensions Specification]]
** [[XQuery Formula Specification (Minimun XML based and more XQuery based)]]

* Reporting Standard S.L. - Product specific discussions, including new feature requests
** Products WITH user interface
*** [[XBRLview]]
*** [[XBRLvalid]]
*** [[XBRLizer]]
*** [[XBRLmapper]]
*** [[Taxonomy Builder]]
*** [[TeamTax]]
** Components without user interface
*** [[XBRL API related discussions]]
*** [[XBRL Database]]
*** [[XBRL Validation Service]]
*** [[XBRL Storage Service]]
*** [[XhBtRmL]]
*** [[XBRLmapper as a service]]
** Other products and components
*** [[Excel XBRL functions library]]

=== Requirements ===

* Requirements
** [[Software requirements]]
** [[Hardware requirements]]

=== Installation ===
* Installation
** [[Installation on Windows]]
** [[Installation on UNIX (Linux, Solaris, AIX, Mac OS X)]]

=== Configuration ===
* [[Taxonomy Catalogs Overview]]
** [[Reporting Standard Taxonomy Catalog]]
** [[XBRL International Taxonomy Packages]]
** [[Oasis Taxonomy Catalogs]]
** [[Custom Taxonomy Catalogs such as Reporting Standard XBRL Database]]

==== Other optional installation steps ====

* [[Installing the XBRL Database]]

=== Useful links and frequently asked questions (FAQ) ===

# [[Where is the license file stored and how can I backup it?]]
# [[The XBRL Taxonomy Catalog]]
# [[java.security.SignatureException: invalid encoding for signature]]
# [[java.security.SignatureException: invalid encoding for signature (Español)]]
# [[This license will not work on this computer]]
# [[Esta licencia no funcionará en este computador]]
# [[Adding taxonomies to the ZIP Catalog]]
# [[Walkthrough downloading Reporting Standard XBRL tools set]]
# [[Walkthrough requesting evaluation license]]
# [[Walkthrough load and store XBRL taxonomies]]
# [http://www.supersociedades.gov.co/servicios/software-para-el-diligenciamiento/Paginas/NIIF-Videos-de-CapacitaciOn.aspx Vídeos respecto a la instalación y funcionamiento de las herramientas de licenciamiento XBRL para la Superintendencia de Sociedades de Colombia]

Taxonomy Catalogs Overview

2016-02-03T15:04:34Z

Ihr: /* Taxonomy Catalogs Overview */

Taxonomy Catalogs Overview

2016-02-03T15:02:26Z

Ihr: /* Taxonomy Catalogs Overview */

Taxonomy Catalogs Overview

2016-02-03T14:52:48Z

Ihr: /* Taxonomy Catalogs Overview */

Taxonomy Catalogs Overview

2016-02-02T21:02:43Z

Ihr:

Taxonomy Catalogs Overview

2016-02-02T21:01:23Z

Ihr: Created page with '== Taxonomy Catalogs Overview == As the name suggest, a taxonomy catalog is a local repository of taxonomy files that the processor can consume as if they were coming from the I…'

Main Page

2016-02-02T20:52:16Z

Ihr:

===Reporting Standadrd XBRL WIKI.===

This WIKI web site is organized in the following sections:

* XBRL Specifications and related discussions
** [[XBRL 2.1]]
*** [[Comments about the Call for review the proposed edit recommendation made on 2011/05/27]]
** [[XDT 1.0 Dimensions Specification]]
** [[Versioning (not a recommendation yet)]]
** [[XII Formula Specification (XML Based)]]
** [[XQuery Formula Specification (Minimun XML based and more XQuery based)]]

* Reporting Standard S.L. - Product specific discussions, including new feature requests
** Products WITH user interface
*** [[XBRLview]]
*** [[XBRLvalid]]
*** [[XBRLizer]]
*** [[XBRLmapper]]
*** [[Taxonomy Builder]]
*** [[TeamTax]]
** Components without user interface
*** [[XBRL API related discussions]]
*** [[XBRL Database]]
*** [[XBRL Validation Service]]
*** [[XBRL Storage Service]]
*** [[XhBtRmL]]
*** [[XBRLmapper as a service]]
** Other products and components
*** [[Excel XBRL functions library]]

=== Requirements ===

* Requirements
** [[Software requirements]]
** [[Hardware requirements]]

=== Installation ===
* Installation
** [[Installation on Windows]]
** [[Installation on UNIX (Linux, Solaris, AIX, Mac OS X)]]

=== Configuration ===
* [[Taxonomy Catalogs Overview]]
** [[Reporting Standard Taxonomy Catalog]]
** [[XBRL International Taxonomy Packages]]
** [[Oasis Taxonomy Catalogs]]
** [[Custom Taxonomy Catalogs such as Reporting Standard XBRL Database]]

==== Other optional installation steps ====

* [[Installing the XBRL Database]]

=== Useful links and frequently asked questions (FAQ) ===

# [[Where is the license file stored and how can I backup it?]]
# [[The XBRL Taxonomy Catalog]]
# [[java.security.SignatureException: invalid encoding for signature]]
# [[java.security.SignatureException: invalid encoding for signature (Español)]]
# [[This license will not work on this computer]]
# [[Esta licencia no funcionará en este computador]]
# [[Adding taxonomies to the ZIP Catalog]]
# [[Walkthrough downloading Reporting Standard XBRL tools set]]
# [[Walkthrough requesting evaluation license]]
# [[Walkthrough load and store XBRL taxonomies]]
# [http://www.supersociedades.gov.co/servicios/software-para-el-diligenciamiento/Paginas/NIIF-Videos-de-CapacitaciOn.aspx Vídeos respecto a la instalación y funcionamiento de las herramientas de licenciamiento XBRL para la Superintendencia de Sociedades de Colombia]

Setting environment variables

2015-11-28T15:04:24Z

Ihr:

In a normal installation, the XBRL API requires a directory with read/write permissions to the user who launches the tools. That directory is used later for the following purposes:
# A place to search for the license file
# A place to read taxonomies in the different supported taxonomy catalogs
# A place to store application properties and user configuration files

The specific mechanism to obtain the value of that directory is documented here: [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/util/RSStaticAndUser.html RSStaticAndUser java class documentation]

In sort, if you have no changed anything.
* On '''windows''' that directory is the content of the APPDATA environment variable, and the '''ReportingStandardXBRLTools'''. Normally this is C:\Users\{Your user name}\AppData\Roaming\ReportingStandardXBRLTools". Note that AppData is a hidden folder.
* On '''UNIX''' (Linux, Mac and other *Ix derived OS) it is the user's home directory followed by '''ReportingStandardXBRLTools'''.

You can modify the installation configuration by setting the following environment variables and Java Variables in order to set the location of common components such as the license file and taxonomy catalog files. The following environment variables and java variables are recognized by the XBRL API:

* '''XBRLCATALOGPATH''' This environment variable points to a ; separated list of directories that can be HOME of [[Taxonomy Catalogs]]. The Windows installer already sets the environment variable and the right value pointing to the directory where the installer has installed the Taxonomy Catalog.

* '''XBRLRSHOME''' This environment variable points to a directory that will be used as the home directory where Reporting Standard applications store user properties that are used to share information across multiple applications (like the information to connect to the XBRL Repository). The Windows installer does not set this environment variable and the API defaults to the user's home directory. The value is used in Windows and Unix, Java and .NET environments.

* '''xbrl.rs.home''' If this java system property exist, it shall point to a directory that will be used instead of the '''XBRLRSHOME''' enviroment variable.

* '''XBRLLIBRARYPATH''' This environment variable points to the directory where Reporting Standard libraries are installed on the system.

Note: the next directory after the directory pointed to by this variables must have a fixed name '''ReportingStandardXBRLTools'''.

There is more information about how the API obtains the path for a user file on the [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/util/RSStaticAndUser.html RSStaticAndUser java class documentation]

Taxonomy Catalogs

2015-11-28T15:02:13Z

Ihr:

RS API supports pluggable taxonomy catalogs.

Taxonomy catalogs are copies of XBRL files published on the Internet that accelerates DTS Loading process because it avoid the need to read files from the Internet every time an XBRL report is loaded or validated.

Every Taxonomy Catalog is a collection of files and metadata to indicate what content the catalog contains. Some catalogs reside in ZIP compressed format and some others in plain files on the filesystem and some others can be configured to use relational databases.

Taxonomy Catalogs can be installed on multiple places in the XBRL API. In normal circumstances, the root of the Taxonomy Catalog is obtained from the content of the XBRLCATALOGPATH environment variable. See [[Setting environment variables]] for more information.

Currently the following taxonomy catalogs are implemented:

== Oasis Taxonomy Catalogs ==

Oasis taxonomy catalogs are recognized by the existence of a Catalog file whose name must be '''XBRLCatalog.xml''' in any one of the directories listed in the XBRLCATALOGPATH environment variable. Those files must be according to the OASIS XML Catalog syntax convention. For this reason, it is recommended (but not required) that they reference the Catalog.xsd schema.

The catalog content are plain files and directories in the filesystem. The installation process might have installed some content on a directory called taxonomy-cache but that is not required. You are free to edit this file and supply new content using either the GUI or by using an XML editor.

The resolution of relative files is always relative to the location of the XBRLCatalog.xml file.

== Reporting Standard ZIP Catalog format ==

Reporting Standard ZIP catalogs are recognized by the existence of a Catalog file whose name must be '''RSZIPCatalog.xml''' in any one of the directories listed in the XBRLCATALOGPATH environment variable. Those files must be according to a XML Schema created by Reporting Standard. The content of this catalog can be managed by the user using the user interface or can be edited by normal XML editors.

The catalog content are ZIP files created by Reporting Standard. Reporting Standard maintains a global database of taxonomy packages using this format and the user can install or uninstall packages as required.

The resolution of a ZIP file location, when it is specified inside the RSZIPCatalog.xml follows the xml:base conventions. In the absence of specific xml:base attributes, the directory where the RSZIPCatalog.xml file is found is used as base for relative resolution. Note that our GUI tools install all zip files using a directory called taxonomy-packages but this is not required.

== XBRL Taxonomy Packages specification created by the XBRL International Consortium ==

Reporting Standard implements the XBRL Taxonomy Packages specification. The resolution of taxonomy packages does not require a specific configuration file. When the XBRL API starts, the content of directories whose name is "xbrl-packages" and exists in any of the folders indicated in the XBRLCATALOGPATH environment variable is explored and all ZIP files on that directory is loaded as an XBRL Taxonomy Package. If the ZIP file is not a proper ZIP file according with the specifications the file is ignored.

== Dynamic auto Taxonomy cache ==

This implementation of a taxonomy catalog stores local copies of files loaded during the DTS loading process so the next time the same file is loaded the local copy is used instead.

This catalog is disabled by default and MUST be enabled by manually adding a property to the JVM. The property name is http://www.reportingstandard.com/properties/dts-store-cache-enable and the property value must be the string "true" (without quotes).

== XBRL Database configured as a taxonomy catalog ==

The Reporting Standard XBRL Database stores a binary copy of files loaded during the DTS Discovery process in the Documents table. There is an implementation of the Taxonomy Catalog interfaces that uses the content of that table as source of files for DTS Discovery. The use of this Taxonomy Catalog resolver is optional but it can be enabled by applications that uses the XBRL Database in an organization. GUI applications such as XBRLizer, the Instance document viewer, XBRLExpress etc already uses the XBRL Database as a taxonomy catalog when a database is configured. If you have develop an application and want to make sure your application uses the XBRL Database as Taxonomy Catalog please contact Reporting Standard S.L. for detailed instructions.

Taxonomy Catalogs

2015-11-28T12:55:58Z

Ihr: Created page with 'RS API supports pluggable taxonomy catalogs. Taxonomy catalogs are copies of XBRL files published on the Internet that accelerates DTS Loading process because it avoid the need …'

Setting environment variables

2015-11-28T12:31:49Z

Ihr:

In a normal installation, the XBRL API requires a directory with read/write permissions to the user who launches the tools. That directory is used later for the following purposes:
# A place to search for the license file
# A place to read taxonomies in the different supported taxonomy catalogs
# A place to store application properties and user configuration files

The specific mechanism to obtain the value of that directory is documented here: [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/util/RSStaticAndUser.html RSStaticAndUser java class documentation]

In sort, if you have no changed anything.
* On '''windows''' that directory is the content of the APPDATA environment variable, and the "ReportingStandardXBRLTools". Normally this is C:\Users\{Your user name}\AppData\Roaming\ReportingStandardXBRLTools". Note that AppData is a hidden folder.
* On '''UNIX''' (Linux, Mac and other *Ix derived OS) it is the user's home directory followed by "ReportingStandardXBRLTools".

You can modify the installation configuration by setting the following environment variables and Java Variables in order to set the location of common components such as the license file and taxonomy catalog files. The following environment variables and java variables are recognized by the XBRL API:

* '''XBRLCATALOGPATH''' This environment variable points to a ; separated list of directories that can be HOME of [[Taxonomy Catalogs]]. The Windows installer already sets the environment variable and the right value pointing to the directory where the installer has installed the Taxonomy Catalog.

* '''XBRLRSHOME''' This environment variable points to a directory that will be used as the home directory where Reporting Standard applications store user properties that are used to share information across multiple applications (like the information to connect to the XBRL Repository). The Windows installer does not set this environment variable and the API defaults to the user's home directory. The value is used in Windows and Unix, Java and .NET environments.

* '''xbrl.rs.home''' If this java system property exist, it shall point to a directory that will be used instead of the '''XBRLRSHOME''' enviroment variable.

* '''XBRLLIBRARYPATH''' This environment variable points to the directory where Reporting Standard libraries are installed on the system.

Note: the next directory after the directory pointed to by this variables must have a fixed name '''ReportingStandardXBRLTools'''.

There is more information about how the API obtains the path for a user file on the [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/util/RSStaticAndUser.html RSStaticAndUser java class documentation]

Setting environment variables

2015-11-28T12:28:53Z

Ihr:

In a normal installation, the XBRL API requires a directory with read/write permissions to the user who launches the tools. That directory is used later for the following purposes:
# A place to search for the license file
# A place to read taxonomies in the different supported taxonomy catalogs
# A place to store application properties and user configuration files

The specific mechanism to obtain the value of that directory is documented here: [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/util/RSStaticAndUser.html RSStaticAndUser java class documentation]

In sort, if you have no changed anything.
* On '''windows''' that directory is the content of the APPDATA environment variable, and the "ReportingStandardXBRLTools". Normally this is C:\Users\{Your user name}\AppData\Roaming\ReportingStandardXBRLTools". Note that AppData is a hidden folder.
* On '''UNIX''' (Linux, Mac and other *Ix derived OS) it is the user's home directory followed by "ReportingStandardXBRLTools".

You can modify the installation configuration by setting the following environment variables and Java Variables in order to set the location of common components such as the license file and taxonomy catalog files. The following environment variables and java variables are recognized by the XBRL API:

* '''XBRLCATALOGPATH''' This environment variable points to a ; separated list of directories where files with the name '''XBRLCatalog.xml''' exist. Those files must be according to the OASIS XML Catalog syntax convention. For this reason, it is recommended (but not required) that they reference the Catalog.xsd schema. The variable has effect in Windows and Unix, Java and .NET environments. The Windows installer already sets the environment variable and the right value pointing to the directory where the installer has installed the Taxonomy Catalog.

* '''XBRLRSHOME''' This environment variable points to a directory that will be used as the home directory where Reporting Standard applications store user properties that are used to share information across multiple applications (like the information to connect to the XBRL Repository). The Windows installer does not set this environment variable and the API defaults to the user's home directory. The value is used in Windows and Unix, Java and .NET environments.

* '''xbrl.rs.home''' If this java system property exist, it shall point to a directory that will be used instead of the '''XBRLRSHOME''' enviroment variable.

* '''XBRLLIBRARYPATH''' This environment variable points to the directory where Reporting Standard libraries are installed on the system.

Note: the next directory after the directory pointed to by this variables must have a fixed name '''ReportingStandardXBRLTools'''.

There is more information about how the API obtains the path for a user file on the [http://www.reportingstandard.com/apidoc/com/ihr/xbrl/util/RSStaticAndUser.html RSStaticAndUser java class documentation]