Regulatory News Service
RNS Replacement
Technical Specification
January 2007
RNS Replacement Technical Specification
Table of Contents
1
INTRODUCTION ................................................................................................................................................ 3
1.1
1.2
2
RNS TECHNICAL SPECIFICATIONS ............................................................................................................ 4
2.1
3
PURPOSE OF THIS DOCUMENT ....................................................................................................................... 3
ASSUMPTIONS ................................................................................................................................................ 3
VENDOR OUTPUT FUTURE SPECIFICATION .................................................................................................... 7
CUSTOMER SUPPORT ..................................................................................................................................... 8
APPENDIX A : EXISTING NEWSML SPECIFICATION FROM TIS104 SERVICE DEFINITION ................ 9
APPENDIX B1 : EXAMPLE EXISTING NEWSML FROM LIVE SYSTEM...................................................... 17
APPENDIX B2 : EXAMPLE EXISTING NEWSML FROM LIVE SYSTEM...................................................... 23
APPENDIX B3 : EXAMPLE EXISTING NEWSML FROM LIVE SYSTEM...................................................... 27
APPENDIX C : IMBEDDED CSS STYLESHEET FORMATTING ...................................................................... 30
APPENDIX D : EXAMPLE NEW NEWSML INCLUDING XHTML .................................................................. 31
APPENDIX E : DETAILED FSA FORMS ............................................................................................................... 34
APPENDIX F : EXAMPLE XSD SCHEMA ............................................................................................................. 39
Page 2 of 39
RNS Replacement Technical Specification
1
Introduction
The Regulatory News Service (RNS) ensures that price-sensitive information issued by
listed companies is distributed to market participants quickly and fairly. This underpins the
orderliness of the UK securities market. In addition RNS is responsible for global news
distribution and regulatory filings into Europe and the US.
The Exchange is currently in the process of designing a replacement infrastructure and
updating standards as various systems and components are end of life in terms of
support.
The project aims to produce RNS News Messages that more closely reflect the
submissions of organisations, simplify the message and speed up the process of
distributing news announcements.
Details of testing services will be provided in a separate publication.
1.1
Purpose of This Document
The purpose of this document is to specify the change to RNS Specifications for
Customer Feeds.
1.2
Assumptions

The FSA are currently in a consultation period for the implementation of the
Transparency Directive CPO604. This includes potential introduction of structured
outputs for certain form types.
It is understood that some of these changes may not be implemented until 2008 as a
response to the introduction of MiFID, however, the XML has been included in this
specification to cover the possibility of 2007 introduction.
If there is no introduction in 2007 no messages containing standard FSA XML tagging
will be used.

Customers connecting to Infolect will be able to process the new XHTML format within
the NEWSML messages
Page 3 of 39
RNS Replacement Technical Specification
2
RNS Technical Specifications
Specification:
Infolect Message Formats Unchanged
Description:
Infolect messages will be unchanged and the NEWSML will be incorporated
in multiple instances of the existing “5NT Announcement Messages Text”
400 byte fields as it is today.
RNS will allow a message to be spread across 9999 messages rather than
the existing 2500 messages. This change will not affect Infolect.
Specification:
NEWSML Headline
Description:
The Announcement Headline is included in the Infolect Message Header and
additionally within the NEWSML contained in the “5NT Announcement
Messages Text”.
The Infolect Message Header “Headline” field will remain unchanged at 29
characters
The existing NEWSML non-body section will contain the same XML headline
field but the Headline text will be changed to create a headline length up to
50 chars.
Specification:
NEWSML XHTML
Description:
The existing NEWSML body will be changed.
The existing body of the NEWSML specifies XHTML 1.0 as the format. This
specification will be retained and used (XHTML is not populated in existing
messages).
Specification:
RNS Standard CSS Style Sheet
Description:
RNS announcements will be created according to an RNS specific style
sheet which will be published on the World Wide Web.
This stylesheet will be available to customers and it is strongly recommended
that this stylesheet is used as announcements will be formatted for this style :
other styles may cause problems with readability.
This style sheet will define the default body text font, if it has not been
explicitly defined by the Contributor using the RNS edit interface. This style
does not need to form part of the specification (with the exception of the URL
where the CSS will live). Customers will always be given warning of any
future changes to this style sheet even though changes could technically be
automatically handled by customer systems.
Page 4 of 39
RNS Replacement Technical Specification
Specification:
NEWSML Embedded Stylesheet Formatting
Description:
The NEWSML message will be transmitted with presentation functionality
that defines the look of messages. This will be supported by a standard RNS
stylesheet formatting defined in Appendix C.
These styles will be embedded into an announcement using the "style" HTML
attribute, and will override the standard CSS stylesheet. For example:
<p style="color: red; font-style: italic;">some text to show in red italic</p>
Specification:
NEWSML XSD
Description:
The NEWSML message will be defined by an XML XSD definition template.
This will be used by vendors and vendor customers to build functionality that
reads the NEWSML messages. This is fully defined in the attached Appendix
F
Page 5 of 39
RNS Replacement Technical Specification
Specification:
NEWSML FSA Standard Forms
Description:
The FSA has announced plans to introduce 3 standard XML forms for
specific company reporting. As explained at the start of this document in
the Assumptions, these plans have yet to be ratified and the option of
including or excluding these forms must be available in the system.
The FSE Standard Forms :



HOL : Notification of Major Interest in Shares
POS : Notification of Transaction in Own Shares
RDS : Notification of Transaction of Directors
The detailed messages are defined in Appendix E.
These messages will be inserted into their own ContentItem section within
the NEWSML :
e.g.
NewsML
<ContentItem
………….
………….
………….
</ContentItem>
<ContentItem Href="Location of other media placed here">
<MediaType FormalName="PDF"/>
<Format FormalName="URL"/>
</ContentItem>
<ContentItem Href="HOL">
………….
………….
………….
</ContentItem>
Specification:
Embedded Media & PDF
Description:
URL links to media and PDF files will be included.
Media or PDF files in a zipped format can be included in a CDATA section of
the xml. This capability is required at system go-live but will not initially be
used. Pictures in the main body will not be allowed (to avoid the possibility of
a picture being pasted accidentally instead of text by a contributor).
Page 6 of 39
RNS Replacement Technical Specification
2.1
Vendor Output Future Specification
The following specification is included for information to allow customers to plan for
potential future changes. This will not be implemented with the RNS replacement
changes.
Specification:
NEWSML Extended Messages
Description:
The maximum Infolect size for an announcement is 9999messages *
400bytes = 3.7MB.
An extension NEWSML field to indicate a continuation announcement is
planned for future developments (dependent on the need for capacity and
bandwidth in the future).
Page 7 of 39
RNS Replacement Technical Specification
3
Customer Support
Client Technology Group
The Client Technology Group will provide technical support during the implementation of
these changes via:


