XBRL linkbase content, as sub-classes of LinkbaseElem, which is an arbitrary element in a linkbase.
See xbrl-linkbase-2003-12-31.xsd (for standard XBRL).
The LinkbaseElem type hierarchy also knows about generic links and generic label and reference links in particular.
For other generic link content, the user may want to define own (implicit) classes for ease of use, taking the
data of the underlying LinkbaseElem, such as a GenericResource.
Moreover, some LinkbaseElem objects such as footnotes occur in XBRL instances, not in XBRL taxonomies. The user may
want to make it easy to populate the specific LinkbaseElems from those elements. This should be quite easy if
for XBRL instances the "same elements" are used, so either they also use DocawareBridgeElem instances, or they use
backing element implementations that are compatible with the DocawareBridgeElem abstraction.
XBRL linkbase content, as sub-classes of
LinkbaseElem
, which is an arbitrary element in a linkbase. See xbrl-linkbase-2003-12-31.xsd (for standard XBRL).The
LinkbaseElem
type hierarchy also knows about generic links and generic label and reference links in particular. For other generic link content, the user may want to define own (implicit) classes for ease of use, taking the data of the underlying LinkbaseElem, such as a GenericResource.Moreover, some
LinkbaseElem
objects such as footnotes occur in XBRL instances, not in XBRL taxonomies. The user may want to make it easy to populate the specific LinkbaseElems from those elements. This should be quite easy if for XBRL instances the "same elements" are used, so either they also useDocawareBridgeElem
instances, or they use backing element implementations that are compatible with theDocawareBridgeElem
abstraction.