22:
128:
Taxonomy
Architecture. The intent of the XBRLS architecture is to make it easier for business users to make use of XBRL, to make it easier for software vendors to support XBRL, and to safely use the features of XBRL. XBRLS is a subset of what is allowed by the complete XBRL Specification. Examples
104:
XBRLS is intended to enable the non-XBRL expert to create both XBRL metadata and XBRL reports in a simple and convenient manner. At the same time, it seeks to improve the usability of XBRL, the interoperability among XBRL-based solutions, the effectiveness of XBRL extensions and to reduce software
88:
XBRLS is designed to be 100% XBRL compliant. The stated goals of XBRLS are "to maximize XBRL's benefits, reduce costs of implementation, and maximize the functionality and effectiveness of XBRL". XBRL is a general purpose specification, based on the idea that no one is likely to use 100% of the
89:
components of XBRL in building any one solution. XBRLS specifies a subset of XBRL that is designed to meet the needs of most business users in most situations, and offers it as a starting point for others. This approach creates an application profile of XBRL (equivalent to a
205:
Although not required when using XBRLS, it is highly encouraged that the entity scheme and identifier be “held static” or synchronized with an explicit member and rather have XBRL Dimensions be used to articulate entity information, perhaps with an XBRLS “Entity ” dimension.
239:
Only uses XBRL Dimensions to articulate the content of segments and scenarios, excluding the use of XML Schema-based contextual information allowed by sections. Furthermore, mixing XML Schema based-contextual information and XBRL Dimensions is technically dangerous.
212:(i.e., dummy values in order to pass XBRL validation), using constant values. The information articulates relating to the entity identifier and entity scheme are moved to an XBRLS specific taxonomy that makes use of XBRL Dimensions to communicate this information.
224:
Although not required when using XBRLS, it is highly encouraged that the period context be “held static” or synchronized with an explicit member and that rather XBRL Dimensions be used to articulate this information, perhaps with an XBRLS “Period ” dimension.
292:
Each schema and each linkbase must provide documentation that describes the contents of the file that is readable by a computer application.
208:
The “entity identifier” and “entity scheme” portion of a context should not be used. Rather, the “entity identifier” and “entity schema” are
363:
393:
398:
388:
368:
281:
The weight attribute value of calculations must be either “1” or “-1”, no decimal value between the two is allowed.
140:
Only uses the segment element of the instance context and disallows the use of the scenario element.
78:
108:
The profile was created by Rene van Egmond and
Charlie Hoffman, who was the initial creator of
32:
147:
as content for the segment element in the instance context. Furthermore, it requires that
377:
90:
383:
151:(member, primary item) participates in a hypercube and that all hypercubes are
51:
41:
21:
158:
Allows no uses of simple or complex typed members within XBRL Dimensions.
94:
314:
Only “all” has-hypercube arcroles are allowed, “notAll” is not allowed
125:
113:
358:
343:
303:
Open hypercubes are not allowed, only closed hypercubes are allowed.
134:
109:
98:
82:
227:
Uses XBRL Dimensions to articulate this XBRL quasi dimension.
15:
124:
The XBRLS architecture is based on many ideas used by the
129:
of these limitations placed on XBRL are the following:
46:
36:
325:Typed members (simple or complex) are not allowed.
184:
364:XBRLS: how a simpler XBRL can make a better XBRL
8:
202:Context: entity identifier, entity scheme
336:
233:Instance (sections 4.7.4 and 4.7.3.2)
176:exists in at least one XBRL Dimension.
7:
359:XBRL Business Information Exchange
344:XBRL Business Information Exchange
14:
181:XBRL Components not used in XBRLS
145:only XBRL dimensional information
20:
112:. It borrows heavily from the
75:XBRL Simple Application Profile
165:uses the precision attribute,
1:
236:Context: segments, scenarios
169:uses the decimals attribute.
415:
289:Annotation, Documentation
270:Tuples are not allowed.
116:Taxonomy Architecture.
35:, as no other articles
248:Fact Value: precision
369:Comprehensive Example
394:Financial accounting
399:Accounting software
389:XML-based standards
188:XBRL Specification
105:development costs.
93:but concerned with
79:application profile
259:must not be used.
120:XBRLS Architecture
54:for suggestions.
44:to this page from
329:
328:
267:Elements: tuples
68:
67:
406:
347:
341:
300:Open Hypercubes
221:Context: period
185:
63:
60:
49:
47:related articles
24:
16:
414:
413:
409:
408:
407:
405:
404:
403:
374:
373:
355:
350:
342:
338:
334:
183:
122:
64:
58:
55:
45:
42:introduce links
25:
12:
11:
5:
412:
410:
402:
401:
396:
391:
386:
376:
375:
372:
371:
366:
361:
354:
353:External links
351:
349:
348:
335:
333:
330:
327:
326:
323:
322:Typed Members
320:
316:
315:
312:
309:
305:
304:
301:
298:
294:
293:
290:
287:
283:
282:
279:
276:
272:
271:
268:
265:
261:
260:
251:Uses only the
249:
246:
242:
241:
237:
234:
230:
229:
222:
219:
215:
214:
203:
200:
196:
195:
192:
189:
182:
179:
178:
177:
172:Requires that
170:
159:
156:
141:
138:
121:
118:
66:
65:
52:Find link tool
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
411:
400:
397:
395:
392:
390:
387:
385:
382:
381:
379:
370:
367:
365:
362:
360:
357:
356:
352:
345:
340:
337:
331:
324:
321:
318:
317:
313:
310:
307:
306:
302:
299:
296:
295:
291:
288:
285:
284:
280:
277:
274:
273:
269:
266:
263:
262:
258:
254:
250:
247:
244:
243:
238:
235:
232:
231:
228:
223:
220:
217:
216:
213:
211:
204:
201:
198:
197:
193:
190:
187:
186:
180:
175:
174:every measure
171:
168:
164:
160:
157:
154:
150:
149:every concept
146:
142:
139:
136:
132:
131:
130:
127:
119:
117:
115:
111:
106:
102:
100:
96:
92:
91:database view
86:
84:
80:
76:
72:
62:
53:
48:
43:
39:
38:
34:
29:This article
27:
23:
18:
17:
339:
256:
252:
226:
209:
207:
194:Explanation
173:
166:
162:
152:
148:
144:
123:
107:
103:
87:
74:
70:
69:
59:October 2023
56:
30:
319:Dimensions
308:Dimensions
297:Dimensions
286:Taxonomies
275:Taxonomies
255:attribute,
378:Categories
50:; try the
37:link to it
332:Footnotes
264:Taxonomy
257:precision
245:Instance
218:Instance
199:Instance
40:. Please
253:decimals
133:Uses no
95:metadata
77:) is an
346:website
311:notAll
278:Weight
143:Allows
126:US GAAP
114:US GAAP
210:static
191:Topic
167:always
161:XBRLS
153:closed
135:tuples
97:, not
33:orphan
31:is an
163:never
71:XBRLS
110:XBRL
99:data
83:XBRL
384:XML
101:).
81:of
380::
85:.
155:.
137:.
73:(
61:)
57:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
