|
MDDL
Technology/Vocabulary Working Meeting on Product Hierarchy
July
31, Bridge Information Systems, New York City
Participating
Organizations
Bang
Networks, Bank of New York, Bridge Information, Dow Jones/WSJ, Fidelity
Investments, FININFO, FISD, FT Information, ILX Systems, Merrill
Lynch, Nasdaq Stock Market, Reuters, Telekurs Financial
What's
The Scope of 1.0 Beta?
MDDL
version 1.0 will be limited to equities, collective investment vehicles
and indices. The priority of development after completion of the
initial release will be:
1.
Completion of instrument/asset classes (i.e. debt, contracts,
units)
2. Completion of indicators (i.e. financial, exchange statistics,
ratings, economic, industrial)
3. Corporate events
MDDL
working groups will immediately begin work on completion of instrument/asset
classes following release of 1.0 in beta format. No immediate time
frame was established for completion of the MDDL standard.
What's
Required for Release of 1.0?
The
following must be completed prior to release of 1.0 beta
- Product
hierarchy/data relationship structure including finalization of
MDDL parent/child relationships (the subject of the July 31 meeting)
- MDDL
schema/DTD
- MDDL
data dictionary
- Review
and adoption of the proposed data dictionary is the top Vocabulary
Committee priority between now and release of 1.0 final
- Proposed
definitions of terms used in the structure of MDDL descriptors
are required prior to sending out for global industry review
- A
mechanism for managing proposals and recommended changes to
the data dictionary terms and definitions must be created
- A
separate working group consisting of pricing experts is needed
to help define the critical elements of MDDL Valuations. FISD
will manage the pricing review process
- Determination
of how the controlled vocabulary lists will be maintained and
implemented
- Which
lists are included in MDDL
- Which
lists are included via name space reference
- MDDL
example documents (instance documents)
- MDDL
White Paper
- Managers
guide to MDDL concept and structure
- Business
problems to be solved (user applications requirement)
- Vendor
and user implementation objectives
- Vendor
-- proof of concept/viability of MDDL. Can vendors modify
their market data products to meet the specification of
MDDL?
- User
-- determination of how MDDL will be used (pilot programs
for internal applications); determination of the cost
of conversion to MDDL (ideas on scaling, size and performance);
and ability to use MDDL to normalize multiple vendor data
files
- Visibility
Strategy
- Press
- XML
Groups
- Conferences
and seminars
Product
Hierarchy
The
following concepts need to be rolled into the specification:
- The
method of defining and providing the controlled vocabularies needs
to be formalized.
- The
element "role" in the "instrumentIdentifier"
contains a controlled vocabulary.
-
The concept of "primary" or a "precedence"
or "rank" needs to be added as a descriptor. Specifically,
this needs to be a child of the "code" for an "instrumentIdentifier".
-
Fields like "currency" and "market" need to
allow for multiple schemes. For example, there may be an ISO currency
scheme BUT vendors need to be able to provide their own proprietary
schemes AS WELL. NOTE: It is intended that the ISO will be provided
but the proprietary version may be added IN ADDITION TO the ISO
scheme.
-
Add "scheme" as an XML attribute to everything that
can have a controlled list. It may be a URL or a name. Provided
for something like "defaultSchemeFor" overriding as
with NewsML defaultVocabularyFor.
-
Add "multiplier" to "currency".
-
Add "new" to "high"/"low" and similar
fields to indicate that this value breaks a previous threshold.
-
The descriptors "highType", "lowType", and
similars need a controlled vocabulary something like this: IntraDay,
WeekToDate, MonthToDate, YearToDate, Weekly, 52wk, Lifetime, Trailing12Month,
Previous, 1 Year, 3 Years, 5 Years, 10 Years
-
Add "components" to each index and not that some indexes
are composed of other indexes
Each component of an index
will specify the following information: Identifier, Base Price,
Weighting, and Divisor.
-
An index has an "indexValue" not a price.
-
Indices can have an "indexMethodology" and an "indexObjective"
(like "fundObjective" for Mutual Funds).
-
As part of the descriptor "expression", consider the
multiplier associated with quoting items in 32nds or othe rnon-decimal
values. Maybe MathML/XBRL has some insights on how to properly
specify denominators and numerators involved in this
-
Sometimes, there are corrections and cancels (of trades) and thus
restatement of the values previously provided. In that event,
a new document is sent and there should be some indication that
the data provided is a correction (and what the correction is).
For example, "Quote 1" is sent out at 10:00 immediately
followed by "Quote 2" immediately followed by "Quote
1 (modified)". Users want to know that the modified quote
is the same as Quote 1 even though it was sequenced after Quote
2.
-
Provide a sequence number for quotes.
-
When an identifier for an instrument changes - what happens? Certainly
there is a corporate action that indicates the change but then
how does a vendor send out quotes linking the old identifier and
the new one (until some specified time where it is assumed this
information has been transmitted successfully). Certainly multiple
identifiers where one is marked as the "primary" seems
appropriate.
-
When the index calculation changes - what happens to let users
know that something has changed thus indicating to them they may
need to retroactively calculate an index with new values.
-
An index may have a base value and associated date/time/month
(or year only). This index may get changed at which point a new
base value date is assumed.
|
|