The Technical Information Desk - Tel: 020 7797 3939, STX 33939
E-mail Client Technology Group at CTGroup@londonstockexchange.com
Technical queries may also be raised directly through your Technical Account
Manager.
Primary Account Manager (PAM)
Please contact your Primary Account Manager directly for all other queries of a
commercial or business nature.
Page 8 of 39
RNS Replacement Technical Specification
APPENDIX A : EXISTING NEWSML SPECIFICATION FROM
TIS104 SERVICE DEFINITION
NewsML is an XML based encoding for news endorsed by the IPTC. For further information on NewsML please
refer to IPTC NewsML Version 1.0 Functional Specification and IPTC NewsML DTD v1.0.
The following NewsML example contains RNS Announcement Data for a correction to a previous announcement.
Original Announcement:
RNS ID: 1200A
Release Date & Time: 19 July 2001 10:30:00
Current Announcement (Correction):
RNS ID: 1234A
Release Date & Time: 20 July 2001 11:15:00
Highlighted in the example below is the RNS data that has changed. The remainder may be considered a static
'wrapper' used to contain the data.
This will not vary between announcements.
Text in bold indicates RNS data that will vary between announcements.
NewsML elements in italics indicate optional elements that may be omitted from announcements depending on
the announcement details.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE NewsML SYSTEM "NewsML-xhtml.dtd">
<NewsML>
<Catalog Href="http://www.londonstockexchange.com/newsml/mastercatalog.xml"/>
<TopicSet FormalName="Companies">
<Topic Duid="CM">
<TopicType FormalName="Company"/>
<FormalName Scheme="CompanyLongName">ABC Company Holdings Plc</FormalName>
<FormalName Scheme="CompanyShortName">ABC Company Hldgs</FormalName>
<FormalName Scheme="TIDM">ABCD</FormalName>
<Property FormalName="CompanyType" Value="Listed"/>
</Topic>
<Topic Duid="C1">
<TopicType FormalName="Company"/>
<FormalName Scheme="CompanyLongName">Related One Plc</FormalName>
<FormalName Scheme="CompanyShortName">Rel One</FormalName>
<FormalName Scheme="TIDM">REL1</FormalName>
<Property FormalName="CompanyType" Value="IRS"/>
</Topic>
<Topic Duid="C2">
<TopicType FormalName="Company"/>
<FormalName Scheme="CompanyLongName">Related Two Plc</FormalName>
<FormalName Scheme="CompanyShortName">Rel Two</FormalName>
<FormalName Scheme="TIDM">REL2</FormalName>
<Property FormalName="CompanyType" Value="Listed"/>
</Topic>
<Topic Duid="C3">
<TopicType FormalName="Company"/>
<FormalName Scheme="CompanyLongName">Related Three Plc</FormalName>
<FormalName Scheme="CompanyShortName">Rel Three</FormalName>
<FormalName Scheme="TIDM">REL3</FormalName>
<Property FormalName="CompanyType" Value="Listed"/>
Page 9 of 39
RNS Replacement Technical Specification
</Topic>
<Topic Duid="C4">
<TopicType FormalName="Company"/>
<FormalName Scheme="CompanyLongName">Related Four Plc</FormalName>
<FormalName Scheme="CompanyShortName">Rel Four</FormalName>
<FormalName Scheme="TIDM">REL4</FormalName>
<Property FormalName="CompanyType" Value="IRS"/>
</Topic>
</TopicSet>
<TopicSet FormalName="RNSCategories">
<Topic Duid="CT">
<TopicType FormalName="RNSCategory"/>
<FormalName Scheme="RNSCategory">ACQ</FormalName>
</Topic>
</TopicSet>
<NewsEnvelope>
<DateAndTime>20010720T111500+0000</DateAndTime>
<NewsProduct FormalName="RNSRegulatory"/>
</NewsEnvelope>
<NewsItem>
<Identification>
<NewsIdentifier>
<ProviderId>londonstockexchange.com</ProviderId>
<DateId>20010720</DateId>
<NewsItemId>1200A</NewsItemId>
<RevisionId PreviousRevision="1" Update="N">2</RevisionId>
<PublicIdentifier>urn:newsml:londonstockexchange.com:20010719:1200A:2
</PublicIdentifier>
</NewsIdentifier>
</Identification>
<NewsManagement>
<NewsItemType FormalName="News"/>
<FirstCreated>20010719T103000+0000</FirstCreated>
<ThisRevisionCreated>20010720T111500+0000</ThisRevisionCreated>
<Status FormalName="Usable"/>
<Urgency FormalName="4"/>
</NewsManagement>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="yes"
Duid="NC00001">
<Role FormalName="MAIN"/>
<BasisForChoice>./ContentItem/MediaType/@FormalName</BasisForChoice>
<AdministrativeMetadata>
<Provider>
<Party FormalName="London Stock Exchange Plc"/>
</Provider>
</AdministrativeMetadata>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00002">
<Role FormalName="MAIN TEXT"/>
<NewsLines>
<HeadLine>The headline of the Announcement</HeadLine>
<DateLine>London,July20</DateLine>
</NewsLines>
<AdministrativeMetadata>
<Source>
<Party FormalName="ABC Company Holdings Plc"/>
</Source>
</AdministrativeMetadata>
<DescriptiveMetadata>
<Language FormalName="en"/>
<OfInterestTo FormalName="RNS"/>
Page 10 of 39
RNS Replacement Technical Specification
<TopicOccurrence Topic="#CM"/>
<TopicOccurrence Topic="#C1" HowPresent="Related"/>
<TopicOccurrence Topic="#C2" HowPresent="Related"/>
<TopicOccurrence Topic="#C3" HowPresent="Related"/>
<TopicOccurrence Topic="#C4" HowPresent="Related"/>
<TopicOccurrence Topic="#CT"/>
</DescriptiveMetadata>
<Metadata>
<MetadataType FormalName="RNSIdentifier"/>
<Property FormalName="RNSNumber" Value="1234A"/>
<Property FormalName="PreviousRNSNumber" Value="1200A"/>
</Metadata>
<ContentItem Duid="CI00001">
<MediaType FormalName="text"/>
<Format FormalName="XHTML"/>
<DataContent>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title/>
</head>
<body>
<pre>The first line of preformatted text.
The second line of preformatted text.
The nth line of preformatted text.
The last line of preformatted text.</pre>
</body>
</html>
</DataContent>
</ContentItem>
</NewsComponent>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00003">
<Role FormalName="VIDEO"/>
<NewsLines>
<HeadLine>Webcast from ABC Company Holdings Plc</HeadLine>
<DateLine>London,July20</DateLine>
</NewsLines>
<AdministrativeMetadata>
<Source>
<Party FormalName="ABC Company Holdings Plc"/>
</Source>
</AdministrativeMetadata>
<DescriptiveMetadata>
<OfInterestTo FormalName="RNS"/>
<TopicOccurrence Topic="#CM"/>
<TopicOccurrence Topic="#C1" HowPresent="Related"/>
<TopicOccurrence Topic="#C2" HowPresent="Related"/>
<TopicOccurrence Topic="#C3" HowPresent="Related"/>
<TopicOccurrence Topic="#C4" HowPresent="Related"/>
<TopicOccurrence Topic="#CT"/>
</DescriptiveMetadata>
<ContentItem Href="Location of streaming media placed here">
<MediaType FormalName="video"/>
<Format FormalName="MPEG"/>
</ContentItem>
</NewsComponent>
</NewsComponent>
</NewsItem>
</NewsML>
Page 11 of 39
RNS Replacement Technical Specification
The following bullet points provide a detailed explanation of the elements, attributes and values within the above
example.
The Href attribute of the Catalog element contains a pointer to the vocabularies which apply to the
FormalNames of certain elements.
The main company and any related companies of the announcements are contained within a TopicSet element
with a FormalName of
"Companies".
<TopicSet FormalName="Companies">
The main company to which the announcement relates is contained in a Topic element with a Duid of "CM".
Separate FormalName elements contain Scheme attributes defining the company descriptor type e.g. TIDM.
<Topic Duid="CM">
<TopicType FormalName="Company"/>
<FormalName Scheme="CompanyLongName">ABC Company Holdings plc</FormalName>
<FormalName Scheme="CompanyShortName">ABC Company Hldgs</FormalName>
<FormalName Scheme="TIDM">ABCD</FormalName>
<Property FormalName="CompanyType" Value="Listed"/>
</Topic>
The Duid is referenced in the DescriptiveMetadata of the NewsComponent elements holding the announcement
text and optional webcast URL. This creates a link between the main company and the text and video
NewsComponents to which it is related.
Any related companies may be described in the following Topic elements. These may be omitted if no related
companies are present, or a maximum of 4 related companies may be included with Duids ranging from "C1" to
"C4". As with the main company, separate FormalName elements contain Scheme attributes defining the
company descriptor.
<Topic Duid="C1">
<TopicType FormalName="Company"/>
<FormalName Scheme="CompanyLongName">Related OnePlc</FormalName>
<FormalName Scheme="CompanyShortName">RelOne</FormalName>
<FormalName Scheme="TIDM">REL1</FormalName>
<Property FormalName="CompanyType" Value="IRS"/>
</Topic>
The Duid is referenced in the DescriptiveMetadata of the NewsComponent elements holding the announcement
text and the optional webcast URL. This creates a link between the related company and the text and video
NewsComponents to which it is related.

