XML Tag : event www.recognia.com
<event type="">

Attributes

Name Type Value Description
type String

The schema of the XML block for the event. The valid schemas are:

Value Description
standard

Standard event data.
summary

Standard event data minus event symmetry and price other than close and volume.

Contains the data for a technical event. This block does not contain enough information to mark up a chart with the lines for the event. This block can be used to display details about the event.

Child tags

<breakout_price>

The breakout price is the price which needed to be crossed in order to trigger or confirm the event.


<class>

The class for the event. Technical events are placed into one of four classes:

Value Description
C

Classic Patterns
S

Short-term Patterns
I

Indicator
O

Oscillator

<confirmation_type>

The Confirmation Type is the method of confirmation. Valid Confirmation Types are:

Value Description
C

Close Price
3

Price bar penetration of at least 3%
P

Penetration
D

Date
N

None
U

Unknown

<confirmed_timestamp>

The timestamp when the event was confirmed. All timestamps are of the form: YYYY-MM-DD-HH.MM.SS.mmmmmm. For daily events, the HH.MM.SS.mmmmmm is always 00.00.00.000000. The <confirmed_timestamp> tag is deprecated; use the <end_date> tag instead.


<consensus_rating>

The Recognia Consensus Rating. This is a number [-100,100] that measures how closely the event matches the textbook definition of the event.


<duration>

The duration of the event in <price_period> time periods.


<end_date>

The date for the end of the event. All dates are of the form: YYYY-MM-DD


<end_timestamp>

The timestamp for the end of the event. All timestamps are of the form: YYYY-MM-DD-HH.MM.SS.mmmmmm. This tag is deprecated; use <end_date> instead.


<event_type_id>

Id number for the event type. See Event Types for a list of the currently recognized events.


<event_type_name>

Event Type Name. This is included with the event block in order to save you having to call the eventtype API command with the <event_type_id> simply to get the event name.


<event_type_specific>

Some event types have unique characteristics. These characteristics will be included as child tags of this tag. The following event types (<event_type_id>) have event specific characteristics:

Value Description
13

Value Description
left_shoulder_height

The height of the left shoulder
neckline_slope

The normalized slope of the neckline
right_shoulder_height

The height of the right shoulder
significant_pivot_count

There are three <significant_pivot_count> tags, one for the three regions of a Head and Shoulders pattern. There is a region attribute for the tag which indicates which region the count is for. The possible values for the attribute are: LEFT_SHOULDER, RIGHT_SHOULDER, and HEAD.

The tag holds a count of the number of significant pivots in the region. This count can be used as a measure of how closely the prices follow the pattern lines in the region.

14

Value Description
left_shoulder_height

The height of the left shoulder
neckline_slope

The normalized slope of the neckline
right_shoulder_height

The height of the right shoulder
significant_pivot_count

There are three <significant_pivot_count> tags, one for the three regions of a Head and Shoulders pattern. There is a region attribute for the tag which indicates which region the count is for. The possible values for the attribute are: LEFT_SHOULDER, RIGHT_SHOULDER, and HEAD.

The tag holds a count of the number of significant pivots in the region. This count can be used as a measure of how closely the prices follow the pattern lines in the region.

1000

A single <moving_average> tag that contains the moving average that was crossed. The only valid moving averages are: 21, 50 and 200.
1001

Two <moving_average> tags that contain the two moving averages that crossed. The only valid moving averages are: 21, 50, 200. Note that you should sort the two moving averages (lowest first) before presenting them in order to make it easier to understand.
1002

Three <moving_average> tags that contain the three moving averages that crossed. The only valid moving averages are: 4, 9, 18. Note that you should sort the three moving averages (lowest first) before presenting them in order to make it easier to understand.
1003

An <rsi> tag that contains the RSI period used. The only valid RSI is: 14.
1004

Three <moving_average> tags that contain the three moving averages used to calculate the MACD. The valid moving averages are: 26, 12 and 9.
1005

A <momentum> tag that contains the momentum period used. The only valid momentum is: 10.

<expected_percentage_move>

The possible expected price move as a percentage.


<expected_price_move>

The actual currency value of the expected price move. If the event is a bearish event then this value will be negative (indicating a drop in price).


<id>

A unique, case sensitive, string id for this event. This is the field that is used to retrieve the chart (securitychart) or markup (eventmarkup) for this event. This id will remain stable as price corrections are recieved and recognition is re-run against the corrected data if the important event characteristics do not change. If you store the id locally, you can call the eventexists command to verify that the event is still valid.


<inbound_trend_duration>

The duration, in <price_period>s, of the inbound trend.


<inbound_trend_start_date>

The date for the start of the inbound trend. All date are of the form: YYYY-MM-DD


<inbound_trend_start_timestamp>

The timestamp for the start of the inbound trend. All timestamps are of the form: YYYY-MM-DD-HH.MM.SS.mmmmmm. This tag is deprecated; use <inbound_trend_start_date> instead.


<instrument>

An <instrument> tag describing the instrument the user entered.


<is_active>

Whether the event is considered currently active.

Value Description
T

Event is active
F

Event is not active

<last_active_date>

The last date for which the event is considered to have an effect on the instrument price. This field is populated when the <is_active> field is changed to "F" and contains the date on which this change was made. All dates are of the form: YYYY-MM-DD.


<last_active_timestamp>

The last timestamp for which the event is considered to have an effect on the instrument price. All timestamps are of the form: YYYY-MM-DD-HH.MM.SS.mmmmmm. This tag is deprecated; use <last_active_date> instead.


<last_possible_active_date>

The last date for which it is possible that the event can be considered to have an effect on the instrument price. This is determined at the time when the event is confirmed, based on the duration of a pattern (classics), the number of bars used in the calculation (moving average crossovers, RSI), and empirical evidence. All dates are of the form: YYYY-MM-DD.


