 Ray, Mike mentioned some of the challenges that GPO faces. Talk about some of the challenges that you see Federal Register trying to address with Federal Register 2.0 and what you see sort of the development pathway beyond there. Okay, we want to get all of our publications converted into XML. And we've got a plan. We've worked out with our GPO partners to do that over the next couple of years. We want to get the rest of the Federal Registers into XML, the 94 to 99 period. We want to get all the CFRs from about 97 when they first went online up to the current. I think we've got about 10 years worth of those ready now. And of course, about 10 years worth of the Federal Register that are available in bulk XML. We want to move back to for all of our legacy publications. At our offices on North Capital Street, we have a unique regulatory library there which has substantial primary legal materials dating from the 1800s. We would love to see that converted and made available. There are no copyright issues with the material that is in our library. But we've got compilations of presidential material, executive agency material, the statutes from Congress, and other sources that would be of great public interest if and when we're able to get that converted and made available freely on the Internet. I think we're fast approaching a day where we can see the beginning of the regulatory timeline to the end in the sense of creation of a rule to publication in the Federal Register and the dynamic that that offers for public involvement, for public participation. I would love to see us be able to do something with that over the next few years. We've got our own internal production tool which we use to receive submissions from agencies, to complete edits on, to align with the Code of Federal Regulations, and then to hand off to our GPO partners for them to compose and produce in its final version. We'd love to see that cycle from beginning to end unified so that the production tool and the public interface can become one and the same. I think the opportunities are virtually endless. The challenges I think are now that we have our data in XML more challenges of imagination and effort than they are of anything else. There's one other that I would like to add and that's the point in time system of ECFR. It's one of the things that we have an ECFR system today which is essentially the daily snapshot of the Code of Federal Regulations. One thing that well-structured data is going to allow us to do and there's a lot of work that's going to be involved but it'll be able to provide that point in time system so that you'd be able to dial back to a date and see what the Code of Federal Regulations was on a particular date, something of I think very high value that Ray and I talk about quite often as we know that we from our strategy perspective need to move forward with this publication support system that he just mentioned as well as a point in time system for the CFR. For about five minutes remaining I'm going to open up the floor to questions. So how much did you pay the GovPulse guys to do all this development? You know I don't know the answer. There was a cost. I don't know what it was. Yeah. Roy, what? GovPulse was built for the sunlight labs contest and so the GPO didn't pay anything for that. What would be the most helpful thing that the community could build for the Federal Register? For me I think the next challenge and I'm inspired by Beth on this point is public participation and by public I mean that part of the public which is an infrequent user of Federal Register information. We know the big guys are going to take care of themselves but I think they're small businesses as we've heard about earlier. There are a lot of other interested participants that we can make this easy for them to get involved and I think that's a big challenge and I think it's also a great opportunity. I was really struck by the fact that you also have a library of all sorts of other things that are not publicly available and you're thinking about possible partners maybe to work with to make that information available or I'm sure throughout the government there are all these kinds of libraries that exist all these kinds of repositories of information. One great thing about having such a group of folks together here at this law.gov event is that we can start thinking about how we can all work together. One to find out what's there which I think is the first problem. Who has what and where it is and then how we can work together to make it available. If you have suggestions that would be a fun conversation to have. We're looking for partners. One thing to add to that on the retrospective conversion of content. There's been a lot of good work that's been done in creating again a standard or a reference for what the requirement would be to create what we call a preservation standard of a document. So how you scan it etc. and the technical aspects of it. It's been a I think a very effective and successful exercise and in our work with the library of Congress. We've been looking at content that they've scanned particularly of the statutes at large and it's working very well and we're able to parse that into very usable data that conforms with the format of what we already have in federal digital system on the statutes at large. So that's I think an existence proof and an example of what could be done. Now I think with a community like this if we have a standard that we can reference and we talk about participation with providing content with that standard we have the basis for actually processing the data and making it easily accessible. So I think some good pieces are available and falling into place that we could leverage. Great. With that please join me in thanking Ray and Mike for their insightful comments. And that concludes this panel.