EXtensible Markup Language (XML) - Cultural View
EXtensible Markup Language (XML) - Cultural View EXtensible Markup Language (XML) - Cultural View
X-expression 114 X-expression X-expressions are the unification of S-expressions found in the Lisp programming language with XML. X-expressions unify notions of computation with data sharing. XBRLS XBRLS (XBRL Simple Application Profile) is an application profile of XBRL. 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" [1] . XBRL is a general purpose specification, based on the idea that no one is likely to use 100% of the 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 database view but concerned with metadata, not data). 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 development costs. The profile was created by Rene van Egmond and Charlie Hoffman, who was the initial creator of XBRL. It borrows heavily from the US GAAP Taxonomy Architecture. XBRLS Architecture The XBRLS architecture is based on many ideas used by the US GAAP 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 of these limitations placed on XBRL are the following: • Uses no tuples. • Only uses the segment element of the instance context and disallows the use of the scenario element. • Allows only XBRL dimensional information as content for the segment element in the instance context. Furthermore, it requires that every concept (member, primary item) participates in a hypercube and that all hypercubes are closed. • Allows no uses of simple or complex typed members within XBRL Dimensions. • XBRLS never uses the precision attribute, always uses the decimals attribute. • Requires that every measure exists in at least one XBRL Dimension. XBRL Components not used in XBRLS
XBRLS 115 XBRL Specification Instance Context: entity Topic Explanation identifier, entity scheme 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 [Axis]” dimension. The “entity identifier” and “entity scheme” portion of a context should not be used. Rather, the “entity identifier” and “entity schema” are static (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. Instance Context: period Although not required when using XBRLS, it is highly encouraged that the period context be “held Instance (sections 4.7.4 and 4.7.3.2) Context: segments, scenarios Instance Fact Value: precision Taxonomy Elements: tuples Tuples are not allowed. static” or synchronized with an explicit member and that rather XBRL Dimensions be used to articulate this information, perhaps with an XBRLS “Period [Axis]” dimension. Uses XBRL Dimensions to articulate this XBRL quasi dimension. 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. Uses only the decimals attribute, precision must not be used. Taxonomies Weight The weight attribute value of calculations must be either “1” or “-1”, no decimal value between the two is Taxonomies Annotation, Documentation allowed. Each schema and each linkbase must provide documentation that describes the contents of the file that is readable by a computer application. Dimensions Open Hypercubes Open hypercubes are not allowed, only closed hypercubes are allowed. Dimensions notAll Only “all” has-hypercube arcroles are allowed, “notAll” is not allowed Dimensions Typed Members Typed members (simple or complex) are not allowed. External links • XBRL Business Information Exchange [2] • XBRLS: how a simpler XBRL can make a better XBRL [3] • Comprehensive Example [4] • XBRLS - XBRL Made Easy [5] • Data Interactive: An Interview with Charlie Hoffman [6] References [1] XBRL Business Information Exchange (http://xbrl.squarespace.com/xbrls/) website [2] http://xbrl.squarespace.com/xbrls/ [3] http://xbrl.squarespace.com/storage/xbrls/XBRLS-How-simpler-can-be-better-2008-03-11.pdf [4] http://xbrl.squarespace.com//storage/xbrls/XBRLS-ComprehensiveExample-2008-04-18.zip [5] http://www.ubmatrix.com/company/innovation.htm [6] http://hitachidatainteractive.com/2008/04/23/an-interview-with-charlie-hoffman
- Page 67 and 68: Office Open XML file formats 63 ECM
- Page 69 and 70: Office Open XML file formats 65 200
- Page 71 and 72: Office Open XML file formats 67 π
- Page 73 and 74: Office Open XML file formats 69 [6]
- Page 75 and 76: Open XML Paper Specification 71 Ope
- Page 77 and 78: Open XML Paper Specification 73 Gho
- Page 79 and 80: Open XML Paper Specification 75 See
- Page 81 and 82: PCDATA 77 PCDATA PCDATA is a term o
- Page 83 and 84: Portable Application Description 79
- Page 85 and 86: Publishing Requirements for Industr
- Page 87 and 88: QName 83 Example In line two th
- Page 89 and 90: QTI 85 January 2010 2.1 reinstated
- Page 91 and 92: QTI 87 References [1] Effective Pra
- Page 93 and 94: Resource Description Framework 89 R
- Page 95 and 96: Resource Description Framework 91 T
- Page 97 and 98: Resource Description Framework 93 a
- Page 99 and 100: Resource Description Framework 95 s
- Page 101 and 102: Resource Description Framework 97 R
- Page 103 and 104: Reverse Ajax 99 Reverse Ajax Revers
- Page 105 and 106: Root element 101 References [1] The
- Page 107 and 108: Schematron 103 Implementation Schem
- Page 109 and 110: Streaming XML 105 Streaming XML Str
- Page 111 and 112: Unique Particle Attribution 107 Uni
- Page 113 and 114: VTD-XML 109 Location Cache Location
- Page 115 and 116: VTD-XML 111 Areas of Applications G
- Page 117: VTD-XML 113 } } References } } ap.s
- Page 121 and 122: XEE (Starlight) 117 XEE (Starlight)
- Page 123 and 124: XEP 119 External links • XEP on R
- Page 125 and 126: XML 121 Attribute element is Hello,
- Page 127 and 128: XML 123 Comments Comments may appea
- Page 129 and 130: XML 125 Schematron Schematron is a
- Page 131 and 132: XML 127 A pull parser creates an it
- Page 133 and 134: XML 129 Prior to its fifth edition
- Page 135 and 136: XML 131 [27] edited by Sueann Ambro
- Page 137 and 138: XML and MIME 133 External links •
- Page 139 and 140: XML appliance 135 References [1] ht
- Page 141 and 142: XML Catalog 137 Using a Catalo
- Page 143 and 144: XML Certification Program 139 XML M
- Page 145 and 146: XML Certification Program 141 • W
- Page 147 and 148: XML Certification Program 143 [35]
- Page 149 and 150: XML data binding 145 XML data bindi
- Page 151 and 152: XML database 147 • Need not have
- Page 153 and 154: XML database 149 • The State of N
- Page 155 and 156: XML editor 151 map XML elements to
- Page 157 and 158: XML Enabled Directory 153 XML Enabl
- Page 159 and 160: XML Events 155 This design has thre
- Page 161 and 162: XML Literals 157 XML Literals In th
- Page 163 and 164: XML Pretty Printer 159 See also •
- Page 165 and 166: XML schema 161 XML schema languages
- Page 167 and 168: XML Schema Editor 163 Logical View
X-expression 114<br />
X-expression<br />
X-expressions are the unification of S-expressions found in the Lisp programming language with <strong>XML</strong>.<br />
X-expressions unify notions of computation with data sharing.<br />
XBRLS<br />
XBRLS (XBRL Simple Application Profile) is an application profile of XBRL.<br />
XBRLS is designed to be 100% XBRL compliant. The stated goals of XBRLS are "to maximize XBRL's benefits,<br />
reduce costs of implementation, and maximize the functionality and effectiveness of XBRL" [1] . XBRL is a general<br />
purpose specification, based on the idea that no one is likely to use 100% of the components of XBRL in building<br />
any one solution. XBRLS specifies a subset of XBRL that is designed to meet the needs of most business users in<br />
most situations, and offers it as a starting point for others. This approach creates an application profile of XBRL<br />
(equivalent to a database view but concerned with metadata, not data).<br />
XBRLS is intended to enable the non-XBRL expert to create both XBRL metadata and XBRL reports in a simple<br />
and convenient manner. At the same time, it seeks to improve the usability of XBRL, the interoperability among<br />
XBRL-based solutions, the effectiveness of XBRL extensions and to reduce software development costs.<br />
The profile was created by Rene van Egmond and Charlie Hoffman, who was the initial creator of XBRL. It borrows<br />
heavily from the US GAAP Taxonomy Architecture.<br />
XBRLS Architecture<br />
The XBRLS architecture is based on many ideas used by the US GAAP Taxonomy Architecture. The intent of the<br />
XBRLS architecture is to make it easier for business users to make use of XBRL, to make it easier for software<br />
vendors to support XBRL, and to safely use the features of XBRL. XBRLS is a subset of what is allowed by the<br />
complete XBRL Specification. Examples of these limitations placed on XBRL are the following:<br />
• Uses no tuples.<br />
• Only uses the segment element of the instance context and disallows the use of the scenario element.<br />
• Allows only XBRL dimensional information as content for the segment element in the instance context.<br />
Furthermore, it requires that every concept (member, primary item) participates in a hypercube and that all<br />
hypercubes are closed.<br />
• Allows no uses of simple or complex typed members within XBRL Dimensions.<br />
• XBRLS never uses the precision attribute, always uses the decimals attribute.<br />
• Requires that every measure exists in at least one XBRL Dimension.<br />
XBRL Components not used in XBRLS
Change language