combined relations for ONE extended linkrole and
has hypercube (any, all or choice) dimensional arcs
(max contributing networks: extrole+any, extrol+all, extrole+choice)
for one primary item.
Interface for all standard xbrl concept types in the taxonomy domain
All item types MUST be one of the types listed in the spec or derived from one of them by restriction.
The context element contains information about the entity being described, the reporting period and
the reporting scenario, all of which are necessary for understanding a business fact captured as an
XBRL item.
Create a supported role object that can perform validation of instances and or taxonomies according to the rules defined in the specification for the role.
Create a fact with plain-as-possible arguments and
return the id in case the fact is a tuple (or string root)
so it can be used to create other child facts
Dimensional DTS that can discover all components for a dimensional taxonomy
on top of the primairy taxonomy components
and can create the hypercubes, dimensions, domains, domainmembers, DSR's that
may be used to create or validate instance documents regarding the XDT spec
extends the standard DTS
overrides the discover networks to build the XDT domain
overrides the validate instance to validate with the XDT domain
overrides the validate to validate the XDT domain
adds methods to obatin the XDT components
Copyright 2006 J2R BV, The Netherlands.
networks of hypercubes with dimensions with domains with domainmembers
that can be constructed for each relationship in a network
by following the standard XBRL networks of relationships
and extended them with the relationships defined by the arcs that
1. are defined in networks of roles that apear in the targetRoles of the main DRS arc
2. and have on their from side a target that is on the to side of the main DRS arc
A DRS is rooted by an arc from a primary item concept.
Use the parent to discover the whole DTS
Taxonomy schemas in the DTS are those:
1. referenced directly from an instance document using the schemaRef, roleRef or arcroleRef element.
Discover the networks of nodes/concepts that are connected by the arcs in this DTS:
check the networks with the cycles allowed attribute on the arcRoleType elements
The concepts that are related do not know they are!
The xbrldi:Member element is a simple-type link whose content
MUST be a member of the domain of the explicit dimension to
which its xlink:href attribute refers.
find domainmember relations for the given baseset
If an argument is null, results are not filtered on that argument and all members in a population match.
find explicit dimension domain relations for the given baseset
If an argument is null, results are not filtered on that argument and all members in a population match.
find relations between the hypercube and dimension in the baseset for the primary item
If an argument is null, results are not filtered on that argument and all members in a population match.
Find the networks in which the given concept is used for the given arguments,
arc local name and namespace, arcRole, link local name and namespace, linkRole.
Find the networks in which the given concept is used for the given arguments,
arc local name and namespace, arcRole, link local name and namespace, linkRole and filters with sub uris.
Find the networks constructed with the given arguments,
arc local name and namespace, arcRole, link local name and namespace, linkRole and filters with sub uris.
find children concepts (to side on arc) for the given parentconcept (from side on arc)
If an argument is null, results are not filtered on that argument and all members in a population match.
find dimension used in the given hypercube in the baseset for the primary item
If an argument is null, results are not filtered on that argument and all members in a population match.
find dimensions that use the default domainmember
If an argument is null, results are not filtered on that argument and all members in a population match.
find related domainmembers for the given baseset
If an argument is null, results are not filtered on that argument and all members in a population match.
find related explicit dimensions for the given baseset
If an argument is null, results are not filtered on that argument and all members in a population match.
find related explicit domains for the given baseset
If an argument is null, results are not filtered on that argument and all members in a population match.
find hypercubes that use the given dimension in baseset for the given primary item
If an argument is null, results are not filtered on that argument and all members in a population match.
find hypercubes related to the given primary item
If an argument is null, results are not filtered on that argument and all members in a population match.
find parent concepts (from side on arc) for the given childconcept (to side on arc)
If an argument is null, results are not filtered on that argument and all members in a population match.
find primary items that use the given hypercube
If an argument is null, results are not filtered on that argument and all members in a population match.
Find the role uris in whose networks the given concept is used for the given
link local name and filters with sub uris. return a list with the found uris
While tuples deal with certain regularly-structured associations between elements that might appear
in an XBRL instance, many documents include irregularly structured associations between facts.
Initialize this document with XBRL content from the data found in the data byte array
and set its id with the given systemid while perfoming XML schema validation.
Initialize this document with XBRL content from the data found in the data stream
and set its id with the given systemid while perfoming XML schema validation.
Initialize this document with XBRL content from the data found at the location
indicated by the given systemid without perfoming XML schema validation.
returns map that can be used as model for selecting valid (dim/dom)n
combinations for prim items
NOTE, allowed or disallowed is per scenario OR per segment
get baseset
1) as declaredBaseSetWithDRS-es for the primaryItem
2) as contributingToBaseSetWithDRS-es for each primary Item descendant that could be found in the DDTS
NOTE: contributingDRS-es may only be used (in ordered fashion)
when there are no declared DRS-es!
Get this elements' DTS by walking up the tree of ancestors from it self onwards
to see if there are InstanceDocumentLink implementors that can return the
requested DTS.
Get the prefix the namespace is known by; if not here, check the parent (if not null or equal to this
Attributes do not have a default namespace, so when the argument is null
the return value is null.
getUnitRef() -
Method in interface com.batavia.xbrl.instance.Item
The Unit ref attribute value identifies the Unit for this item.
getUnits() -
Method in interface com.batavia.xbrl.instance.Xbrl
Get the unit elements that are contained by this XBRL mapped by their ID attributes
fully qualified name values (prefix:id)
NOTE (illegal) identical ID's on xbrli:unit elements will cause only one to be visible in this map.
getUri() -
Method in interface com.batavia.xbrl.conformance.TestCase
wraps abstract item concept and arc that refs it
have dimensions (explicit or implicit) based on hypercube-dimension in linkabse
hypercubes are on the to end of arcs with one of the has hypercube roles
http://xbrl.org/int/dim/arcrole/all
http://xbrl.org/int/dim/arcrole/any, and
http://xbrl.org/int/dim/arcrole/choice.
isInferred() -
Method in interface com.batavia.xbrl.instance.Fact
Facts that were inferred for the PTVI file DO NOT contribute in calculations
since the original instance cannot bind the instance fact to the summation item
Although each taxonomy defines a single set of elements representing a set of business reporting concepts
, the human-readable XBRL documentation for those concepts, including labels (strings used as
human-readable names for each concept) and other explanatory documentation, is contained in a resource
element in the label linkbase.
The [XLINK] specification defines linkbases in the following way:
“documents containing collections of inbound and third-party links are called link databases,
or linkbases” [XLINK] (http://www.w3.org/TR/2001/REC-xlink-20010627/#dt-linkbase).
The extended links in a taxonomy provide additional information about concepts by expressing
relationships between concepts (inter-concept relationships) or associating concepts with documentation
about their meaning.
Implementation should be configurable to handle
different log levels (log only msgs on and below configured level) and
different packageNames (log only msgs from configured packageNames) and
different types (log each type to its own file)
place the msgs in a collection and handle the log msgs in a separate thread
LOGTYPE_ERROR -
Static variable in interface com.batavia.xbrl.io.log.Log
LOGTYPE_EVENT -
Static variable in interface com.batavia.xbrl.io.log.Log
LOGTYPE_USER -
Static variable in interface com.batavia.xbrl.io.log.Log
args are in this order compareReportFilename and instance file names
output is csv file
context.entity.scheme;context.entity.identifier;context.entity.segment;context.scenario;context.period;qNamePath;value1;value...n
one arg with URI for schema entry point of DTS
example:
http://www.xbrl-ntp.nl/nltaxonomie-v1-0-20061017/taxonomy/report/bd/rpt-bd-vennootschapsbelasting-2005.xsd
create an absolute reference to the location of the referred location knowing that it was found in the location origin
which is known to be a directory.