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/db-wg@ripe.net/
[db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
- Previous message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
- Next message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Wed May 11 21:45:58 CEST 2016
Peter Hessler wrote: > What should the WG do, then? Ask the NCC to write new code? Update the > data-model? the code is new; the data model has it roots around 1992 (ripe-50) and can't be changed without causing serious disruption to data consumers, which would mean retooling pretty much anything ever built to ingest ripedb objects. There are a lot of db info consumers: https://www.ripe.net/analyse/statistics/ripe-database/ripedb-queries It works well enough that as a data consumer, I don't particularly need to see massive changes to it. It could be revolutionised and that might be interesting, but drastically changing the data model is a lot of work for all parties. Nick
- Previous message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
- Next message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]