This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] Re: [db-wg] Improved RIPE Registry Global Resource Service - now accessible via RESTful API
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] Improved RIPE Registry Global Resource Service - now accessible via RESTful API
- Next message (by thread): [ncc-services-wg] Public demo sessions to develop RIPEstat Toolbox
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Palse
ppalse at ripe.net
Wed Jan 12 16:56:09 CET 2011
Dear Richard, We are using a different system built on top of our RIPE Database software. The adoption of a common schema between ARIN and RIPE database is currently not possible. With the exception of a small subset of RPSL, the two data models are very different. Having said this, one of the powers of XML is in the ease with which it can be transformed using XSL for instance. In one of our first articles about our REST services we describe how we are using XSL to return our responses in multiple representation formats like JSON and HTML. Using this approach you may find that, especially for the subset of object types that may match between ARIN and the RIPE database like routing data for example, it is not difficult to transform objects from ARIN to the RIPE XML and vice versa. This way you could end up with a single view of both data sets. GRS on the other hand is an attempt to provide a global view of internet and operational data using a single XML representation already. In our last article on RIPE Labs about GRS sources we explain how it is possible to access the GRS data for ARIN and the other registries not only using the "-s" flag on port 43 but also using our REST interfaces. If you want to know more about RIPE's REST services you can find some examples in our API documentation and try to run them: http://labs.ripe.net/ripe-database/database-api/api-documentation I hope you find this information useful. Kind regards Paul Palse -- Database Group Manager at RIPE NCC http://www.ripe.net/info/ncc/contact.html On 11 Jan, 2011 Week: 3, at 19:55 PM, Richard L. Barnes wrote: > Hey Mirjam, > > Forgive me for not looking this up myself, but are you guys using the same RESTful API that ARIN is using? > > --Richard > > > > On Jan 11, 2011, at 9:55 AM, Mirjam Kuehne wrote: > >> Dear colleagues, >> >> The RIPE Registry Global Resource Service (GRS) that was announced earlier on this list is now accessible via the RIPE Database RESTful web services API. In addition to that we also added support for GRS to the new prototype search form. >> >> Read more on RIPE Labs: >> >> http://labs.ripe.net/Members/Paul_P_/grs-sources-and-the-ripe-database-api >> >> Kind Regards, >> Mirjam Kuehne >> RIPE NCC >> >> >> Mirjam Kuehne wrote: >>> [Apologies for duplicate emails] >>> Dear colleagues, >>> We have redesigned and improved the way we mirror other databases (Thanks to the RIPE NCC Database staff!). We now have a method of translating the operational data from other registries (for instance from other RIRs or the RADb) into the RIPE Database structure. >>> This means the RIPE Database will contain the most complete set of operational data in (RIPE) RPSL format that has ever been available in one place. >>> Read more on RIPE Labs: >>> http://labs.ripe.net/Members/Paul_P_/ripe-registry-global-resource-service >>> Kind Regards, >>> Mirjam Kuehne >>> RIPE NCC >> >
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] Improved RIPE Registry Global Resource Service - now accessible via RESTful API
- Next message (by thread): [ncc-services-wg] Public demo sessions to develop RIPEstat Toolbox
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]