The category of the announcement is contained within a TopicSet
element with a FormalName of "RNSCategories".
<TopicSet FormalName="RNSCategories">
The category of the announcement is contained in a Topic element with a Duid of "CT".
<Topic Duid="CT">
<TopicType FormalName="RNSCategory"/>
<FormalName Scheme="RNSCategory">ACQ</FormalName>
</Topic>
The Duid is referenced in the DescriptiveMetadata of the NewsComponent elements holding the announcement
text and the optional webcast URL. This creates a link between the category of the announcement and the text
and video NewsComponents to which it is related.
The DateAndTime and DateId elements will contain the release Date and
Time of the current announcement.
Page 12 of 39
RNS Replacement Technical Specification
<DateAndTime>20010720T111500+0000</DateAndTime>
The DateAndTime element is formed from the complete date representation in basic format followed by the time
designator (‘T’) and the complete time representation in basic format followed by the Coordinated Universal Time.
No separators shall be used. This format is specified in ISO 8601. The NewsML specification used prefers this
element to include the difference between the local time and Coordinated Universal Time (UTC). i.e.
CCYYMMDDTHHMMSSHHMM
The NewsProduct element defines the type of news contained within the
NewsML. In the case of RNS this may be "RNSRegulatory" news or
"RNSNonregulatory" news only.
<NewsProduct>RNSRegulatory</NewsProduct>
The DateId is set to the release date of the current announcement. The
date must conform to CCYYMMDD
<DateId>20010720</DateId>
The ProviderId element contains the domain name for the London Stock
Exchange
<ProviderId>londonstockexchange.com</ProviderId>
The NewsItemId contains the RNS number of the ORIGINAL announcement, NOT the correction. This allows
the RNS data to conform to the IPTC NewsML specification. The RNS number of the current announcement may
be found in the Metadata element. In most cases, the announcement will not be a correction to a previous
announcement, i.e. it will be an original, so the RNS Number in the NewsItemId element will match the current
RNS Number in the Metadata.
<NewsItemId>1200A</NewsItemId>

The NewsML above contains an announcement which is a correction to a previous announcement. This is
indicated by the revision number of "2".
<RevisionId PreviousRevision="1"
update="N">2</RevisionId>
If another correction is made to the announcement, the PreviousRevision will increment to "2" and the RevisionId
will increment to "3". An original announcement will have a revision number of "1" and the PreviousRevision
attribute will read "0".
The PublicIdentifier will be constructed from a standard prefix including the domain name and then the date,
followed by the RNS Number of the ORIGINAL announcement and the revision number of the current
announcement.
<PublicIdentifier>urn:newsml:londonstockexchange.com:
20010719:1200A:2</PublicIdentifier>

The FirstCreated element will contain the release timestamp of the ORIGINAL announcement.
<FirstCreated>20010719T103000+0000</FirstCreated

The NewsItemType element contains a FormalName element. The FormalName attribute values are defined
through an IPTC vocabulary. The FormalName attribute will always have the value of "News".
<NewsItemType FormalName="News"/>

Page 13 of 39
RNS Replacement Technical Specification
The ThisRevisionCreated element contains the release timestamp of the current announcement.
<ThisRevisionCreated>20010720T111500+0000</ThisRevisionCreated>
The timestamp format must conform to the same format as described in the DateAndTime element.
The Status element indicates the status of the NewsML news item. This will always be set to Usable for
announcements released by the RNS department.
<Status FormalName="Usable"/>

The Urgency of regulatory announcements will be set at "4". Nonregulatory announcements will have a lower
Urgency of "8". Again, there is a vocabulary defined by the IPTC for the FormalName attribute. However, RNS will
only use these two values.
<Urgency FormalName="4"/>

A wrapper NewsComponent element will be included to hold the child NewsComponent elements containing
the announcement text and, if included, the webcast URL. The EquivalentList attribute will be set to "yes" if a
webcast URL is supplied in the announcement, otherwise it will be set to "no".
<NewsComponent xml:lang="en" Essential="no"
EquivalentsList="yes" Duid="NC00001"> .....
</NewsComponent>

The Role element will define the role of the NewsComponent. The value of the FormalName is controlled by a
vocabulary defined in the Catalog element. Only three values will be used by RNS. "MAIN" denotes the wrapper
NewsComponent. "MAIN TEXT" denotes the NewsComponent holding the announcement text and "VIDEO"
denotes the NewsComponent holding a webcast URL.
<Role FormalName="MAIN"/>

The BasisForChoice element will only be included if a webcast URL is included in the announcement. If no
webcast URL is included this element will be omitted. The element will give the reasons for choosing between the
announcement text or the webcast. For RNS, this will always be set to the media type i.e. text or video.
<BasisForChoice>./ContentItem/MediaType/@FormalName</
BasisForChoice>
The provider of the NewsML containing the RNS data is the London Stock Exchange Plc.
<Provider>
<Party FormalName="London Stock Exchange Plc"/>
</Provider>

A NewsComponent holding the announcement text will always be present in the NewsML
<NewsComponent xml:lang="en" Essential="no"
EquivalentsList="no" Duid="NC00002">

Within the NewsComponent holding the announcement text, the headline of the announcement will be
contained in the Headline element.
<HeadLine>The headline of the Announcement</HeadLine>

The dateline will contain the place of creation of the NewsML followed by the month and day.
<DateLine>London,July20</DateLine>

The source of the RNS data which has been placed into the NewsML is the contributor. This may be either the
actual main company of the announcement, when the contributor name will match the main company long name.
Page 14 of 39
RNS Replacement Technical Specification
Or an agent acting on behalf of the main company, in which case the contributor name will differ from the main
company name.
<Source>
<Party FormalName="ABC Company Holdings Plc"/>
</Source>

The OfInterestTo element again has a FormalName which is controlled by a vocabulary. RNS will always be set
to "RNS".
<OfInterestTo FormalName="RNS"/>

The TopicOccurrence elements, in the DescriptiveMetadata of the NewsComponent holding the announcement
text, will use the Duids of the Topic elements to link the main, any related companies and the category of the
announcement to the text and video NewsComponents. A HowPresent attribute will mark the Duids of related
companies.
<TopicOccurrence Topic="#CM"/>
<TopicOccurrence Topic="#C1" HowPresent="Related"/>
<TopicOccurrence Topic="#C2" HowPresent="Related"/>
<TopicOccurrence Topic="#C3" HowPresent="Related"/>
<TopicOccurrence Topic="#C4" HowPresent="Related"/>
<TopicOccurrence Topic="#CT"/>

