Walkthrough load and store XBRL taxonomies - Revision history

Agil at 15:05, 8 January 2019

2019-01-08T15:05:49Z

← Older revision		Revision as of 15:05, 8 January 2019
Line 96:		Line 96:
	= Feedback =		= Feedback =
	Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]		Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]

	~~=Navigate=~~
	~~[[Main Page]]~~

Agil at 15:05, 8 January 2019

2019-01-08T15:05:03Z

← Older revision		Revision as of 15:05, 8 January 2019
Line 15:		Line 15:
	* the Database package that provide additional tools to work directly with the database		* the Database package that provide additional tools to work directly with the database

	Visit the [[Walkthrough downloading Reporting Standard XBRL tools set]] page in order to find the download URLs for the packages that are not publicly available in the [~~http~~://www.reportingstandard.com/~~index.php~~/en~~/downloads~~ downloads page]		Visit the [[Walkthrough downloading Reporting Standard XBRL tools set]] page in order to find the download URLs for the packages that are not publicly available in the [https://www.reportingstandard.com/downloads/?lang=en downloads page]

	Visit also the [[Hardware requirements]] and [[Software requirements]] pages and check your environment meets them.		Visit also the [[Hardware requirements]] and [[Software requirements]] pages and check your environment meets them.
Line 30:		Line 30:
	== Installing required XBRL packages into the local taxonomy catalog ==		== Installing required XBRL packages into the local taxonomy catalog ==

	Starting with version 2.8.5 of Reporting Standard tools set we incorporated support for the [~~http~~://xbrl.org/Specification/taxonomy-package/PWD-2014-01-15/taxonomy-package-PWD-2014-01-15.html Taxonomy Package 1.0 Public Working Draft 15 January 2014] in addition to that taxonomy catalog.		Starting with version 2.8.5 of Reporting Standard tools set we incorporated support for the [https://www.xbrl.org/Specification/taxonomy-package/PWD-2014-01-15/taxonomy-package-PWD-2014-01-15.html Taxonomy Package 1.0 Public Working Draft 15 January 2014] in addition to that taxonomy catalog.

	In order to speed up taxonomy loading process it is worth installing local copies of the remote official files. Installation of taxonomy packages is a simple straight forward step.		In order to speed up taxonomy loading process it is worth installing local copies of the remote official files. Installation of taxonomy packages is a simple straight forward step.
Line 65:		Line 65:
	The database table model is a normalized relational model composed of different layers. At the top is there is the Documents layer, that contains a physical copy of the files that compose the DTS. At the bottom there is the XML layer that contains several tables to define an XML Fragment composed by XML Nodes (every attribute is a node, every element is a fragment, the element value is a node too) and every node is a pair of a qualified name and qualified value.		The database table model is a normalized relational model composed of different layers. At the top is there is the Documents layer, that contains a physical copy of the files that compose the DTS. At the bottom there is the XML layer that contains several tables to define an XML Fragment composed by XML Nodes (every attribute is a node, every element is a fragment, the element value is a node too) and every node is a pair of a qualified name and qualified value.

	The model contains two structures that are related one to the other. The table structure represents the database tables, indexes, and foreign keys between the tables. The entity structure contains the XBRL object model that is serialized to the database. The complete documentation about those two models is [~~http~~://www.reportingstandard.com/pojo/documentation/entities/index.html on this web page]		The model contains two structures that are related one to the other. The table structure represents the database tables, indexes, and foreign keys between the tables. The entity structure contains the XBRL object model that is serialized to the database. The complete documentation about those two models is [https://www.reportingstandard.com/pojo/documentation/entities/index.html on this web page]

	The model is extensible. Users can define additional entities and tables and the add the user model to the XBRL model. During the DTS Storage process the user defined objects that are populated and related with the XBRL model will be written to the database too. This feature requires some knowledge about the technologies used to document the entity model so they will not be covered by this documentation. Please contact us if you want more information in this regard.		The model is extensible. Users can define additional entities and tables and the add the user model to the XBRL model. During the DTS Storage process the user defined objects that are populated and related with the XBRL model will be written to the database too. This feature requires some knowledge about the technologies used to document the entity model so they will not be covered by this documentation. Please contact us if you want more information in this regard.

Ihr: Protected "Walkthrough load and store XBRL taxonomies" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2014-08-12T17:55:10Z

Protected "Walkthrough load and store XBRL taxonomies" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

← Older revision

Revision as of 17:55, 12 August 2014

Ihr: /* Doing some queries on the database model */

2014-08-12T10:52:56Z

Doing some queries on the database model

← Older revision		Revision as of 10:52, 12 August 2014
Line 86:		Line 86:

	This query obtains the element name for rows returned in the previous query '''select r.from.name.name from XBRLRelationship r where r.arcrole.uri like '%element-label' and r.to.value.name like '%Assets%''''		This query obtains the element name for rows returned in the previous query '''select r.from.name.name from XBRLRelationship r where r.arcrole.uri like '%element-label' and r.to.value.name like '%Assets%''''

			This screen capture merges the output of the previous two queries:
			[[File:hql-sample-element-and-label.png]]

	This query obtains concept labels from concept names: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.		This query obtains concept labels from concept names: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.

Ihr: /* Doing some queries on the database model */

2014-08-12T10:47:56Z

Doing some queries on the database model

← Older revision		Revision as of 10:47, 12 August 2014
Line 81:		Line 81:
	Another example: '''select c.parent.namespace, c.conceptName from XBRLConcept c where c.conceptName like 'x6'''' here we are selecting the XBRLConcept entity and filtering all them whose concept name is just '''x6'''. in our example, there are 24 definitions of this concept name in 24 different taxonomy schemas. In order to know the schema namespare where the concept is defined, we are going to include the taxonomy (the parent property of a concept) and from the taxonomy we will access the namespace definition (that is in another entity called Namespace). Now you can see how useful and powerful the dot notation is in obtaining information related to an entity that is stored in another related entity.		Another example: '''select c.parent.namespace, c.conceptName from XBRLConcept c where c.conceptName like 'x6'''' here we are selecting the XBRLConcept entity and filtering all them whose concept name is just '''x6'''. in our example, there are 24 definitions of this concept name in 24 different taxonomy schemas. In order to know the schema namespare where the concept is defined, we are going to include the taxonomy (the parent property of a concept) and from the taxonomy we will access the namespace definition (that is in another entity called Namespace). Now you can see how useful and powerful the dot notation is in obtaining information related to an entity that is stored in another related entity.

	The last ~~two~~ examples are using the XBRLRelationship table to select specific relationships and then exploring the from and to sides of them.		The last examples are using the XBRLRelationship table to select specific relationships and then exploring the from and to sides of them.

	Obtain concept labels from concept names: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.		Obtain element labels from labels text: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri like '%element-label' and r.to.value.name like '%Assets%''''. This query obtains element labels that contains the word '''Assets''' anywhere in the label text.

			This query obtains the element name for rows returned in the previous query '''select r.from.name.name from XBRLRelationship r where r.arcrole.uri like '%element-label' and r.to.value.name like '%Assets%''''

			This query obtains concept labels from concept names: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.

	[[File:hql-sample-query.png]]		[[File:hql-sample-query.png]]

	Obtain concept labels from concept labels content: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri like '%element-label' and r.to.value.name like '%Assets%''''. This query obtains concept labels that contains the word '''Assets''' anywhere in the concept label.

	= Feedback =		= Feedback =

Ihr: /* Doing some queries on the database model */

2014-08-12T10:34:53Z

Doing some queries on the database model

← Older revision		Revision as of 10:34, 12 August 2014
Line 81:		Line 81:
	Another example: '''select c.parent.namespace, c.conceptName from XBRLConcept c where c.conceptName like 'x6'''' here we are selecting the XBRLConcept entity and filtering all them whose concept name is just '''x6'''. in our example, there are 24 definitions of this concept name in 24 different taxonomy schemas. In order to know the schema namespare where the concept is defined, we are going to include the taxonomy (the parent property of a concept) and from the taxonomy we will access the namespace definition (that is in another entity called Namespace). Now you can see how useful and powerful the dot notation is in obtaining information related to an entity that is stored in another related entity.		Another example: '''select c.parent.namespace, c.conceptName from XBRLConcept c where c.conceptName like 'x6'''' here we are selecting the XBRLConcept entity and filtering all them whose concept name is just '''x6'''. in our example, there are 24 definitions of this concept name in 24 different taxonomy schemas. In order to know the schema namespare where the concept is defined, we are going to include the taxonomy (the parent property of a concept) and from the taxonomy we will access the namespace definition (that is in another entity called Namespace). Now you can see how useful and powerful the dot notation is in obtaining information related to an entity that is stored in another related entity.

	The last ~~example~~: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.		The last two examples are using the XBRLRelationship table to select specific relationships and then exploring the from and to sides of them.

			Obtain concept labels from concept names: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.

	[[File:hql-sample-query.png]]		[[File:hql-sample-query.png]]

			Obtain concept labels from concept labels content: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri like '%element-label' and r.to.value.name like '%Assets%''''. This query obtains concept labels that contains the word '''Assets''' anywhere in the concept label.

	= Feedback =		= Feedback =

Ihr: /* Prepare the database to store XBRL information */

2014-08-11T09:48:11Z

Prepare the database to store XBRL information

← Older revision		Revision as of 09:48, 11 August 2014
Line 42:		Line 42:
	== Prepare the database to store XBRL information ==		== Prepare the database to store XBRL information ==

	Follow the instructions indicated on the [[Installing the XBRL Database]] pages in order to install and set up the table models. ~~Use~~ the database ~~that best fit your environment~~. Then come back to this page and continue with the next steps.		Follow the instructions indicated on the [[Installing the XBRL Database]] pages in order to install and set up the table models. For this test we are using Microsoft SQL Server Express 2008, but the database can be installed on Oracle, IBM DB2 or PostgreSQL. Then come back to this page and continue with the next steps.

	== Store a taxonomy into the database ==		== Store a taxonomy into the database ==

Ihr: /* Doing some queries on the database model */

2014-08-10T11:04:53Z

Doing some queries on the database model

← Older revision		Revision as of 11:04, 10 August 2014
Line 82:		Line 82:

	The last example: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.		The last example: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.

			[[File:hql-sample-query.png]]

	= Feedback =		= Feedback =

Ihr: /* Doing some queries on the database model */

2014-08-10T10:59:57Z

Doing some queries on the database model

← Older revision		Revision as of 10:59, 10 August 2014
Line 81:		Line 81:
	Another example: '''select c.parent.namespace, c.conceptName from XBRLConcept c where c.conceptName like 'x6'''' here we are selecting the XBRLConcept entity and filtering all them whose concept name is just '''x6'''. in our example, there are 24 definitions of this concept name in 24 different taxonomy schemas. In order to know the schema namespare where the concept is defined, we are going to include the taxonomy (the parent property of a concept) and from the taxonomy we will access the namespace definition (that is in another entity called Namespace). Now you can see how useful and powerful the dot notation is in obtaining information related to an entity that is stored in another related entity.		Another example: '''select c.parent.namespace, c.conceptName from XBRLConcept c where c.conceptName like 'x6'''' here we are selecting the XBRLConcept entity and filtering all them whose concept name is just '''x6'''. in our example, there are 24 definitions of this concept name in 24 different taxonomy schemas. In order to know the schema namespare where the concept is defined, we are going to include the taxonomy (the parent property of a concept) and from the taxonomy we will access the namespace definition (that is in another entity called Namespace). Now you can see how useful and powerful the dot notation is in obtaining information related to an entity that is stored in another related entity.

	The last example: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = 'http://www.xbrl.org/2003/arcrole/concept-label' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.		The last example: '''select r.to.value.name from XBRLRelationship r where r.arcrole.uri = '<nowiki>http://www.xbrl.org/2003/arcrole/concept-label</nowiki>' and r.from.conceptName = 'x6'''' this one obtains the labels defined for concepts where the concept name is x6. The query traverses the XBRLRelationship entity and filter those who has an specific arc role (concept-label) and, at the from part of the relationship, there is a concept where the concept name is 'x6'. You can now feel the power of the dot hehe. Once the relationships are selected, we will obtain the to side of the relationship and from that point we will go further to the 'value' (which is the XBRLResource) and from there to the 'name' which is the local part of the QName.



	= Feedback =		= Feedback =

Ihr at 10:59, 10 August 2014

2014-08-10T10:59:26Z

@@ Line 60: / Line 60: @@
 Now is time to get a cold coke from the fridge
 = Feedback =
 Send us feedback about this information to: [mailto:support@reportingstandard.com Support at ReportingStandard dot com]