1. SDMX at the New York Fed Paul Asman 10 January 2007

2. Outline What we’ve done How it’s being used What’s ahead for us –Representational changes –Registry

3. 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

4. NY Fed Data in SDMX (1) Utility Messages Foreign Exchange Rates Interest Rates (Fed Funds) Primary Dealer Statistics

5. Utility Structure Sample

6. Utility Data Sample

7. 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

8. Cross-Sectional Data Sample

9. 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

10. Web Traffic (SDMX Use)

12. 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

13. 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.

14. Registry Supports automatic discovery Represents a professionalizing of our SDMX implementation We have implemented some registry functionality, but by no means all.

15. Registry Architecture RegistrationDiscovery Subscription/ Notification Other Services Provisioning Metadata Repository Provision Agreement, Data Sources, Constraints, etc. Structural Metadata Repository Key Family, Metadata Structure Definition, Item Scheme, etc.

16. 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

17. Administrative Functions

18. Message Submission

19. And Response

20. 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.

21. 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