In the MetaData of the NewsComponent holding the announcement text. The Property element with a
FormalName of "RNSNumber" will hold the RNS Number of the current announcement.
<Property FormalName="RNSNumber" Value="1234A"/>

In the MetaData of the NewsComponent holding the announcement text, the Property element with a
FormalName of "PreviousRNSNumber" will hold the RNS Number of the announcement that it directly replaces.
For original announcements this element will be omitted. For a correction to a correction, the value will be the
RNS Number of the preceding correction NOT the original announcement.
<Property FormalName="PreviousRNSNumber"
Value="1200A"/>

The MediaType element is controlled by an IPTC vocabulary. RNS will only supply the value of "text" in the
NewsComponent holding the text of the announcement and "video" for the NewsComponent holding the webcast
URL.
<MediaType FormalName="text"/>
The Format element is controlled by an IPTC vocabulary. RNS will only supply the value of "XHTML" in the
NewsComponent holding the text of the announcement and "MPEG" for the NewsComponent holding the
webcast URL.
<Format FormalName="XHTML"/>

The announcement text will be contained within an xhtml wrapper in the DataContent child element of the
ContentItem element. The text will be preformatted and will be contained with html <Pre> tags.
A second NewsComponent will only be included if a webcast URL is supplied with the announcement. The
webcast must be equivalent to the announcement text. It will contain a Role element to distinguish it from the
NewsComponent containing the announcement text. The Headline, DateLine, AdministrativeMetadata and
DetailedMetadata elements will match the contents of those in the NewsComponent holding the text of the
announcement. The URL of the webcast will be contained within the Href attribute of the ContentItem element.
<NewsComponent xml:lang="en" Essential="no"
EquivalentsList="no" Duid="NC00003">
<Role FormalName="VIDEO"/>
<NewsLines>
Page 15 of 39
RNS Replacement Technical Specification
<HeadLine>Webcast from ABC Company HoldingsPlc</HeadLine>
<DateLine>London,July20</DateLine>
</NewsLines>
<AdministrativeMetadata>
<Source>
<Party FormalName="ABC Company Holdings Plc"/>
</Source>
</Administrative Metadata>
<DescriptiveMetadata>
<OfInterestTo FormalName="RNS"/>
<TopicOccurrence Topic="#CM"/>
<TopicOccurrence Topic="#C1"
HowPresent="Related"/>
<TopicOccurrence Topic="#C2"
HowPresent="Related"/>
<TopicOccurrence Topic="#C3"
HowPresent="Related"/>
<TopicOccurrence Topic="#C4"
HowPresent="Related"/>
<TopicOccurrence Topic="#CT"/>
</DescriptiveMetadata>
<ContentItem Href="Location of streaming media placed here">
<MediaType FormalName="video"/>
<Format FormalName="MPEG"/>
</ContentItem>
</NewsComponent>
Page 16 of 39
RNS Replacement Technical Specification
APPENDIX B1 : EXAMPLE EXISTING NEWSML FROM LIVE SYSTEM
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE NewsML SYSTEM "NewsML-xhtml.dtd">
<NewsML>
<Catalog Href="http://www.londonstockexchange.com/newsml/mastercatalog.xml"
/>
<TopicSet FormalName="Companies">
<Topic Duid="CM">
<TopicType FormalName="Company" />
<FormalName Scheme="CompanyLongName">Taylor Nelson Sofres
PLC</FormalName>
<FormalName Scheme="CompanyShortName">Taylor Nelson
Sofres</FormalName>
<FormalName Scheme="TIDM">TNN</FormalName>
<Property FormalName="CompanyType" Value="Listed Company" />
</Topic>
</TopicSet>
<TopicSet FormalName="RNSCategories">
<Topic Duid="CT">
<TopicType FormalName="RNSCategory" />
<FormalName Scheme="RNSCategory">Director/PDMR
Shareholding</FormalName>
</Topic>
</TopicSet>
<NewsEnvelope>
<DateAndTime>20061009T163005+0100</DateAndTime>
<NewsProduct FormalName="RNSRegulatory" />
</NewsEnvelope>
<NewsItem>
<Identification>
<NewsIdentifier>
<ProviderId>londonstockexchange.com</ProviderId>
<DateId>20061009</DateId>
<NewsItemId>1887K</NewsItemId>
<RevisionId PreviousRevision="0" Update="N">1</RevisionId>
<PublicIdentifier>urn:newsml:londonstockexchange.com:20061009:1887K:1</PublicIdenti
fier>
</NewsIdentifier>
</Identification>
<NewsManagement>
<NewsItemType FormalName="News" />
<FirstCreated>20061009T163005+0100</FirstCreated>
<ThisRevisionCreated>20061009T163005+0100</ThisRevisionCreated>
<Status FormalName="Usable" />
<Urgency FormalName="4" />
</NewsManagement>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00001">
<Role FormalName="MAIN" />
<AdministrativeMetadata>
<Provider>
<Party FormalName="London Stock Exchange Plc" />
</Provider>
</AdministrativeMetadata>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00002">
<Role FormalName="MAIN TEXT" />
<NewsLines>
Page 17 of 39
RNS Replacement Technical Specification
<HeadLine>Director/PDMR Shareholding</HeadLine>
<DateLine>London,OCTOBER09</DateLine>
</NewsLines>
<AdministrativeMetadata>
<Source>
<Party FormalName="Taylor Nelson Sofres PLC" />
</Source>
</AdministrativeMetadata>
<DescriptiveMetadata>
<Language FormalName="en" />
<OfInterestTo FormalName="RNS" />
<TopicOccurrence Topic="#CM" />
<TopicOccurrence Topic="#CT" />
</DescriptiveMetadata>
<Metadata>
<MetadataType FormalName="RNSIdentifier" />
<Property FormalName="RNSNumber" Value="1887K" />
<Property FormalName="TickerCode" Value="" />
<Property FormalName="MarketCode" Value="" />
</Metadata>
<ContentItem Duid="CI00001">
<MediaType FormalName="text" />
<Format FormalName="XHTML" />
<DataContent>
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en" lang="en">
<head>
<title />
</head>
<body>
<pre>RNS Number:1887K
Taylor Nelson Sofres PLC
09 October 2006
NOTIFICATION OF TRANSACTIONS OF DIRECTORS, PERSONS DISCHARGING MANAGERIAL
RESPONSIBILITY OR CONNECTED PERSONS
This form is intended for use by an issuer to make a RIS notification required
by DR 3.1.4R(1).
(1)
(2)
(3)
(4)
An issuer making a notification in respect of a transaction relating to
the shares or debentures of the issuer should complete boxes 1 to 16, 23
and 24.
An issuer making a notification in respect of a derivative relating to the
shares of the issuer should complete boxes 1 to 4, 6, 8, 13, 14, 16, 23
and 24.
An issuer making a notification in respect of options granted to a
director/person discharging managerial responsibilities should complete
boxes 1 to 3 and 17 to 24.
An issuer making a notification in respect of a financial instrument
relating to the shares of the issuer (other than a debenture) should
complete boxes 1 to 4, 6, 8, 9, 11, 13, 14, 16, 23 and 24.
Please complete all relevant boxes in block capital letters.
1. Name of the issuer
Page 18 of 39
RNS Replacement Technical Specification
TAYLOR NELSON SOFRES PLC
2. State whether the notification relates to (i) a transaction notified in
accordance with DR 3.1.4R(1)(a); or
(ii) DR 3.1.4(R)(1)(b) a disclosure made in accordance with section 324 (as
extended by section 328) of the Companies Act 1985; or
(iii) both (i) and (ii)
(iii) BOTH (i) AND (ii)
3. Name of person discharging managerial responsibilities/director
ANDY BOLAND - FINANCE DIRECTOR
4. State whether notification relates to a person connected with a person
discharging managerial responsibilities/director named in 3 and identify the
connected person
PERSON REFERRED TO IN 3. ABOVE
5. Indicate whether the notification is in respect of a holding of the person
referred to in 3 or 4 above or in respect of a non-beneficial interest
NOT APPLICABLE
6. Description of shares (including class), debentures or derivatives or
financial instruments relating to shares
NOT APPLICABLE
7. Name of registered shareholders(s) and, if more than one, the number of
shares held by each of them
NOT APPLICABLE
8 State the nature of the transaction
NOT APPLICABLE
9. Number of shares, debentures or financial instruments relating to shares
acquired
Page 19 of 39
RNS Replacement Technical Specification
NOT APPLICABLE
10. Percentage of issued class acquired (treasury shares of that class should
not be taken into account when calculating percentage)
NOT APPLICABLE.
11. Number of shares, debentures or financial instruments relating to shares
disposed
NOT APPLICABLE.
12. Percentage of issued class disposed (treasury shares of that class should
not be taken into account when calculating percentage)
NOT APPLICABLE.
13. Price per share or value of transaction
NOT APPLICABLE.
14. Date and place of transaction
NOT APPLICABLE
15. Total holding following notification and total percentage holding following
notification (any treasury shares should not be taken into account when
calculating percentage)
NOT APPLICABLE.
16. Date issuer informed of transaction
NOT APPLICABLE.
If a person discharg
ing managerial responsibilities has been granted options by
the issuer complete the following boxes
17 Date of grant
9 OCTOBER 2006
Page 20 of 39
RNS Replacement Technical Specification
18. Period during which or date on which it can be exercised
9 OCTOBER 2009 to 8 OCTOBER 2016
19. Total amount paid (if any) for grant of the option
NIL
20. Description of shares or debentures involved (class and number)
TAYLOR NELSON SOFRES PLC ORDINARY SHARES OF 5P EACH
21. Exercise price (if fixed at time of grant) or indication that price is to be
fixed at the time of exercise
NIL
22. Total number of shares or debentures over which options held following
notification
OPTIONS HELD OVER 876,000 SHARES FOLLOWING NOTIFIC_TION
23. Any additional information
265,000 PERFORMANCE SHARES GRANTED UNDER A CONDITION"L AWARD UNDER THE TAYLOR
NELSON SOFRES PLC LONG TERM INCENTIVE PLAN.
150,000 PERFORMANCE SHARES GRANTED UNDER A CONDITIONAL RETENTION AWARD UNDER THE
TAYLOR NELSON SOFRES PLC LONG TERM INCENTIVE PLAN.
24. Name of contact and telephone number for queries
IAN PORTAL, COMPANY SECRETARY, 020 8 967 0007
Name and signature of duly authorised officer of issuer responsible for making
notification
IAN PORTAL, COMPANY SECRETARY
Date of notification
9 OCTOBER 2006.
Page 21 of 39
RNS Replacement Technical Specification
END
This information is provided by RNS
The company news service from the London Stock Exchange
END
RDSBLBDGSBGGGLC</pre>
</body>
</html>
</DataContent>
</ContentItem>
</NewsComponent>
</NewsComponent>
</NewsItem>
</NewsML>
Page 22 of 39
RNS Replacement Technical Specification
APPENDIX B2 : EXAMPLE EXISTING NEWSML FROM LIVE SYSTEM
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE NewsML SYSTEM "NewsML-xhtml.dtd">
<NewsML>
<Catalog Href="http://www.londonstockexchange.com/newsml/mastercatalog.xml"
/>
<TopicSet FormalName="Companies">
<Topic Duid="CM">
<TopicType FormalName="Company" />
<FormalName Scheme="CompanyLongName">Intertek Group
PLC</FormalName>
<FormalName Scheme="CompanyShortName">Intertek Group
Plc</FormalName>
<FormalName Scheme="TIDM">ITRK</FormalName>
<Property FormalName="CompanyType" Value="Listed Company" />
</Topic>
</TopicSet>
<TopicSet FormalName="RNSCategories">
<Topic Duid="CT">
<TopicType FormalName="RNSCategory" />
<FormalName Scheme="RNSCategory">Holding(s) in
Company</FormalName>
</Topic>
</TopicSet>
<NewsEnvelope>
<DateAndTime>20061009T163010+0100</DateAndTime>
<NewsProduct FormalName="RNSRegulatory" />
</NewsEnvelope>
<NewsItem>
<Identification>
<NewsIdentifier>
<ProviderId>londonstockexchange.com</ProviderId>
<DateId>20061009</DateId>
<NewsItemId>1917K</NewsItemId>
<RevisionId PreviousRevision="0" Update="N">1</RevisionId>
<PublicIdentifier>urn:newsml:londonstockexchange.com:20061009:1917K:1</PublicIdenti
fier>
</NewsIdentifier>
</Identification>
<NewsManagement>
<NewsItemType FormalName="News" />
<FirstCreated>20061009T163010+0100</FirstCreated>
<ThisRevisionCreated>20061009T163010+0100</ThisRevisionCreated>
<Status FormalName="Usable" />
<Urgency FormalName="4" />
</NewsManagement>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00001">
<Role FormalName="MAIN" />
<AdministrativeMetadata>
<Provider>
<Party FormalName="London Stock Exchange Plc" />
</Provider>
</AdministrativeMetadata>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00002">
<Role FormalName="MAIN TEXT" />
Page 23 of 39
RNS Replacement Technical Specification
<NewsLines>
<HeadLine>Holding(s) in Company</HeadLine>
<DateLine>London,OCTOBER09</DateLine>
</NewsLines>
<AdministrativeMetadata>
<Source>
<Party FormalName="Intertek Group PLC" />
</Source>
</AdministrativeMetadata>
<DescriptiveMetadata>
<Language FormalName="en" />
<OfInterestTo FormalName="RNS" />
<TopicOccurrence Topic="#CM" />
<TopicOccurrence Topic="#CT" />
</DescriptiveMetadata>
<Metadata>
<MetadataType FormalName="RNSIdentifier" />
<Property FormalName="RNSNumber" Value="1917K" />
<Property FormalName="TickerCode" Value="" />
<Property FormalName="MarketCode" Value="" />
</Metadata>
<ContentItem Duid="CI00001">
<MediaType FormalName="text" />
<Format FormalName="XHTML" />
<DataContent>
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en" lang="en">
<head>
<title />
</head>
<body>
<pre>RNS Number:1917K
Intertek Group PLC
09 October 2006
SCHEDULE 10
NOTIFICATION OF MAJOR INTERESTS IN SHARES
1. Name of company
Intertek Group plc
2. Name of shareholder having a major interest
FMR Corp. and Fidelity International Limited and their direct and indirect
subsidiaries
3.
Please state whether notification indicates that it is in respect of holding
of the shareholder named in 2 above or in respect of a non-beneficial interest
or in the case of an individual holder if it is a holding of that person&apos;s
spouse or children under the age of 18
Non beneficial interest on behalf of various direct and indirect subsidiaries of
FMR Corp. and Fidelity International Ltd a
nd notifiable interest of Mr Edward C.
Johnson 3d, principal shareholder of FMR Corp. and Fidelity International Ltd
Page 24 of 39
RNS Replacement Technical Specification
4. Name of the registered holder(s) and, if more than one holder, the number of
shares held by each of them
Registered Holder
No. of shares
BANK OF NEW YORK
BANK OF NEW YO
RK BRUSSELS
BANK OF NEW YORK BRUSSELS
BANK OF NEW YORK EUROPE LONDON
BROWN BROTHERS HARRIMAN AND CO
BROWN BROTHERS HARRIMAN AND CO
BROWN BROTHERS HARR
IMAN LTD LUX
CITIBANK NA
CITIBANK, LONDON
JP MORGAN CHASE BANK
JP MORGAN, BOURNEMOUTH
JP MORGAN, BOURNEMOUTH
101,000
JP MORGAN, BOURNEMOUTH
JP MORGAN, BOURNEMOUTH
MELLON BANK
NATIONAL ASTL BANK MELBOURNE
NORTHERN TRUST CO
10,400
NORTHERN TRUST LONDON
STATE STREET BANK AND TR CO
STATE STREET BANK AND TR CO
STATE STREET BK AND TR CO LNDN
Total
5,974,989
56,900
68,500
79,700
506,500
34,000
436,200
996
89,900
74,000
26,100
1,097,105
577,140
300,600
251,854
37,600
601,594
87,800
1,513,300
23,800
5. Number of shares / amount of stock acquired
Not Applicable
6. Percentage of issued class
Not Applicable
7. Number of shares / amount of stock disposed
1,661,200 shares
8. Percentage of issued class
1.06
9. Class of security
Ordinary shares of 1p
10. Date of transaction
Not disclosed
11. Date company informed
9 October 2006
Page 25 of 39
RNS Replacement Technical Specification
12. Total
holding following this notification
5,974,989 shares
13. Total percentage holding of issued class following this notification
3.82%
14. Any additional information
None
15. Name of contact and telephone number for queries
Maggie Mellor 0207 396 3442
16. Name and signature of authorised company official responsible for making
this notification
Maggie Mellor, Deputy Company Secretary
17. D
ate of notification
9 October 2006
The FSA does not give any express or implied warranty as to the accuracy of this
document or material and does not accept any liability for error or omission.
The FSA is not liable for any damages (including, without limitation, damages
for loss of business or loss of profits) arising in contract, tort or otherwise
from the use of or inability to use this docum
ent, or any material contained in
it, or from any action or decision taken as a result of using this document or
any such material.
This information is provided by RNS
The company news service from the London Stock Exchange
END
HOLEAKENEAPKFFE</pre>
</body>
</html>
</DataContent>
</ContentItem>
</NewsComponent>
</NewsComponent>
</NewsItem>
</NewsML>
Page 26 of 39
RNS Replacement Technical Specification
APPENDIX B3 : EXAMPLE EXISTING NEWSML FROM LIVE SYSTEM
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE NewsML SYSTEM "NewsML-xhtml.dtd">
<NewsML>
<Catalog Href="http://www.londonstockexchange.com/newsml/mastercatalog.xml"
/>
<TopicSet FormalName="Companies">
<Topic Duid="CM">
<TopicType FormalName="Company" />
<FormalName Scheme="CompanyLongName">Morant Wright Japan Inc.
Tst. Ltd</FormalName>
<FormalName Scheme="CompanyShortName">Morant Wright
Japan</FormalName>
<FormalName Scheme="TIDM">MWJ</FormalName>
<Property FormalName="CompanyType" Value="Investment Trust /
Fund" />
</Topic>
</TopicSet>
<TopicSet FormalName="RNSCategories">
<Topic Duid="CT">
<TopicType FormalName="RNSCategory" />
<FormalName Scheme="RNSCategory">Net Asset Value(s)</FormalName>
</Topic>
</TopicSet>
<NewsEnvelope>
<DateAndTime>20061009T165815+0100</DateAndTime>
<NewsProduct FormalName="RNSRegulatory" />
</NewsEnvelope>
<NewsItem>
<Identification>
<NewsIdentifier>
<ProviderId>londonstockexchange.com</ProviderId>
<DateId>20061009</DateId>
<NewsItemId>1974K</NewsItemId>
<RevisionId PreviousRevision="0" Update="N">1</RevisionId>
<PublicIdentifier>urn:newsml:londonstockexchange.com:20061009:1974K:1</PublicIdenti
fier>
</NewsIdentifier>
</Identification>
<NewsManagement>
<NewsItemType FormalName="News" />
<FirstCreated>20061009T165815+0100</FirstCreated>
<ThisRevisionCreated>20061009T165815+0100</ThisRevisionCreated>
<Status FormalName="Usable" />
<Urgency FormalName="4" />
</NewsManagement>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00001">
<Role FormalName="MAIN" />
<AdministrativeMetadata>
<Provider>
<Party FormalName="London Stock Exchange Plc" />
</Provider>
</AdministrativeMetadata>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00002">
<Role FormalName="MAIN TEXT" />
Page 27 of 39
RNS Replacement Technical Specification
<NewsLines>
<HeadLine>Net Asset Value(s)</HeadLine>
<DateLine>London,OCTOBER09</DateLine>
</NewsLines>
<AdministrativeMetadata>
<Source>
<Party FormalName="Morant Wright Japan Inc.
Tst. Ltd" />
</Source>
</AdministrativeMetadata>
<DescriptiveMetadata>
<Language FormalName="en" />
<OfInterestTo FormalName="RNS" />
<TopicOccurrence Topic="#CM" />
<TopicOccurrence Topic="#CT" />
</DescriptiveMetadata>
<Metadata>
<MetadataType FormalName="RNSIdentifier" />
<Property FormalName="RNSNumber" Value="1974K" />
<Property FormalName="TickerCode" Value="" />
<Property FormalName="MarketCode" Value="" />
</Metadata>
<ContentItem Duid="CI00001">
<MediaType FormalName="text" />
<Format FormalName="XHTML" />
<DataContent>
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en" lang="en">
<head>
<title />
</head>
<body>
<pre>RNS Number:1974K
Morant Wright Japan Inc. Tst. Ltd
09 October 2006
Morant Wright Japan Income Trust Limited
(a closed-ended investment company incorporated in Guernsey with registration
number 43839)
FUND NAME
NAV DATE
MW Japan Income Trust Ltd
NAV
93.36p
BOLVM72
09 October 2006
N.B. The NAV is inclusive of 6.42p per share in respect of the fair value of
the swap.
Date: 09 October 2006
Enquiries:
Northern Trust International Fund Administration Services (Guernsey) Limited
Sean Murray 44 (0)1481 745311
Page 28 of 39
RNS Replacement Technical Specification
This information is provided by RNS
The comp
any news service from the London Stock Exchange
END
NAVKGMGGVLNGVZM</pre>
</body>
</html>
</DataContent>
</ContentItem>
</NewsComponent>
</NewsComponent>
</NewsItem>
</NewsML>
Page 29 of 39
RNS Replacement Technical Specification
APPENDIX C : Imbedded CSS Stylesheet Formatting
COLOR RELATED
color: <color>
FONT RELATED
font-family: <font name>
font-style: normal | italic
font-weight: normal | bold | bolder | lighter
font-size: <point-size>
TEXT ALIGNMENT AND DECORATION
text-align: left | right | center | justify
text-decoration: none | underline | overline | line-through
TABLE BORDERS
border-color:
border-style:
ridge | inset
border-width:
<color>
none | hidden | dotted | dashed | solid | double | groove |
| outset
<border-width>
Page 30 of 39
RNS Replacement Technical Specification
APPENDIX D : EXAMPLE NEW NEWSML INCLUDING XHTML
This is an example announcement presenting the example in Appendix B3 in HTML.
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE NewsML SYSTEM "NewsML-xhtml.dtd">
<NewsML>
<Catalog Href="http://www.londonstockexchange.com/newsml/mastercatalog.xml"
/>
<TopicSet FormalName="Companies">
<Topic Duid="CM">
<TopicType FormalName="Company" />
<FormalName Scheme="CompanyLongName">Morant Wright Japan Inc.
Tst. Ltd</FormalName>
<FormalName Scheme="CompanyShortName">Morant Wright
Japan</FormalName>
<FormalName Scheme="TIDM">MWJ</FormalName>
<Property FormalName="CompanyType" Value="Investment Trust /
Fund" />
</Topic>
</TopicSet>
<TopicSet FormalName="RNSCategories">
<Topic Duid="CT">
<TopicType FormalName="RNSCategory" />
<FormalName Scheme="RNSCategory">Net Asset Value(s)</FormalName>
</Topic>
</TopicSet>
<NewsEnvelope>
<DateAndTime>20061009T165815+0100</DateAndTime>
<NewsProduct FormalName="RNSRegulatory" />
</NewsEnvelope>
<NewsItem>
<Identification>
<NewsIdentifier>
<ProviderId>londonstockexchange.com</ProviderId>
<DateId>20061009</DateId>
<NewsItemId>1974K</NewsItemId>
<RevisionId PreviousRevision="0" Update="N">1</RevisionId>
<PublicIdentifier>urn:newsml:londonstockexchange.com:20061009:1974K:1</PublicIdenti
fier>
</NewsIdentifier>
</Identification>
<NewsManagement>
<NewsItemType FormalName="News" />
<FirstCreated>20061009T165815+0100</FirstCreated>
<ThisRevisionCreated>20061009T165815+0100</ThisRevisionCreated>
<Status FormalName="Usable" />
<Urgency FormalName="4" />
</NewsManagement>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00001">
<Role FormalName="MAIN" />
<AdministrativeMetadata>
<Provider>
<Party FormalName="London Stock Exchange Plc" />
</Provider>
</AdministrativeMetadata>
<NewsComponent xml:lang="en" Essential="no" EquivalentsList="no"
Duid="NC00002">
Page 31 of 39
RNS Replacement Technical Specification
<Role FormalName="MAIN TEXT" />
<NewsLines>
<HeadLine>Net Asset Value(s)</HeadLine>
<DateLine>London,OCTOBER09</DateLine>
</NewsLines>
<AdministrativeMetadata>
<Source>
<Party FormalName="Morant Wright Japan Inc.
Tst. Ltd" />
</Source>
</AdministrativeMetadata>
<DescriptiveMetadata>
<Language FormalName="en" />
<OfInterestTo FormalName="RNS" />
<TopicOccurrence Topic="#CM" />
<TopicOccurrence Topic="#CT" />
</DescriptiveMetadata>
<Metadata>
<MetadataType FormalName="RNSIdentifier" />
<Property FormalName="RNSNumber" Value="1974K" />
<Property FormalName="TickerCode" Value="" />
<Property FormalName="MarketCode" Value="" />
</Metadata>
<ContentItem Duid="CI00001">
<MediaType FormalName="text" />
<Format FormalName="XHTML" />
<DataContent>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Enter the title of your XHTML document here</title>
</head>
<body style="font-family: 'Times New Roman', sans-serif">
<p>RNS Number:1974K<br />
Morant Wright Japan Inc. Tst. Ltd<br />
09 October 2006</p>
<hr />
<h1>Morant Wright Japan Income Trust Limited</h1>
<h2> (a closed-ended investment company incorporated in Guernsey with
registration
number 43839)</h2>
<table border="true">
<tbody>
<tr align="left">
<th>FUND NAME</th>
<th>NAV</th>
<th>NAV DATE</th>
</tr>
<tr>
<td>MW Japan Income Trust Ltd - BOLVM72</td>
<td style="color: blue; font-weight: bold">93.36p</td>
<td>09 October 2006</td>
</tr>
</tbody>
</table>
<p style="font-family: 'arial', sans-serif; font-style: italic"> N.B. The NAV
is inclusive of 6.42p per share in respect of the fair value of
the swap.</p>
<p>Date: 09 October 2006</p>
<p>Enquiries:</p>
<p>Northern Trust International Fund Administration Services (Guernsey)
Limited</p>
Page 32 of 39
RNS Replacement Technical Specification
<p>Sean Murray 44 (0)1481 745311</p>
<p>This information is provided by RNS<br />
The company news service from the London Stock Exchange</p>
<hr />
<pre style="font-family: arial">END
NAVKGMGGVLNGVZM
</pre>
</body>
</html>
</DataContent>
</ContentItem>
</NewsComponent>
</NewsComponent>
</NewsItem>
</NewsML>
Page 33 of 39
RNS Replacement Technical Specification
APPENDIX E : DETAILED FSA FORMS
The three standard FSA forms in this section are shown to provide a detailed image of the
specification currently under consultation by the FSA and are referred to in the “NEWSML FSA
Standard Forms” specification in the main document.
Specification:
NEWSML FSA Standard Forms: HOL
Description:
HOL : Notification of Major Interest in Shares
<!-XSD Definition of the HOL News Type
-->
- <xs:group name="NewsHOLGroup">
- <xs:sequence>
- <xs:element name="NewsHOL">
- <xs:complexType>
- <xs:sequence>
<xs:element name="Issuer" type="xs:string" />
<xs:element name="Name" type="xs:string" />
<xs:element name="Shareholder" type="xs:string" minOccurs="0" />
<xs:element name="ThresholdDate" type="xs:date" />
<xs:element name="IssuerNotifiedDate" type="xs:date" />
<xs:element name="ThresholdPercentage" type="xs:decimal" />
- <xs:choice>
<xs:group ref="EventChangeGroup" />
<xs:group ref="FinancialInstrumentsGroup" />
<xs:group ref="VotingRightsGroup" />
</xs:choice>
<xs:element name="Total" type="xs:decimal" />
<xs:element name="VotingRightsTotal" type="xs:decimal" />
<xs:element name="VotingRightsPercentageTotal"
type="xs:decimal" />
<xs:element name="Undertakings" type="xs:string" minOccurs="0"
/>
<xs:group ref="ProxyVotingGroup" />
<xs:group ref="HOLAdditionalInformationGroup" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <!-Group Definitions for HOL News Message
-->
- <xs:group name="EventChangeGroup">
- <xs:sequence>
- <xs:element name="EventChange">
- <xs:complexType>
- <xs:sequence>
<xs:group ref="HOLNotificationDetailsGroup" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="FinancialInstrumentsGroup">
- <xs:sequence>
- <xs:element name="FinancialInstruments">
- <xs:complexType>
- <xs:sequence>
<xs:element name="FinancialInstrumentExpirationDate"
type="xs:date" />
<xs:element
name="FinancialInstrumentNumberOfVotingRightsIfExercise
d" type="xs:decimal" />
<xs:element name="FinancialInstrumentExerciseDate"
type="xs:date" />
Page 34 of 39
RNS Replacement Technical Specification
<xs:element name="FinancialInstrumentNumberOfVotingRights"
type="xs:decimal" />
<xs:element
name="FinancialInstrumentPercentageOfVotingRights"
type="xs:decimal" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="HOLAdditionalInformationGroup">
- <xs:sequence>
- <xs:element name="AnyAdditionalInformation">
- <xs:complexType>
- <xs:sequence>
<xs:element name="AdditionalInformation" type="xs:string"
minOccurs="0" />
<xs:element name="Contact" type="xs:string" />
<xs:element name="ContactTelephone" type="Text75Type" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="HOLNotificationDetailsGroup">
- <xs:sequence>
<xs:element name="NonFinancialInstrumentSharesType" type="xs:string" />
<xs:element name="NonFinancialInstrumentShares" type="xs:decimal" />
<xs:element name="NonFinancialInstrumentVotingRights" type="xs:decimal" />
<xs:element name="NonFinancialInstrumentNumberOfSecurities" type="xs:decimal" />
<xs:element name="NonFinancialInstrumentDirectVotingRights" type="xs:decimal" />
<xs:element name="NonFinancialInstrumentIndirectVotingRights" type="xs:decimal" />
<xs:element name="NonFinancialInstrumentDirectVotingRightsPercentage"
type="xs:decimal" />
<xs:element name="NonFinancialInstrumentIndirectVotingRightsPercentage"
type="xs:decimal" />
</xs:sequence>
</xs:group>
- <xs:group name="ProxyVotingGroup">
- <xs:sequence>
- <xs:element name="ProxyVoting">
- <xs:complexType>
- <xs:sequence>
<xs:element name="ProxyHolder" type="xs:string" minOccurs="0" />
<xs:element name="ProxyHoldersVotingRightsCeased"
type="xs:decimal" minOccurs="0" />
<xs:element name="ProxyHoldersVotingRightsCeasedDate"
type="xs:date" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="VotingRightsGroup">
- <xs:sequence>
- <xs:element name="VotingRightsAttachedToShares">
- <xs:complexType>
- <xs:sequence>
<xs:group ref="HOLNotificationDetailsGroup" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <!--
Specification:
NEWSML FSA Standard Forms : POS
Page 35 of 39
RNS Replacement Technical Specification
Description:
POS : Notification of Transaction in Own Shares
<!-Definition of the POS News Type
-->
- <xs:group name="NewsPOSGroup">
- <xs:sequence>
- <xs:element name="NewsPOS">
- <xs:complexType>
- <xs:sequence>
<xs:element name="Issuer" type="xs:string" />
<xs:element name="Reason" type="xs:string" />
<xs:element name="SecurityDescription" type="xs:string" />
<xs:element name="DateOfTransaction" type="xs:date" />
- <xs:choice>
<xs:group ref="SecuritiesOtherThanSharesGroup" />
<xs:group ref="SharesGroup" />
</xs:choice>
<xs:group ref="GenericAdditionalInformationGroup" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
Group Definitions for POS News Message
-->
- <xs:group name="SecuritiesOtherThanSharesGroup">
- <xs:sequence>
- <xs:element name="SecuritiesOtherThanShares">
- <xs:complexType>
- <xs:sequence>
<xs:element name="TransactionType" type="TransactionTypeType"
/>
<xs:element name="NonSharesRedeemedOrCancelled"
type="xs:decimal" />
<xs:element name="NonSharesRemaining" type="xs:decimal" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="SharesGroup">
- <xs:sequence>
- <xs:element name="Shares">
- <xs:complexType>
- <xs:sequence>
<xs:element name="NumberOfSecurities" type="xs:decimal" />
<xs:element name="LowestPurchasePrice" type="xs:decimal" />
<xs:element name="HighestPurchasePrice" type="xs:decimal" />
<xs:element name="SharesCancelled" type="xs:decimal" />
<xs:element name="TreasuryShares" type="xs:decimal" />
<xs:element name="TotalTreasuryShares" type="xs:decimal" />
<xs:element name="TotalNonTreasuryShares" type="xs:decimal" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
<xs:simpleType name="TransactionTypeType">
<xs:restriction base="xs:string">
<xs:enumeration value="Acquisition"/>
<xs:enumeration value="Redemption"/>
<xs:enumeration value="Cancellation"/>
</xs:restriction>
</xs:simpleType>
Page 36 of 39
RNS Replacement Technical Specification
Specification:
NEWSML FSA Standard Forms : RDS
Description:
RDS : Notification of Transaction of Directors
<!-Group Definitions for RDS News Message
-->
- <xs:group name="DerivativesRelatingToSharesGroup">
- <xs:sequence>
- <xs:element name="DerivativesRelatingToShares">
- <xs:complexType>
- <xs:sequence>
<xs:element name="SecurityDescription" type="xs:string" />
<xs:element name="NatureOfTransaction" type="xs:string" />
<xs:element name="SharePrice" type="xs:decimal" />
<xs:element name="DateOfTransaction" type="xs:date" />
<xs:element name="PlaceOfTransaction" type="xs:string" />
<xs:element name="DateIssuerFormed" type="xs:date" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="FinancialInstrumentsRelatingToSharesGroup">
- <xs:sequence>
- <xs:element name="FinancialInstrumentsRelatingToShares">
- <xs:complexType>
- <xs:sequence>
<xs:element name="SecurityDescription" type="xs:string" />
<xs:element name="NatureOfTransaction" type="xs:string" />
<xs:element name="NumberOfSecurities" type="xs:decimal" />
<xs:element name="NumberOfSecuritiesDisposed" type="xs:decimal" />
<xs:element name="SharePrice" type="xs:decimal" />
<xs:element name="DateOfTransaction" type="xs:date" />
<xs:element name="PlaceOfTransaction" type="xs:string" />
<xs:element name="DateIssuerFormed" type="xs:date" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="GrantOfOptionsGroup">
- <xs:sequence>
- <xs:element name="GrantOfOptions">
- <xs:complexType>
- <xs:sequence>
<xs:element name="DateOfGrant" type="xs:date" />
<xs:element name="GrantExercisePeriod" type="xs:string" />
<xs:element name="AmountPaidForGrant" type="xs:decimal" />
<xs:element name="SharesDebenturesInvolved" type="xs:string" />
<xs:element name="ExercisePriceAtTimeOfGrant" type="xs:decimal"
minOccurs="0" />
<xs:element name="NumberOfSecuritiesForOptionsHeld"
type="xs:decimal" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
- <xs:group name="SharesOrDebenturesGroup">
- <xs:sequence>
- <xs:element name="SharesOrDebentures">
- <xs:complexType>
- <xs:sequence>
<xs:element name="NatureOfHolding" type="xs:string" />
<xs:element name="SecurityDescription" type="xs:string" />
<xs:element name="ShareholdersAndShares" type="xs:string" />
<xs:element name="NatureOfTransaction" type="xs:string" />
<xs:element name="NumberOfSecurities" type="xs:decimal" />
<xs:element name="PercentageSecuritiesAcquired" type="xs:decimal" />
<xs:element name="NumberOfSecuritiesDisposed" type="xs:decimal" />
<xs:element name="PercentageOfSecuritiesDisposed" type="xs:decimal" />
<xs:element name="SharePrice" type="xs:decimal" />
<xs:element name="DateOfTransaction" type="xs:date" />
Page 37 of 39
RNS Replacement Technical Specification
<xs:element name="PlaceOfTransaction" type="xs:string" />
<xs:element name="TotalHoldingAfterTransaction" type="xs:decimal" />
<xs:element name="TotalPercentageHoldingAfterTransaction"
type="xs:decimal" />
<xs:element name="DateIssuerFormed" type="xs:date" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
Page 38 of 39
RNS Replacement Technical Specification
APPENDIX F : EXAMPLE XSD SCHEMA
See Supporting XSD document.
Page 39 of 39