The mappingtool.properties file includes these properties:
The prefix or “short name” is used in the Disclosure Management Mapping Tool user interface and instance documents. The prefix value must have these characteristics:
Has a unique value—two or more taxonomies should not use the same prefix
Starts with a letter or underscore character
Contains no spaces
Is short because it is used repeatedly within instance documents
The taxonomy entry point is the path to a taxonomy's xsd file, relative to the DISCMAN_INSTANCE/XbrlFiles folder.
Taxonomies can have multiple entry points. Administrators control which entry points are registered and shown by the Disclosure Management Mapping Tool. For example, the US GAAP taxonomy has five entry points, but an administrator can choose to register only three. The Web site from which the taxonomy is downloaded usually contains details about its entry points.
The path to the xsd file should use the “/” character as a path separator. Alternately a double “\\” can be used, but not a single “\”, for example:
label_# is the user-readable label associated with the entry point.
The label is shown in the Disclosure Management Mapping Tool user interface.
Each entry point value should have a corresponding label entry.
Administrators can indicate the extended link label value to be shown for extended links in the taxonomy. Two values are available: “title” or “definition”. The extended link value is defined in the extLinkLabel_1=[definition][title] property of the mappingtool.properties file. When one value is not available, the other is used. For example, when the value is set to “definition” and the taxonomy has only title labels, titles are used. This property is optional. If the property is not provided, the default value is “title”.
The schema name (schemaRef property) in the instance document is determined by the schemaRef_# value specified in mappingtool.properties file. Because this information is not supplied by the taxonomy itself, the administrator must provide the schemaRef property. The pattern for this property is: schemaRef_#=[SomeTaxonomyURI]
Note the following when specifying the schemaRef property:
The schemaRef property is normally a URI to the entry point of the taxonomy referenced by an instance document. The SEC requires that the schemaRef property point only to the taxonomy file name only (see. “orcl-20100831.xsd”.) However, the UK--IFRS requires that a full URI, (for example, http://www.xbrl.org/uk/ifrs/core/2009-09-01/uk-ifrs-full-2009-09-01.xsd") be used.
This property is optional. If it is not provided, the schema value from the correspondingentryPoint_#" property is used.
Disclosure Managements supports multiple schema reference (SchemaRef) declarations in an instance document. For example, the following schema reference declarations can be specified in the mappingtool.properties file using the schemaRef_# parameter and spaces as separators: Note that the three schemaRef_# values are separated by spaces.
taxonomy_1.schemaRef_1=http://www.svs.cl/cl/fr/ci/2011-04-26/cl-ci_shell_2011-04-26.xsd http://www.svs.cl/cl/fr/ci/2011-04-26/cl-ci_ias-1_2010-04-30/cl-ci_ias-1_2010-04-30_role-210000.xsd http://www.svs.cl/cl/fr/ci/2011-04-26/cl-ci_ias-1_2010-04-30/cl-ci_ias-1_2010-04-30_role-110000.xsd
Thepackage_# property determines if the taxonomy files are included when a user select the “Generate XBRL” option from Microsoft Excel or Word. When this property is enabled,Disclosure Management produces the XBRL instance document on the Disclosure Management server and includes the additional documents within the compressed file (with a "DMR" extension). The .DMR file is then serialized to the client machine and saved to the file system (as indicated by the user)..When the package property is “false”Disclosure Management does not include the dependent taxonomy files within the DMR file. Disclosure Management-includes only the XBRL instance document and a few other proprietary files.
The package_# property accepts a boolean flag value:
A “true” boolean value indicates that the taxonomy files is packaged.
A “false” boolean value indicates that the taxonomy file is not packaged.
This property is optional; if it is not provided, “true” is used as the default.
The "formatted" property is used to automatically apply a "rich text" format to specified data types.
Each data type must be space separated and represented the following way: "xsd_target_namespace#dataType". The pattern for the properties is: taxonomy_#.formatted=[Space separated data types]
For example to indicate that concepts which are of the textBlockItemType data type always use "rich text" formatting for "taxonomy_1", add the following entry: taxonomy_1.formatted=http://xbrl.us/us-types/2009-01-31#textBlockItemType
This property is optional. If it is not provided, the "plain text" format is always used.
The "unformatted" property is useful to automatically apply a "plain text" format to specified data types.
Each data type must be space separated, and represented in the following way: "xsd_target_namespace#dataType". The pattern for the properties is: taxonomy_#.formatted=[Space separated data types]
For example, to indicate that concepts which are of the textBlockItemType data type always use "plain text" formatting for "taxonomy_1", add the following entry: taxonomy_1.unformatted=http://xbrl.us/us-types/2009-01-31#textBlockItemType
This property is optional. If it is not provided, the "plain text" format is used.
You can enable or disable override functionality for a particular concept type in the mappingtool.properties file. The “overridable” and “unoverridable” properties govern whether it is possible to override all facts based on concepts of a specified type and its derived types on the Review tab.
Each item of the list in the mappingtool.properties file must be in the form of: <target-name-space>#<dataTypeName>
You do not have to enumerate all the data type for which the override setting is enabled. Because data types are usually organized hierarchically, specify the override setting for the common parent type. For example, you could enable the override setting for the decimalItemType and its children by entering: taxonomy_1.overridable_1=http://www.xbrl.org/2003/instance#decimalItemType
In this case, all facts based on concepts of all types inherited from decimalItemType (for example numeric, monetary, or volumeItemType) are overridable.
You can also set global override settings in addition to taxonomy specific settings, for example:global.overridable=http://www.xbrl.org/2003/instance#decimalItemType http://www.xbrl.org/2003/instance#booleanItemType http://www.xbrl.org/2003/instance#dateItemType
The unoverridable setting allows you to disable the ability to override types in the hierarchy. For example if you want to disable the ability to override formatted items in the US GAAP extension, you would specify: taxonomy_1.unoverridable_1= http://xbrl.us/us-types/2009-01-31#textBlockItemType
A list of all element types and their derived types for US GAAP are as follows:
Table 2. nonNumeric-2009-12-16.xsd
| nonNumeric-2009-12-16.xsd | |
|---|---|
| URL: http://www.xbrl.org/dtr/type/nonNumeric-2009-12-16.xsd | |
| Namespace URI = http://www.xbrl.org/dtr/type/non-numeric | |
| Namespace prefix: nonnum | |
| nonnum:domainItemType | xbrli:stringItemType |
| nonnum:escapedItemType | xbrli:stringItemType |
| nonnum:xmlNodesItemType | nonnum:escapedItemType |
| nonnum:xmlItemType | nonnum:xmlNodesItemType |
| nonnum:textBlockItemType | nonnum:xmlNodesItemType |
Table 3. nonNumeric-2009-12-16.xsd
| nonNumeric-2009-12-16.xsd | |
|---|---|
| URL: http://www.xbrl.org/dtr/type/nonNumeric-2009-12-16.xsd | |
| Namespace URI = http://www.xbrl.org/dtr/type/non-numeric | |
| Namespace prefix: nonnum | |
| nonnum:domainItemType | xbrli:stringItemType |
| nonnum:escapedItemType | xbrli:stringItemType |
| nonnum:xmlNodesItemType | nonnum:escapedItemType |
| nonnum:xmlItemType | nonnum:xmlNodesItemType |
| nonnum:textBlockItemType | nonnum:xmlNodesItemType |
Table 4. us-types-2011-01-31.xsd
| us-types-2011-01-31.xsd | |
|---|---|
| URL: http://xbrl.fasb.org/us-gaap/2011/elts/us-types-2011-01-31.xsd | |
| Namespace URI: http://fasb.org/us-types/2011-01-31 | |
| Namespace prefix: us-types | |
| us-types:FederalHomeLoanBankAdvancesGeneralDebtObligationsDisclosures-InterestRateTypeItemType | xbrli:stringItemType Enumeration –“Floating” or “Fixed” |
| us-types:FederalHomeLoanBankAdvancesStateFHLBBank-InterestRateTypeItemType | xbrli:stringItemType Enumeration –“Floating” or “Fixed” |
| us-types:MalpracticeInsurance-OccurrenceOrClaims-madeItemType | xbrli:stringItemType Enumeration - “Occurrence ” or “Claims-made” |
| us-types:MalpracticeInsurance-RetrospectivelyRatedItemType | xbrli:stringItemType Enumeration –“Yes” or “No” |
| us-types:dateStringItemType | xbrli:normalizedStringItemType |
| us-types:durationStringItemType | xbrli:normalizedStringItemType |
| us-types:perUnitItemType | xbrli:decimalItemType |
| us-types:boeItemType | xbrli:decimalItemType |
| us-types:yesNoItemType | xbrli:tokenItemType Enumeration –“Yes” or “No” |
| us-types:restrictedInvestmentItemType | xbrli:tokenItemType Enumeration –“Restricted Investment”,“ Restricted Investment Exempt from Registration”,“ Restricted Investment Not Exempt from Registration” |
| us-types:investmentOnLoanForShortSalesItemType | xbrli:tokenItemType Enumeration–“Investment on Loan”, “'Entire Investment on Loan, Partial Investment on Loan” |
| us-types:investmentPledgedItemType | xbrli:tokenItemType Enumeration–“Investment Pledged”, “Entire Investment Pledged”,“ Partial Investment Pledged” |
Table 5. dei-2011-01-31.xsd
| dei-2011-01-31.xsd | |
|---|---|
| URL: http://taxonomies.xbrl.us/us-gaap/2009/non-gaap/dei-2009-01-31.xsd | |
| Namespace URI: http://xbrl.sec.gov/dei/2011-01-31 | |
| Namespace prefix: dei | |
| dei: yesNoItemType | xbrli:tokenItemType Enumeration–“Yes”’ or “No” |
| dei: filerCategoryItemType | xbrli:tokenItemType Enumeration–“Large Accelerated Filer”, “Accelerated Filer”, “Non-accelerated Filer, Smaller Reporting Company” |
| dei: currencyItemType | xbrli:tokenItemType Restriction: 3 letter code, all uppercase |
| dei: countryItemType | xbrli:tokenItemType Restriction: 2 characters, 1st is an uppercase letter, 2nd is an upper case letter or digit |
| dei: nineDigitItemType | xbrli:tokenItemType Restriction: 9 digits |
| dei: centralIndexKeyItemType | xbrli:tokenItemType Restriction: 10 digits |
| dei: fiscalPeriodItemType | xbrli:tokenItemType Enumeration:– “FY”, “Q1”, “Q2”, “Q3”, “Q4”, “H1”, “H2”, “M9”, “T1”, “T2”,“ T3”, “M8”, “CY” |
| dei: submissionTypeItemType | xbrli:tokenItemType Enumeration–“10-K”, “10-KT”, “10-Q”,“ 10-QT”,“ 20-F”, “20-FT”, “40-F”, “485BPOS”, “497”“, 6-K”,“ 8-K”,“ F-1”,“ F-3”, “F-4,” “F-9”, “F-10,” “N-CSR”, “N-CSR”, “N-Q, ”, “POS AM”, “S-1”, “S-3,” “S-4”, “S-11”,“ Other”,“ N-1A”, “NCSR,”“ 10” |
A list of all element types and their derived types for UK GAAP are as follows:
Table 6. us-types-2011-01-31.xsd
| uk-types-2009-09-01.xsd | |
|---|---|
| URL: http://www.xbrl.org/uk/all/types/2009-09-01/uk-types-2009-09-01.xsd | |
| Namespace URI: : http://www.xbrl.org/uk/all/types/2009-09-01 | |
| Namespace prefix: uk-types | |
| uk-types:entityAccountsTypeItemType | xbrli:stringItemType Enumeration–“Group consolidated accounts”, “Company accounts”“, Group consolidated and company accounts”,“ Other accounts type” |
| uk-types:percentItemType | xbrli:pureItemType |
| uk-types:reportPeriodItemType | xbrli:tokenItemType Enumeration–“FY”, “Q1”,“Q2”, “Q3”, “Q4”, “H1”, “H2”, “CY”, ‘“Other”’ |
| uk-types:entityFormItemType | xbrli:stringItemType Enumeration–“Public Limited Company”, “Private Limited Company”, “Limited Liability Partnership”, “Other” |
| uk-types:fixedItemType | xbrli:stringItemType |
| uk-types:domainItemType | xbrli:stringItemType |
| uk-types:perShareItemType | xbrli:decimalItemType |
Use the addlinkbases property to add documentation for concepts in extension taxonomies. The documentation refers to the actual meaning of the concept being created. The addlinkbases property is set by specifying a space delimited list of one or more linkbase(s), which you attach to a registered taxonomy. While the linkbases listed do not have to be for documentation only, it is the only resource supported at this time.
The most common documentation that SEC filers might attach to their extension taxonomies are:
Table 7. Documentation linkbases
| Documentation Linkbase | File Location |
|---|---|
| 2011 US-GAAP | http://xbrl.fasb.org/us-gaap/2011/elts/us-gaap-doc-2011-01-31.xml |
| 2011 DEI | http://sec-2011-01-31/dei/2011/dei-doc-2011-01-31.xml |
| 2009 US-GAAP | http://taxonomies.xbrl.us/us-gaap/2009/elts/us-gaap-doc-2009-01-31.xml |
| 2009 DEI | http://taxonomies.xbrl.us/us-gaap/2009/non-gaap/dei-doc-2009-01-31.xml |
The linkbases in this are not exclusive. There are several additional documentation linkbases available for the US-GAAP taxonomy. The addlinkbases property is case-sensitive (the file name should only be in lowercase characters). Additionally, the Disclosure Management service is normally restarted when the mappingtool.properties file is modified.
In the following example, the taxonomy "orcl-20101130" is a 2009 US-GAAP extension taxonomy. Two documentation linkbases are attached including one for the US-GAAP concepts and one for the DEI (document & entity information) concepts Adding the two linkbases shows the documentation (where available) when a US-GAAP or a DEI concept is selected in the mapping tool. Note that the two linkbases are space separated:
taxonomy_1.prefix=Oracle
taxonomy_1.addlinkbases=http://taxonomies.xbrl.us/us-gaap/2009/elts/us-gaap-doc-2009-01-31.xml
http://taxonomies.xbrl.us/us-gaap/2009/non-gaap/dei-doc-2009-01-31.xml
taxonomy_1.label_1=Oracle 10-Q 20101130
taxonomy_1.entryPoint_1=orcl-20101130/abc-20101130.xsd