The <Issue> Element
Description
The collection of issue values. The structure of Index, Share, Stock, Warrant, Bond, Option, Future, Forward, Currency and Convertible all have the same basic structure. You will need to know the exact ticker/exchange combination to retrieve any issue from the Infront Netherlands database, or use a collection containing the wanted issues. In the unlikely event of incomplete database information, you might receive an UnknownIssue.
Note You can always find a specific issue by ticker-type through the XPath expression
/TBMData/Sector/Organisation/[@exchange='...' and Ticker[@type='...' and @id='...']]Note that the ticker information is stored in a separate node, since it is possible to receive tickers of several different ticker types.
<Issue
type =
string
subtype =
string
exchange =
string
id =
integer >
</Issue>
Attributes
| Attribute name | Data type | Description |
|---|---|---|
| type Optional | string |
This attribute occurs when the
<Parameter> "generic-issues" is set,
and all issues are respresented by the tag Issue,
rather than a specialized tag like Share or Stock.
The type attribute can be set to the following values:
share, index, currency, option, warrant, bond,
future, rights, commodity,
interest-rate, structured-product. (The
<UnknownIssue> tag is represented
by the value "unknown".)
|
| subtype Optional | string | This attribute occurs for some instruments in combination with the type attribute and indicates a subdivision of the instrument type. See Instrument SubTypes for more information. |
| exchange Required | string | Note: Although <PrimaryIssue> returns the market code for TBM/TES tickers, issue nodes will return the actual exchange code here. As a consequence, issue nodes and <PrimaryIssue> nodes cannot be matched when using the TBM ticker type classification; they can be matched for any other classification, but of course only if the issue data requested also contains a request for the primary issue data. |
| id Required | integer | The id of an issue node uniquely identifies this node; the id should not be used, but you should check the <Ticker> child nodes to identify the issues. The id is only there to distinguish between issues of the same type from the same exchange. Note: The id attribute is the same as the AUID ticker value. |