<last_possible_active_timestamp>

The last timestamp for which it is possible that the event can be considered to have an effect on the instrument price. The last date that the event is actually considered to have an effect is returned in the <last_active_date> tag. All timestamps are of the form: YYYY-MM-DD-HH.MM.SS.mmmmmm. This tag is deprecated; use <last_possible_active_date> instead.


<price_period>

The price period for the event. Currently Recognia performs recognition on D daily and W weekly prices.


<pricing>

This tag contains the pricing (open, high, low, close) and volume traded at the time of confirmation. For daily patterns these values are the end of day values for the instrument.

Child tags

<close>

Close Price


<date>

Date for the price record. Dates have the format YYYY-MM-DD.


<high>

High Price


<low>

Low Price


<open>

Open Price


<open_interest>

Open Interest. This tag is deprecated.


<timestamp>

Timestamp for the price record. Timestamps have the format YYYY-MM-DD-HH.MM.SS.mmmmmm. This tag is deprecated; use the <date> tag instead.


<volume>

Volume Traded



<start_date>

Date for the start of the event. Dates have the format YYYY-MM-DD.


<start_timestamp>

Timestamp for the start of the event. Timestamps have the format YYYY-MM-DD-HH.MM.SS.mmmmmm. This tag is deprecated; use the <start_date> tag instead.


<symmetry_rating>

A measure of how symmetrical the chart for the event is. Not all event types have a symmetry rating. This is a Recognia derived value and ranges between 0 (not symmetrical) and 100 (perfectly symmetrical).


<target_price_range>

The target price range for this event.

Child tags

<close_position>

The Close Position indicates where the price closed at the end of the day relative to the target price range (e.g. BEFORE, WITHIN, BEYOND). In some cases, the stock has already reached the target price range (i.e. WITHIN or BEYOND) on the same date the event was identified (usually due to a dramatic jump or drop in price).


<lower>

Lower limit of the Target Price Range.


<upper>

Upper limit of the Target Price Range.



<trade_type>

Trading Opportunity Type. Possible values are:

Value Description
L

Long
S

Short
U

Undefined

<trading_horizon>

Trading Horizon. Possible values are:

Value Description
S

Short-term: 2 - 6 weeks.
I

Intermediate-term: 6 - 39 weeks.
L

Long-term: 9 months - 2 years+.

<trend_change_type>

The trend change type for this event. Valid Trend change type codes are:

Value Description
R

Reversal
C

Continuation
E

End
U

Undefined


Sample

<event type="standard">
	<breakout_price>0.387500</breakout_price>
	<class>C</class>
	<confirmation_type>C</confirmation_type>
	<confirmed_timestamp deprecated="T">2007-05-23-00.00.00.000000</confirmed_timestamp>
	<consensus_rating>72</consensus_rating>
	<duration>18</duration>
	<end_date>2007-05-23</end_date>
	<end_timestamp deprecated="T">2007-05-23-00.00.00.000000</end_timestamp>
	<event_type_id>42</event_type_id>
	<event_type_name>Symmetrical Continuation Triangle (Bearish)</event_type_name>
	<event_type_specific></event_type_specific>
	<expected_percentage_move>0.154838</expected_percentage_move>
	<expected_price_move>-0.060000</expected_price_move>
	<id>USvrm_AAPNhQPogGRAACAAAAACYg</id>
	<inbound_trend_duration>12</inbound_trend_duration>
	<inbound_trend_start_date>2007-04-11</inbound_trend_start_date>
	<inbound_trend_start_timestamp deprecated="T">2007-04-11-00.00.00.000000</inbound_trend_start_timestamp>
	<instrument>
		<currency_symbol>CAD</currency_symbol>
		<exchange_symbol>TORONTO</exchange_symbol>
		<id>222125225</id>
		<isin>CA4062161017</isin> 
		<issue_type>PFD</issue_type>
		<name>Nortel Networks</name>
		<related_index_instrument_id>222155588</related_index_instrument_id>
		<symbol type="BELZBERG">NT</symbol> 
		<symbol type="BLOOMBERG">NT</symbol> 
		<symbol type="COMMON">NTL.PR.F</symbol>
		<symbol type="ILX">NTL.F</symbol> 
		<symbol type="INTERACTIVE">NTL</symbol> 
		<symbol type="POWERDATA">NTL/PRF</symbol>
		<symbol type="REUTERS">NTL_pf</symbol>
		<type>S</type>
	</instrument>
	<is_active>T</is_active>
	<last_active_date></last_active_date>
	<last_active_timestamp deprecated="T"></last_active_timestamp>
	<last_possible_active_date>2007-07-12</last_possible_active_date>
	<last_possible_active_timestamp deprecated="T">2007-07-12-00.00.00.000000</last_possible_active_timestamp>
	<price_period>D</price_period>
	<pricing>
		<close>0.370000</close>
		<date>2007-05-23</date>
		<high>0.410000</high>
		<low>0.370000</low>
		<open>0.410000</open>
		<open_interest deprecated="T"></open_interest>
		<timestamp deprecated="T">2007-05-23-00.00.00.000000</timestamp>
		<volume>111000</volume>
	</pricing>
	<start_date>2007-04-27</start_date>
	<start_timestamp deprecated="T">2007-04-27-00.00.00.000000</start_timestamp>
	<symmetry_rating>0</symmetry_rating>
	<target_price_range>
		<close_position>BEFORE</close_position>
		<lower>0.32</lower>
		<upper>0.34</upper>
	</target_price_range>
	<trade_type>S</trade_type>
	<trading_horizon>I</trading_horizon>
	<trend_change_type>C</trend_change_type>
</event>