[db-wg] Future of "geoloc:"
- Previous message (by thread): [db-wg] Future of "geoloc:"
- Next message (by thread): [db-wg] Future of "geoloc:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Suchy
danny at danysek.cz
Tue Apr 12 22:26:24 CEST 2022
geofeed is quite new attribute... you cannot expect quick adoption in field. At this time, geoloc should simply remain as-is. Daniel On 4/12/22 21:17, denis walker via db-wg wrote: > Colleagues > > Now we have the "geofeed:" attribute, what should we do with > "geoloc:"? Right now far more people are using "geoloc:" than > "geofeed:". > > denis$ zgrep "^geofeed:" ~/Desktop/ripe.db.inetnum.gz | wc -l > 289 > denis$ zgrep "^remarks:\s*geofeed" ~/Desktop/ripe.db.inetnum.gz | wc -l > 13 > > Although from the 289 there are only 161 unique organisations. > > denis$ zgrep "^geoloc:" ~/Desktop/ripe.db.inetnum.gz | wc -l > 35453 > > cheers > denis > co-chair DB-WG >
- Previous message (by thread): [db-wg] Future of "geoloc:"
- Next message (by thread): [db-wg] Future of "geoloc:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]