--additional-dts-entry-point = FILE
Forces the specified entry-point file to be included in the DTS discovery process. Add the option multiple times to specify more than one entry point.
|
--ct-restrict-mode = 1.0|1.1|default
Specifies how to check complex type restrictions. A value of 1.0 checks complex type restrictions as defined in the XSD 1.0 specification—even in XSD 1.1 validation mode. A value of 1.1 checks complex type restrictions as defined in the XSD 1.1 specification—even in XSD 1.0 validation mode. A value of default checks complex type restrictions as defined in the XSD specification of the current validation mode (1.0 or 1.1). The default value is default.
|
--deduplicate = true|false
Enables de-duplication according to the Handling Duplicate Facts in XBRL and Inline XBRL 1.0 specification. Removes facts that are (i) complete duplicates, (ii) consistent duplicates (by definition these are numeric facts; the most accurate of the duplicates is retained for processing). Inconsistent and multi-language duplicates are not affected by this option. Default value is false.
Note: Boolean option values are set to true if the option is specified without a value.
|
--dimensions = true|false
Enables XBRL Dimension 1.0 extensions. Default is true.
Note: Boolean option values are set to true if the option is specified without a value.
|
--dts = FILE
Preloads the DTS entry point given in FILE, and uses it for the validation of instance files. Add the option multiple times to specify more than one entry point. Entry points in instance files will be ignored. The command is used to batch validate multiple instance files that all refer to the same taxonomy. The --dts option instructs the Raptor engine to load the DTS only a single time—and not for each instance in the file list. (A file list is given either on the CLI, or in a text file that is indicated as a file list by setting the --listfile option to true.) If an instance file in the file list references a different taxonomy, then a warning is issued. This command can greatly speed up validation time when validating many small instance files each that have a large supporting DTS; it provides no advantage when validating a single instance file.
|
--essence-alias-checks = true|false
Enables reporting of essence-alias inconsistencies. Default value is true.
Note: Boolean option values are set to true if the option is specified without a value.
|
--generic-links = true|false
Enables the XBRL Generic Links 1.0 extension. Default value is true.
Note: Boolean option values are set to true if the option is specified without a value.
|
--generic-preferred-label = true|false
Enables the XBRL Generic Preferred Label 1.0 extension. Default value is true.
Note: Boolean option values are set to true if the option is specified without a value.
|
--inconsistencies-limit = N | unlimited
Specifies the XBRL inconsistencies limit, with values being in the range 1-65535 or unlimited. Processing continues if the limit is reached, but further inconsistencies are not reported. The default value is 100.
|
--preload-xbrl-schemas = true|false
Preloads schemas of the XBRL 2.1 specification. Default is true.
Note: Boolean option values are set to true if the option is specified without a value.
|
--report-duplicates = all|complete|consistent|inconsistent|inconsistent-numeric|inconsistent-non-numeric|multi-language
Enables the reporting of duplicate facts of the specified duplicate class. Add the option multiple times to specify more than one duplicate class. There is no default value. If no value is specified, then no check for duplicates is carried out.
|
--report-duplicates-severity = info|warning|inconsistency|error
Specifies whether the detected duplicate facts should be reported as errors or warnings. If they are reported as errors, then the XBRL validation of the instance will fail. The default is error.
|
--report-import-namespace-mismatch-as-warning = true|false
Downgrades namespace or target-namespace mismatch errors when importing schemas with xs:import from errors to warnings. The default value is false.
Note: Boolean option values are set to true if the option is specified without a value.
|
--requires-element-checks = true|false
Enables reporting of requires-element inconsistencies. The default value is true.
Note: Boolean option values are set to true if the option is specified without a value.
|
--schema-imports = load-by-schemalocation | load-preferring-schemalocation | load-by-namespace | load-combining-both | license-namespace-only
Specifies the behaviour of xs:import elements, each of which has an optional namespace attribute and an optional schemaLocation attribute: <import namespace="someNS" schemaLocation="someURL">. The option specifies whether to load a schema document or just license a namespace, and, if a schema document is to be loaded, which information should be used to find it. Default: load-preferring-schemalocation.
The behavior is as follows:
•load-by-schemalocation: The value of the schemaLocation attribute is used to locate the schema, taking account of catalog mappings. If the namespace attribute is present, the namespace is imported (licensed). •load-preferring-schemalocation: If the schemaLocation attribute is present, it is used, taking account of catalog mappings. If no schemaLocation attribute is present, then the value of the namespace attribute is used via a catalog mapping. This is the default value. •load-by-namespace: The value of the namespace attribute is used to locate the schema via a catalog mapping. •load-combining-both: If either the namespace or schemaLocation attribute has a catalog mapping, then the mapping is used. If both have catalog mappings, then the value of the --schema-mapping option (XBRL option and XML/XSD option) decides which mapping is used. If no catalog mapping is present, the schemaLocation attribute is used. •license-namespace-only: The namespace is imported. No schema document is imported.
|
--schema-mapping = prefer-schemalocation | prefer-namespace
If schema location and namespace are both used to find a schema document, specifies which of them should be preferred during catalog lookup. (If either the --schemalocation-hints or the --schema-imports option has a value of load-combining-both, and if the namespace and URL parts involved both have catalog mappings, then the value of this option specifies which of the two mappings to use (namespace mapping or URL mapping; the prefer-schemalocation value refers to the URL mapping).) Default is prefer-schemalocation.
|
--schemalocation-hints = load-by-schemalocation | load-by-namespace | load-combining-both | ignore
Specifies the behavior of the xsi:schemaLocation and xsi:noNamespaceSchemaLocation attributes: Whether to load a schema document, and, if yes, which information should be used to find it. Default: load-by-schemalocation.
•The load-by-schemalocation value uses the URL of the schema location in the xsi:schemaLocation and xsi:noNamespaceSchemaLocation attributes in XML or XBRL instance documents. This is the default value. •The load-by-namespace value takes the namespace part of xsi:schemaLocation and an empty string in the case of xsi:noNamespaceSchemaLocation and locates the schema via a catalog mapping. •If load-combining-both is used and if either the namespace part or the URL part has a catalog mapping, then the catalog mapping is used. If both have catalog mappings, then the value of the --schema-mapping option (XBRL option and XML/XSD option) decides which mapping is used. If neither the namespace nor URL has a catalog mapping, the URL is used. •If the option's value is ignore, then the xsi:schemaLocation and xsi:noNamespaceSchemaLocation attributes are both ignored.
|
--summation-item-checks = true|false
Enables reporting of summation-item inconsistencies. The default value is true.
Note: Boolean option values are set to true if the option is specified without a value.
|
--taxonomy-package = FILE
Specifies the absolute path to an additional taxonomy package as described in the Taxonomy Package 1.0 and Taxonomy Packages 1.0 working drafts. The value of FILE gives the location of the taxonomy package. Add the option multiple times to specify more than one taxonomy package.
|
--taxonomy-packages-config-file = FILE
Specifies the path to the TaxonomyPackagesConfig.json file, which is used to load XBRL taxonomy packages. The file's convenience is that it serves as a catalog of taxonomy packages. The structure of the JSON file is as in the example listing below. The value of the uri key gives the location of the package. The active key (of a set of packages) switches on usage of those packages.
{"taxonomies":
{"EIOPA Solvency II XBRL Taxonomy 2.1.0":
{"packages":[
{"uri":"C:\\test\\XBRL\\EIOPA_SolvencyII_XBRL_Taxonomy_2.1.0.zip"},
{"uri":"C:\\test\\XBRL\\AdditionalTestPkg.zip"}
],"active":true
},"Test Taxonomy":
{"packages":[{"uri":"C:\\test\\XBRL\\test.zip"}],"active":true
}
}
}
|
--treat-custom-role-errors-as-warnings = true|false
Reports non-critical XBRL errors related to custom role/arcrole types (for example, missing roleRefs) as warnings. Default value is false.
Note: Boolean option values are set to true if the option is specified without a value.
|
--treat-inconsistencies-as-errors = true|false
Causes XBRL validation to fail if the file contains any inconsistency as defined by the XBRL 2.1 specification. Default value is false.
Note: Boolean option values are set to true if the option is specified without a value.
|
--treat-invalid-use-of-standard-role-as-warning = true|false
Specifies whether the invalid use of standard roles should be reported only as a warning. Default value is false.
Note: Boolean option values are set to true if the option is specified without a value.
|
--uri-transformation = none|make-absolute|make-relative|keep-relative
Specifies how URIs should written to the generated XBRL document.
•none: Copy URI verbatim to target document •make-absolute: Make any relative URIs absolute by resolving against the in-scope base URI at the respective element in the input document. For example: if the input file is c:\test\inlinexbrl.xhtml, and it contains a relative reference to a schema, schemas\schema.xsd, then the relative reference would be resolved to: c:\test\schemas\schema.xsd. Note that xml:base attributes in the input document can change the base URI. •make-relative: If possible, make any absolute and relative URIs relative to the output document (otherwise write the resolved absolute URI) •keep-relative: If possible, make only the relative URIs relative to the output document (and copy any absolute URI)
|
--utr-file = FILE
Specifies the path to the Units Registry file. The default is: http://www.xbrl.org/utr/utr.xml.
|
--utr-status = PWD|CR|REC|NIE|PROPOSED|IWD|ACK|RR
Enables support of unit definitions with the given status in the Units Registry. Add the option multiple times to specify more than one unit status. Default is REC.
|
--validate-dts-only = true|false
The DTS is discovered by starting from the XBRL instance document. All referenced taxonomy schemas and linkbases are discovered and validated. The rest of the XBRL instance document is ignored. Default value is false.
Note: Boolean option values are set to true if the option is specified without a value.
|
--xinclude = true|false
Enables XML Inclusions (XInclude) support. Default value is false. When false, XInclude's include elements are ignored.
Note: Boolean option values are set to true if the option is specified without a value.
|
|
