abstract
An abstract is a report element. It is like a concept, except that no fact may be reported against it. Abstract are used to organize concepts in a meaningful hierarchy.
archive
An archive is a package of facts that get submitted together, with the associated metadata (taxonomy).
- 1.2. Output formats
- 3.7. API reference
- 3.8. API reference (copy archives)
- 6.5. API reference
- 13.1. API reference
- 8.9. Facts API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 10.6. API reference
- 9.6. API reference
- 3.9. API reference (periods)
- 14. Complete API Reference
- 7.7. API reference
- 11.3. API reference
- 5.6. API reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 4.1. API reference
- 3. Archives
- 3.1. List archives
- 3.2. Look up an archive
- 3.3. Archive metadata
- 3.4. Available periods
- 3.5. Add an archive
- 3.6. Delete an archive
- 15. Changelog
- 6. Components
- 6.1. List components
- 6.2. Identify components
- 6.3. Component metadata
- 8. Facts
- 8.3. Slicers and dicers
- 8.8. Facts
- 0.3. Cell store vocabulary
- 0.4. Analogy with spreadsheets
- 10. Labels
- 10.1. List labels
- 10.2. Identify labels
- 10.3. Label metadata
- 10.4. Add a label
- 9.3. Model structure metadata
- 9.4. Add a model structure
- 7.1. Kinds of report elements
- 7.4. Report element metadata
- 7.5. Add a report element
- 11. Rules
- 5. Sections
- 5.1. List sections
- 5.2. Identify sections
- 5.3. Section metadata
- 5.4. Add a section
aspect
An aspect is a dimension-value pair in a context. It is also used as a synonym for dimension.
component
Within an archive, facts that make sense together are grouped in components.
- 1.1. Endpoints
- 6.5. API reference
- 13.1. API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 10.6. API reference
- 9.6. API reference
- 14. Complete API Reference
- 7.7. API reference
- 11.3. API reference
- 5.6. API reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 15. Changelog
- 6. Components
- 6.2. Identify components
- 6.3. Component metadata
- 6.4. Component by data points
- 13. Data points
- 8.1. List facts
- 8.7. Labels
- 16.6. CellStore
- 0.3. Cell store vocabulary
- 0.4. Analogy with spreadsheets
- 10. Labels
- 10.1. List labels
- 9. Model Structures
- 9.1. Hierarchies
- 9.2. Get a model structure
- 9.3. Model structure metadata
- 9.4. Add a model structure
- 9.5. Delete a model structure
- 7. Report elements
- 7.1. Kinds of report elements
- 7.2. List report elements
- 5. Sections
- 5.3. Section metadata
- 12. Spreadsheets
- 12.1. View a spreadsheet
concept
A concept is a report element. In a fact, it is always associated with the xbrl:Concept aspect.
- 6.5. API reference
- 13.1. API reference
- 8.9. Facts API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 10.6. API reference
- 9.6. API reference
- 14. Complete API Reference
- 7.7. API reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 8. Facts
- 8.2. Hypercube queries
- 8.3. Slicers and dicers
- 8.4. Aggregation
- 8.6. Other fields
- 8.7. Labels
- 8.8. Facts
- 0.3. Cell store vocabulary
- 10. Labels
- 9. Model Structures
- 9.1. Hierarchies
- 9.3. Model structure metadata
- 9.4. Add a model structure
- 7.1. Kinds of report elements
- 7.4. Report element metadata
- 7.5. Add a report element
- 11. Rules
- 11.2. Rule metadata
- 5. Sections
context
A context is a set of dimensional coordinates that gives meaning to the value of a fact.
default value
A dimension often has a default value. When a hypercube query is performed, then facts where this dimension is absent will be included in the result, and their context will be modified with an additional aspect that associates the dimension with its default value.
dimension
A dimension is a report element. When associated with a value in a fact context, it is called an aspect. A dimension is associated with a member, except the xbrl:Concept dimension, which is associated with a concept.
- 6.5. API reference
- 13.1. API reference
- 8.9. Facts API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 9.6. API reference
- 14. Complete API Reference
- 7.7. API reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 8. Facts
- 8.3. Slicers and dicers
- 8.4. Aggregation
- 8.5. Default dimension values
- 8.7. Labels
- 9. Model Structures
- 9.1. Hierarchies
- 9.3. Model structure metadata
- 7.1. Kinds of report elements
- 7.4. Report element metadata
- 7.5. Add a report element
- 5. Sections
entity
Facts are reported by entities (such as Apple). Usually, entities report facts about themselves, so that it's the same entity that appears in the contexts of the facts that it reports.
- 2.5. Delete an entity
- 3.7. API reference
- 3.8. API reference (copy archives)
- 6.5. API reference
- 13.1. API reference
- 2.6. API reference
- 8.9. Facts API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 10.6. API reference
- 9.6. API reference
- 3.9. API reference (periods)
- 14. Complete API Reference
- 7.7. API reference
- 11.3. API reference
- 5.6. API reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 4.1. API reference
- 3. Archives
- 3.1. List archives
- 3.3. Archive metadata
- 3.5. Add an archive
- 15. Changelog
- 2. Entities
- 2.1. List entities
- 2.2. Identify entities
- 2.3. Entity metadata
- 2.4. Add an entity
- 8. Facts
- 8.2. Hypercube queries
- 8.3. Slicers and dicers
- 8.4. Aggregation
- 8.7. Labels
- 0.3. Cell store vocabulary
- 0.4. Analogy with spreadsheets
- 10.2. Identify labels
- 7.1. Kinds of report elements
fact
A fact is an atom of data. It is a value associated with a context.
- 6.5. API reference
- 13.1. API reference
- 8.9. Facts API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 14. Complete API Reference
- 7.7. API reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 15. Changelog
- 2.2. Identify entities
- 8. Facts
- 8.1. List facts
- 8.2. Hypercube queries
- 8.3. Slicers and dicers
- 8.4. Aggregation
- 8.5. Default dimension values
- 8.6. Other fields
- 8.7. Labels
- 8.8. Facts
- 0.1. XBRL
- 0.3. Cell store vocabulary
- 0.4. Analogy with spreadsheets
- 9. Model Structures
- 7. Report elements
- 7.1. Kinds of report elements
- 5.3. Section metadata
- 12. Spreadsheets
- 12.3. Validating cells
fact table
A fact table is a very structured display of a bunch of facts. A fact table is the result of a hypercube query. Each column corresponds to a dimension, and an additional column to the value.
- 1.1. Endpoints
- 13.1. API reference
- 8.9. Facts API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 14. Complete API Reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 8.1. List facts
- 8.3. Slicers and dicers
- 8.7. Labels
- 0.3. Cell store vocabulary
- 0.4. Analogy with spreadsheets
- 9. Model Structures
hypercube
A hypercube, in the cell store, is a query that returns facts from the main pool. It is also a report element that can be used in a component. A hypercube has dimensions, and each dimension is associated with a set of accepted values.
- 3.7. API reference
- 6.5. API reference
- 13.1. API reference
- 2.6. API reference
- 8.9. Facts API reference
- 8.10. API reference (fact table for component)
- 8.11. API reference (fact table for report)
- 10.6. API reference
- 9.6. API reference
- 3.9. API reference (periods)
- 14. Complete API Reference
- 7.7. API reference
- 11.3. API reference
- 5.6. API reference
- 12.5. API reference (spreadsheet for component)
- 12.6. API reference (spreadsheet for report)
- 4.1. API reference
- 6. Components
- 6.2. Identify components
- 6.3. Component metadata
- 6.4. Component by data points
- 13. Data points
- 8.1. List facts
- 8.2. Hypercube queries
- 8.3. Slicers and dicers
- 8.4. Aggregation
- 8.5. Default dimension values
- 8.7. Labels
- 0.2. Cell stores
- 9. Model Structures
- 9.1. Hierarchies
- 9.3. Model structure metadata
- 9.4. Add a model structure
- 7.1. Kinds of report elements
- 7.4. Report element metadata
- 7.5. Add a report element
- 5. Sections
JSONiq
JSONiq is a NoSQL query language that deals with heterogeneous, arborescent data. It comes with a number of connectors that make it convenient to access, simultaneously, many data sources (MongoDB databases, traditional relational databases, S3 storage on Amazon, Graph Databases, Cloudant and many more) and combine them seamlessly to extract information. JSONiq knowledge is not required for using cell stores.
line items
The line items report element is the top level report element in the hierarchy of abstracts and concepts.
member
A member is a report element. A member is typically associated with a dimension (aspect) in the context of a fact (except the *xbrl:Concept* aspect).
report element
A report element is a building block of a component. They correspond to metadata cells in a spreadsheet. There are six kinds of report elements: concepts, abstracts, line items, dimension, member, hypercube.
- 6.5. API reference
- 13.1. API reference
- 8.10. API reference (fact table for component)
- 10.6. API reference
- 9.6. API reference
- 14. Complete API Reference
- 7.7. API reference
- 11.3. API reference
- 5.6. API reference
- 12.5. API reference (spreadsheet for component)
- 0.3. Cell store vocabulary
- 0.4. Analogy with spreadsheets
- 10. Labels
- 10.2. Identify labels
- 10.3. Label metadata
- 10.4. Add a label
- 9.1. Hierarchies
- 9.3. Model structure metadata
- 9.4. Add a model structure
- 7.1. Kinds of report elements
- 7.4. Report element metadata
- 7.5. Add a report element
- 7.6. Delete a report element
section
A section is a group of components that share their metadata (report elements). A section is identified by a URI.
- 6.5. API reference
- 13.1. API reference
- 8.10. API reference (fact table for component)
- 10.6. API reference
- 9.6. API reference
- 14. Complete API Reference
- 7.7. API reference
- 11.3. API reference
- 5.6. API reference
- 12.5. API reference (spreadsheet for component)
- 6. Components
- 6.2. Identify components
- 6.3. Component metadata
- 16.6. CellStore
- 0.3. Cell store vocabulary
- 0.4. Analogy with spreadsheets
- 10.2. Identify labels
- 10.3. Label metadata
- 10.4. Add a label
- 9.3. Model structure metadata
- 9.4. Add a model structure
- 7.4. Report element metadata
- 7.5. Add a report element
- 11.1. List rules
- 5. Sections
- 5.2. Identify sections
- 5.3. Section metadata
- 5.4. Add a section
- 5.5. Delete a section
- 12.4. Slicing and dicing