context_id

[jfraschilla]

Are the context_id's consistent for all companies?
Does the context_id map to a concept?
Context(context_id='c-20', entity={'scheme': 'http://www.sec.gov/CIK', 'identifier': '0000320193'}, period={'type': 'duration', 'startDate': '2024-12-29', 'endDate': '2025-03-29'}, dimensions={}),

[dgunning]

Are the context_id's consistent for all companies?

No, context_ids are not consistent across all companies. The contextId is defined within each XBRL instance file by the filer (the company). While the structure of what a context represents (entity, period, dimensions) is standardized, the actual string used for the contextId (e.g., "Current_AsOf_Dec_31_2023", "YTD_Q3_2023_ScenarioA") is chosen by the company preparing the filing. The parser extracts these filer-defined IDs and their associated details.

Does the context_id map to a concept?

No, a context_id itself does not directly map to a single XBRL concept . Instead:
A context (identified by contextId) defines the specific circumstances for a reported value – such as the entity, reporting period, and any dimensional information (e.g., business segment, geographical region).

A concept (or "element" like us-gaap:Assets) is a specific piece of financial data being reported.
A fact links a concept (element) with a context to provide a specific value. The FactDatabase is structured with keys like "elementId_contextId", indicating that a fact is the combination of an element and a context.

Therefore, a single context_id can be referenced by many different facts, each pertaining to a different concept. For example, the context "For the year ended Dec 31, 2023" could be used with facts for "Revenues," "Net Income," "Operating Expenses," etc.

The context provides the "who, when, and what scenario," while the element provides the "what financial item."

[jfraschilla]

Thank you