Tags

Tags is an array of strings, each string defines one tag. A tag can be viewed as a boolean property being true if present. A tag is divided into at least two parts, a namespace and the content, e.g. sub:report:interim where sub is the namespace. Tag can be added to the different namespaces over time, but they should always appear in this documentation

Tags describe in general the taxonomy and classification of press releases. This is done primary through the root and sub namespace listed below. The tags are hierarchical by nature and the entire hierarchy should be present, mening that id sub:report:interim:q4 appears in a tag, sub:report:interim and sub:report also appears

Namespaces

There are a few namespaces and tags that follow with each.

Root namespace (:)

This namespace is important in some contexts and will always be the first thing in the array. It is defined by metadata that must be present.

Tags

• :regulatory indicates that news item is required by some regulation

• :regulatory:marindicates that news item is required by EU Market Abuse Regulation

• :regulatory:vpmlindicates that news item is required by Swedish "Lagen om värdepappersmarknaden" Regulation

• :regulatory:lhfiindicates that news item is required by Swedish "Lagen om handel med finansiella instrument" Regulation

• :regulatory:listingindicates that news item is Stock Exchange Listing Requirement

• :correction A correction of a previous sent news item

• :correction:{news_id} A correction with a reference to the news id of which it corrects

Subject namespace (sub:)

This namespace contain metadata that helps to categorize the news item. This namespace is defined by MFN.

• sub:reportindicates that news is report of some kind

• sub:report:annualindicates that news is a Annual report

• sub:report:interimindicates that news is a Interim report

• sub:report:interim:q1indicates that news is a First Quarter Interim report

• sub:report:interim:q2indicates that news is a Second Quarter Interim report, a.k.a. Semi Annual

• sub:report:interim:q3indicates that news is a Third Quarter Interim report

• sub:report:interim:q4indicates that news is a Forth Quarter Interim report, a.k.a. Year End

• sub:caindicates that news item is related to a Corporate Action

• sub:ca:sharesindicates that news item is related a change in number of shares or votes

• sub:ca:shares:issuanceindicates that news item informs about stock issuance

• sub:ca:shares:repurchaseindicates that news item informs repurchase of stocks

• sub:ca:shares:rightsindicates that news item informs about changes to stock rights or classes

• sub:ca:maindicates that news item is related to Mergers & Acquisitions

• sub:ca:prospectusindicates that news item is related to a prospectus

• sub:ca:otherindicates that news item is related to other Corporate Action

• sub:ciindicates that news item is related to Corporate Information

• sub:ci:gmindicates that news item is related to a general meeting

• sub:ci:gm:noticeindicates that news item is a Notice to a General Meeting

• sub:ci:gm:infoindicates that news item is a Report from a General Meeting

• sub:ci:insiderindicates that news item is a insider transaction

• sub:ci:shareholder-announcementindicates that news item is a shareholder announcement

• sub:ci:calendarindicates that news item is a financial calendar

• sub:ci:presentationindicates that news item is related to a presentation

• sub:ci:nominationindicates that news item is related to Nomination Committee

• sub:ci:earningsindicates that news item informs about a earnings report

• sub:ci:salesindicates that news item informs about some sales

• sub:ci:sales:orderindicates that news item informs about a incoming sales order

• sub:ci:staffindicates that news item is related to staff changes

• sub:ci:otherindicates that news item is related to other Corporate Information

Custom namespace (cus:)

Author of a news item can add their own tags in order to categorize their content, but should in most cases probably be ignored by third parties. example might be cus:fintech