Bang Networks,
Bloomberg, CSFB, Deutsche Bank, EDS, Fidelity, FISD, Fleet Asset
Management, Goldman Sachs, ILX Systems, London Market Systems,
Merrill Lynch, MFS Investment Management, Morgan Stanley, Reuters,
UBS Paine Webber
Product
Extensions
FISD members
initiated discussions on the next product areas for MDDL with most of
the discussion focused on debt/fixed income. The initial objectives of
the discussions will be to design the business modeling strategy (i.e.
define all the properties associated with the debt domain) and to
determine the overlap between debt and preferred equities and equity
warrants (completion of equities domain). Once the business model is
established, the MDDL Technical Committee will be able to extend MDDL
to debt instruments.
Defining
the properties for debt instruments is the next step and will be the
principle subject of the February 13 meeting in London. This
will be a concept discussion. All ideas are welcome.
Construct
Enhancements
The two major
constructs for grouping data in Version 1.0 are snap for
snapshot quotes and timeseries for quotes over time. The next
construct areas on target for inclusion are query (the
mechanism for how users would request data) and update (the
mechanism for how MDDL will send data updates including
delete/remove). The Technical Committee is actively seeking volunteers
to work on the new construct areas. Members should make their interest
known via e-mail to Michael Atkin
at FISD or James Hartley
at Reuters.
Liaison
Committee
MDDL is in the
process of establishing formal liaison with a number of XML-related
organizations including XBRL, RIXML, IPTC/NewsML, ISO 15022 and SDMX.
We have created a formal Liaison Committee to help manage these
relationships. The co-chairs of the Liaison Committee are
John Bottega
(Merrill Lynch) and Tony
Coates (Reuters). Participation is open to all interested FISD
members. MDDL met with ISO 15022 and will become a liaison to
TC68/SC4.
Change
Management
MDDL will use a
three-tiered version identification scheme to manage changes to the
specification. Major changes are those that affect backwards
compatibility. Minor and incremental changes will likely be bundled
for implementation management. New releases of MDDL can also be made
on “committee decision” for PR purposes or in light of the existing
release point (i.e. the Committee can choose to turn an incremental
change into a minor release or a minor into a major release if the
situation so warrants).
1.
|
0.
|
1
|
Major
Change |
Minor
Change |
Incremental
Change |
Major
Changes
- Technical
fixes or enhancements that affect backwards compatibility (e.g.
deletion)
- Changes to
the default vocabulary
Minor
Changes
- Extension
of MDDL into a new Domain or new Class
- Change to
MDDL descriptors
- Enhancement
or addition of new construct area
Incremental Changes
- Extension
of MDDL into a new Subclass
- Changes to
controlled vocabulary
- Addition of
a new Property to the vocabulary
- Edits to
documentation
View MDDL
Change Notification Procedure Flowchart
View MDDL
Change Request Form in
Word or Acrobat
