SDMX at the New York Fed

Paul Asman10 January 2007

Outline

• What we’ve done

• How it’s being used

• What’s ahead for us–Representational changes

–Registry

Rationale

• Goals– To represent our most sought data in a

guaranteed format– That the consumers of that data can easily

integrate into their own applications

• SDMX meets these goals

NY Fed Data in SDMX (1)

Utility Messages

• Foreign Exchange Rates

• Interest Rates (Fed Funds)

• Primary Dealer Statistics

Utility Structure Sample

Utility Data Sample

NY Fed Data in SDMX (2)

Cross-Sectional Messages

• Temporary Open Market Operations (repurchase agreements)

• Permanent Open Market Operations (for our own portfolio)

• Securities Lending

Cross-Sectional Data Sample

Message Type Not Important

• Our choice of message type (at least between utility and compact) is a matter of convenience

• SDMX has utilities for converting messages in one format to messages in another

• What matters is that we publish data in a guaranteed format, not which format we guarantee

Web Traffic (SDMX Use)

Web Traffic (SDMX Use)

0

200000

400000

600000

800000

1000000

1200000

1400000

1600000

1800000

2000000

home page TOMO WebService

POMO WebService

FX RatesXML File

FX rates webpage

Future Representational Directions

• SDMX 2.0 features– Hierarchical code lists– Code list translation tables– Extended key families

• The time-value pairs will remain, and automated consumption of them will not be affected

More to Be Done

• We do not offer automatic expansion of codes for key family dimensions

• We do not offer automatic discovery of what we have

An automated registry can fill these gaps.

Registry

• Supports automatic discovery

• Represents a professionalizing of our SDMX implementation

We have implemented some registry functionality, but by no means all.

Registry Architecture

Registration DiscoverySubscription/Notification

Other Services

Provisioning Metadata RepositoryProvision Agreement, Data Sources, Constraints, etc.

Structural Metadata RepositoryKey Family, Metadata Structure Definition, Item Scheme, etc.

Registry Functionality Implemented

• Storage of structural metadata– Code lists– Key families– Concepts– Other maintainable artifacts

• Query and retrieval

• Submission, modification, and removal

• Web Service interface

Administrative Functions

Message Submission

And Response

Directions

• Take advantage of SDMX 2.0

• Take advantage of Registry functionality we have implemented

• Implement more Registry functionality

This will meet the needs of the foreseeable future.

Contact Information

Paul Asman

Federal Reserve Bank of New York

paul.asman@ny.frb.org

1-212-720-6637

Presentation (including notes): www.newyorkfed.org/xml/sdmxConferenceJanuary2007.ppt